• Journal of Institute of Control, Robotics and Systems
• /
• v.13 no.12
• /
• pp.1179-1185
• /
• 2007

This paper presents a new approach to automotive embedded systems development and validation. Recently automotive embedded systems become even more complex and the product life cycle is getting reduced. To overcome these problems AUTOSAR, a standardized software platform and component based approach, was introduced. Model-based approach has been widely applied in the development of embedded systems and has strong benefits such as early validation and automated testing. In this paper cooperative development and validation of AUTOSAR and model-based approach are introduced and automated testing techniques are proposed. With the proposed techniques we can improve complexity management through increased reuse and exchangeability of software module and automated testing is realized.

• 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.

• 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).

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2012.10a
• /
• pp.495-497
• /
• 2012

Development of application risk management for medical device software test. First, Through questionnaires, Medical device manufacturers, Analysis of software validation and risk management status. Second, Analyzed by comparing the difference between black box testing and white box testing. Third, After analyzing the potential for software analysis tools using code derived factors were quantified, Finally, Medical device risk management process so that it can be applied to build the framework by FMEA(Failure Mode and Effect Analysis) technique. Through this Difficult to build software validation and risk management processes for manufacturers to take advantage of support in medical device GMP(Good Manufacture Practice).

• Proceedings of the IEEK Conference
• /
• 2002.07b
• /
• pp.920-923
• /
• 2002

In this paper, we propose Class Diagram With Constraints (CDWC) as an object oriented modeling technique which makes validation possible in software development. CDWC is a simple and basic model for the object oriented analysis, and has a reasonable strictness for software developers. CDWC consists of class diagrams and constraints (invariant and pre/post conditions), using UML and a subset of OCL.. We introduce a method of validation of CDWC using the verification technique of algebraic formal specification language CafeOBJ.

• Asia pacific journal of information systems
• /
• v.30 no.3
• /
• pp.457-496
• /
• 2020

This study aims to extensively analyze the performance of various Machine Learning (ML) techniques for predicting version to version change-proneness of source code Java files. 17 object-oriented metrics have been utilized in this work for predicting change-prone files using 31 ML techniques and the framework proposed has been implemented on various consecutive releases of two Java-based software projects available as plug-ins. 10-fold and inter-release validation methods have been employed to validate the models and statistical tests provide supplementary information regarding the reliability and significance of the results. The results of experiments conducted in this article indicate that the ML techniques perform differently under the different validation settings. The results also confirm the proficiency of the selected ML techniques in lieu of developing change-proneness prediction models which could aid the software engineers in the initial stages of software development for classifying change-prone Java files of a software, in turn aiding in the trend estimation of change-proneness over future versions.

• Journal of Platform Technology
• /
• v.10 no.4
• /
• pp.11-24
• /
• 2022

The tool for developing airborne software requires the same level of safety as airborne software because the tool whose output is part of the airborne software and thus could insert an error into the airborne software. This paper describes how to ensure the reliability of the tool output that becomes a part of the airborne software by validating of the input and output files of the tool when generating the ARINC 661 standard UA definition file and the CDS configuration file through the A661UAGEN tool of Hanwha Systems. We present the method to validate XML data structure and contents with an XML schema definition, which is an input of the A661UAGEN tool. And the method to validate the output binary data by using mask data for the corresponding data structure and valid value, which is the output of the A661UAGEN tool, was presented. As such, validation of the input and output of the tool improves the reliability of binary DFs and CDs integrated into the airborne software, allowing airborne software developers to utilize the tool to ensure safety in developing the OFP.

• Proceedings of the Korean Society for Quality Management Conference
• /
• 2004.04a
• /
• pp.114-119
• /
• 2004

Software verification and validation(V&V) is a means to develop high-quality software and assure safety and reliability for software. Also, we can achieve the desired software quality through systematic V&V activities. The software to be applied safety critical system like nuclear power plants is required to setup the V&V methodology that comply with licensing requirements for nuclear power plants and should be performed V&V activities according to it. In this paper, we classified safety-critical, safety-related and non-safety for software according to safety function to be peformed and define V&V activities to be applied software grade. Also, we defined V&V activities, procedures and documentation for each phase of software development life cycle and showed techniques and management to perform V&V. Finally, we propose the V&V framework to be applied software development of SMART(System-integrated Modular Advanced ReacTor) MMIS (Man-Machine Interface System) and to comply with domestic licensing requirements.

• 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.

• Nuclear Engineering and Technology
• /
• v.27 no.3
• /
• pp.385-392
• /
• 1995

A software engineering process has been developed for the design of safety critical software for Wolsong 2/3/4 project to satisfy the requirement of the regulatory body. Among the process, this paper described the detail process of validation testing peformed to ensure that the software with its hardware, developed by the design group, satisfies the requirements of the functional specification prepared by the independent functional group. To perform the test, test facility and test software ore developed and actual safety system computer was connected. Three kinds of test cases, i.e., functional test performance test and self-check test were programmed and run to verify each functional specifications. Test failures ore fedback to the design group to revise the software and test result were analyzed and documented in the report to submit to the regulatory body. The test methodology and procedure were very efficient and satisfactory to perform the systematic and automatic test. The test results were also acceptable and successful to verify the software acts as specified in the program functional specification. This methodology can be applied to the validation of other safety-critical software.