• Journal of the Korean Society of Systems Engineering
• /
• v.14 no.2
• /
• pp.49-57
• /
• 2018

The main objective of this paper is come up with methodology approach for FPGA-based system in verification and validation lifecycle regarding software reliability using system engineering approach. The steps of both reverse engineering and re-engineering are carried out to implement an FPGA-based of safety critical system in Nuclear Power Plant. The reverse engineering methodology is applied to elicit the requirements of the system as well as gain understanding of the current life cycle and V&V activities of FPGA based-system. The re-engineering method is carried out to get a new methodology approach of software reliability, particularly Software Reliability Growth Model. For measure the software reliability of a given FPGA-based system, the following steps are executed as; requirements definition and measurement, evaluation of candidate reliability model, and the validation of the selected system. As conclusion, a new methodology approach for software reliability measurement using software reliability growth model is developed.

• International Journal of Internet, Broadcasting and Communication
• /
• v.15 no.2
• /
• pp.218-226
• /
• 2023

In Korea, we still use function point based cost estimations for software size and cost of a project. The current problem is that we make difficultly calculating function points with requirements and also have less accurate. That is, it is difficult for non-experts to analyze requirements and calculate function point values with them, and even experts often derive different function points. In addition, all stakeholders strongly make the validity and accuracy of the function point values of the project before /after the development is completed. There are methods for performing function point analysis using source code [1][2][3][4] and some researchers [5][6][7] attempt empirical verification of function points about the estimated cost. There is no research on automatic cost validation with source code after the final development is completed. In this paper, we propose automatically how to calculate Function Points based on natural language requirements before development and prove FP calculation based on the final source code after development. We expect validation by comparing the function scores calculated by forward engineering and reverse engineering methods.

• KIISE Transactions on Computing Practices
• /
• v.23 no.6
• /
• pp.335-342
• /
• 2017

In the verification and validation procedures regarding the safety-critical software of nuclear power plants for the attainment of the requisite license from the regulatory body, it is difficult to judge the safety and dependability of the development, implementation, and validation activities through a simple reading and review of the documentation. Therefore, these activities, especially safety assurance activities, require systematic evaluation techniques to determine that software faults are acceptable level. In this study, a safety case methodology is applied in an assessment of the level and depth of the results of the development and validation of a manufacturer in its targeting of the bistable processor of a digital reactor protection system, and the evaluation results are analyzed. This study confirms the possibility of an effective supplementation of the existing safety demonstration method through the application of the employed safety case methodology.

• Journal of the Korea Society for Simulation
• /
• v.27 no.1
• /
• pp.25-32
• /
• 2018

This paper presents an efficient software reliability testing method for the model based auto-generated code and reify a dynamic test procedure. The benefits of executing the model-based each static/dynamic reliability test before the code-based static/dynamic reliability test are described. Also, The correlations of code/model based reliability test are demonstrated by using model testing tool, Model Advisor and Verification and Validation, and the code testing tool, PolySpace and LDRA. The result of reliability test is indicated in this paper.

• Nuclear Engineering and Technology
• /
• v.41 no.1
• /
• pp.91-98
• /
• 2009

The "3+3 Process" for safety critical software for nuclear power plants' I&C (Instrumentation and Control system) has been developed in this work. The main idea of the "3+3 Process" is both to simplify the software development and safety analysis in three steps to fulfill the requirements of a software safety plan [1]. The "3-Step" software development process consists of formal modeling and simulation, automated code generation and coverage analysis between the model and the generated source codes. The "3-Step" safety analysis consists of HAZOP (hazard and operability analysis), FTA (fault tree analysis), and DV (design validation). Put together, these steps are called the "3+3 Process". This scheme of development and safety analysis minimizes the V&V work while increasing the safety and reliability of the software product. For assessment of this process, validation has been done through prototyping of the SDS (safety shut-down system) #1 for PHWR (Pressurized Heavy Water Reactor).

• Bulletin of the Korean Space Science Society
• /
• 2006.10a
• /
• pp.155-155
• /
• 2006

• Proceedings of the Korean Nuclear Society Conference
• /
• 1999.10a
• /
• pp.115.1-115
• /
• 1999

• Proceedings of the Safety Management and Science Conference
• /
• 2001.05a
• /
• pp.77-81
• /
• 2001

Burn-in is a test procedure to find and eliminate the inherent initial failure of a product during or at the final stage of production process. Software testing is the validation and verification process which is used to cut off the faults from a software. The two have the common function and objective of "debugging". This article summarizes some significant models on the optimal hardware and software burn-in time, and provides the relevant paper lists. The need for the development of the unified burn-in policy of a hardware-software system is addressed.addressed.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.19 no.38
• /
• pp.61-68
• /
• 1996

Quality Assurance Principles must be effectively implemented in developments and in use of safety critical software in nuclear industry. Brief definitions related to computer software and quality assurance were defined and several methods for evaluating software quality were proposed herewith. Independent verification and validation was suggested to assure the quality of safety critical software.

• Proceedings of the KIEE Conference
• /
• 2005.07d
• /
• pp.2489-2491
• /
• 2005

Currently, Programmable Logic Contorller(PLC) uses Real Time Operation System(RTOS) as basic OS. RTOS executes defined results as to defined time. General features of RTOS emphasize the priority in each task, high-speed process of external interrupt, task scheduling, synchronization in task, the limitation of memory capacity. For safety critical placement, PLC software needs Verification and Validation(V&V). For example, nuclear power plant. In this paper, PLC RTOS is verified by formal methods. Particularly, formal method V&V uses verification tool called 'STATEMATE', and shows the results.