• Journal of Aerospace System Engineering
• /
• v.17 no.1
• /
• pp.33-41
• /
• 2023

As seen in the case of the Boeing 737 Max accident, the proportion of aircraft software is rapidly increasing. However, it is vulnerable to safety issues. In case of domestic aircraft software, to operate a Light Unmanned Aerial Vehicle (LUAV) less than an empty weight of 150 kg, safety certification is required for an Ultra-Light Vehicle (ULV). However, software certification procedure is not included. Since the use of LUAVs has increased recently, software verification is required. This paper proposed a checklist of LUAV software that could be applied to LUAV referring DO-178C, an aviation software certification standard. A case study of applying the proposed checklist to the Model-based Development-based Helicopter Flight Control Computer (FCC) project currently used by domestic and foreign advanced companies and institutions was conducted.

• Journal of the Korean Society for Aeronautical & Space Sciences
• /
• v.40 no.6
• /
• pp.548-554
• /
• 2012

Verification and validation of operational software of the flight control computer, which is flight safety critical, is very important to prove correctness and faultness of the software. To verify the real-time softare requirement on operational software of flight control computer, real-time software internal parameter and variable monitoring technics on hardware-in-the-loop environment, similar to on-flight environment, is required. This paper describes flight safety critical software validation and verificiation environment using standard debugging interface, NEXUS 5001.

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

• IEMEK Journal of Embedded Systems and Applications
• /
• v.4 no.4
• /
• pp.164-173
• /
• 2009

Automotive systems have tended to be equipped with many electronic contents to satisfy safety, comport, convenience, and entertainment services over the past years. As a result, the amount of vehicle embedded software in electrical/electronic(E/E) systems is steadily increasing to manage these requirements. This leads to the traditional, document-based software development in the vehicle embedded systems being increasingly displaced by a model-based development in order to reduce software development time and cost. Due to the application of model-based development, a great evolution is being realized in the aspect of efficiency, but the development is being made without sufficient testing. So, erroneous automotive embedded software may cause serious problems such as car accidents which relate to human safety. Therefore, efficient methods for model-based test and validation are needed to improve software reliability in the stage of embedded software development. This paper presents the model-based development and test method for AUTOSAR embedded software to improve its reliability and safety, and it is demonstrated based on the case study.

• Proceedings of the KSR Conference
• /
• 2008.11b
• /
• pp.1257-1263
• /
• 2008

Recent advances in embedded system technology have brought more dependence on automating train control. While much efforts have been reported to improve electronic hardware's safety, not so much systematic approaches to evaluate software's safety, especially for the vital software running on board train controllers. In this paper, we have developed a software testing tool to evaluate train control system software safety, expecially "Metric Analysis" module. We have reviewed requirements in the international standards and surveyed available tools in the market. From this, we identified the S/W metric analysis module is required for software evaluation. So we have developed S/W metric analysis module for railway signaling systems.

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

• Journal of the Korea Safety Management & Science
• /
• v.5 no.2
• /
• pp.165-174
• /
• 2003

This paper analyzes the competitive power of domestic software industries focusing on the subjective rating of software development process. A survey is conducted to perform subjective evaluation of software development process of his/her company. Comparison between SPICE-experienced companies and non-experienced companies, between domestic companies and companies in developed countries are performed.

• Proceedings of the Safety Management and Science Conference
• /
• 2011.04a
• /
• pp.451-459
• /
• 2011

In this paper, a software release model is presented to determine the optimum testing time with consideration of software error type. The software errors are classified into two types, major and minor errors. The software testing is continued until the Nth major error is discovered and corrected. The total cost needed before and after testing time is modeled under nonhomogeneous Poisson error correction model. Numerical examples are presented to demonstrate the results.

• Proceedings of the Safety Management and Science Conference
• /
• 2005.05a
• /
• pp.129-135
• /
• 2005

This paper proposes the interated and balanced project management system for software and IT by considering BSC, MBNQA, ISO 9001, Six Sigma, CMM and SPICE. This system can be extended to assess the various project management practices.