• Nuclear Engineering and Technology
• /
• 제39권2호
• /
• pp.129-132
• /
• 2007

It is generally known that software reliability growth models such as the Jelinski-Moranda model and the Goel-Okumoto's non-homogeneous Poisson process (NHPP) model cannot be applied to safety-critical software due to a lack of software failure data. In this paper, by applying two of the most widely known software reliability growth models to sample software failure data, we demonstrate the possibility of using the software reliability growth models to prove the high reliability of safety-critical software. The high sensitivity of a piece of software's reliability to software failure data, as well as a lack of sufficient software failure data, is also identified as a possible limitation when applying the software reliability growth models to safety-critical software.

• 전기전자학회논문지
• /
• 제16권2호
• /
• pp.145-152
• /
• 2012

This paper is the Software Hazard Analysis (SWHA) which will study the managerial process and the technical methode and techniques inherent in the performance of software safety task within the Military Aircraft System Safety program. This SWHA identifies potential hazardous effects on the software intensive systems and provides a comprehensive and qualitative assessment of the software safety. The purpose of this paper is to identify safety critical functions of software in Military A/C. The identified software hazards associated with the design or function will be evaluated for risks and operational constraint to further improve the software design requirement, analysis and testing efforts for safety critical software. This common SWHA, the first time analysis in KOREA, was review all avionics OFP(Operational Flight Program), and focus only on software segments which are safety critical. This paper provides a important understanding between the customer and developer as to how the software safety for the Military A/C will be accomplished. It will also provide the current best solution which may as one consider the necessary step in establishing a credible and cost-effective software safety program.

• Journal of Electrical Engineering and Technology
• /
• 제2권3호
• /
• pp.386-390
• /
• 2007

At recent times, an essential issue in the replacement of the old analogue I&C to computer-based digital systems in nuclear power plants becomes the quantitative software reliability assessment. Software reliability models have been successfully applied to many industrial applications, but have the unfortunate drawback of requiring data from which one can formulate a model. Software that is developed for safety critical applications is frequently unable to produce such data for at least two reasons. First, the software is frequently one-of-a-kind, and second, it rarely fails. Safety critical software is normally expected to pass every unit test producing precious little failure data. The basic premise of the rare events approach is that well-tested software does not fail under normal routine and input signals, which means that failures must be triggered by unusual input data and computer states. The failure data found under the reasonable testing cases and testing time for these conditions should be considered for the quantitative reliability assessment. We presented the quantitative reliability assessment methodology of safety critical software for rare failure cases in this paper.

• Nuclear Engineering and Technology
• /
• 제27권1호
• /
• pp.84-95
• /
• 1995

Application of computer software to safety-critical systems is on the increase. To be successful, the software must be designed and constructed to meet the functional and performance requirements of the system. For safety reason, the software must be demonstrated not only to meet these requirements, but also to operate safely as a component within the system. For longer-term cost consideration, the software must be designed and structured to ease future maintenance and modifications. This paper present a software engineering process for the production of safety-critical software for a nuclear power plant The presentation is expository in nature of a viable high quality safety-critical software development. It is based on the ideas of a rational design process and on the experience of the adaptation of such process in the production of the safety-critical software for the Shutdown System Number Two of Wolsong 2, 3 & 4 nuclear power generation plants. This process is significantly different from a conventional process in terms of rigorous software development phases and software design techniques. The process covers documentation, design, verification and testing using mathematically precise notations and highly reviewable tabular format to specify software requirements and software design. These specifications allow rigorous, stepwise verification of software design against software requirements, and code against software design using static analysis. The software engineering process described in this paper applies the principle of information-hiding decomposition in software design using a modular design technique so that when a change is' required or an error is detected, the affected scope can be readily and confidently located. It also facilitates a sense of high degree of confidence in the ‘correctness’ of the software production, and provides a relatively simple and straightforward code implementation effort.

• 한국멀티미디어학회논문지
• /
• 제15권1호
• /
• pp.115-130
• /
• 2012

오늘날 대다수의 안전필수 시스템들(Safety-Critical Systems)에는 컴퓨터, 전기 및 전자 부품이나 장치들에 소프트웨어를 칩에 내장하거나 제어용 소프트웨어 시스템이 탑재되어 구축되고 있다. 이에 따라, 컴퓨터 소프트웨어를 내장하였거나 탑재한 시스템들의 안전성을 평가하기 위한 여러 가지의 결함 분석 기법들이 제안되어져 오고 있다. 이러한 소프트웨어 결함 분석 기법들은 전통적으로는 하나의 안전필수 시스템을 분석하는데 단지 하나의 방법으로만 분석해 왔으나, 시스템의 종류와 특성이 다양해지면서 그 시스템에 가장 알맞은 결함 분석 기법이 동원되어야 함은 필수적이다. 본 연구에서는, 안전필수 시스템에서 소프트웨어의 크기가 비교적 작고, 안전성과 관련한 시스템 제어 반응 시간이 특별히 민감하지 않는 소프트웨어의 안전성을 평가하는 방법으로 결함트리 분석(FTA)과 소프트웨어 고장 유형 및 영향 분석(FMEA)을 결합한 시스템 결함 분석 방법을 제안하고 유비쿼터스 헬스케어 시스템을 이용하여 사례연구를 수행하고자 한다.

• 한국항행학회논문지
• /
• 제19권2호
• /
• pp.91-97
• /
• 2015

이 논문은 항공 분야에서의 안전필수 소프트웨어를 평가하기 위한 고려사항을 기술한다. 항공 분야에서의 안전필수 소프트웨어의 평가를 수행하기 위해서는 해당 소프트웨어의 평가 수준에 대한 정보가 필요하다. 그 수준은 표준에 명시되어 있으나 소프트웨어 자체적으로 결정되는 요소가 아니며 시스템 안전 평가 결과 및 시스템 설계 결과에 의존적이다. 그러므로 소프트웨어 평가수준을 결정하기 위해 시스템 개발 및 시스템 안전 평가 표준에서 필요로 하는 정보에 대해 설명한다. 그리고 소프트웨어를 평가하기 위한 기존의 방법론들을 조사하고 항공기 지상 유도 및 통제 시스템 소프트웨어의 평가에 적용할 방법을 제시한다.

• International Journal of Safety
• /
• 제3권1호
• /
• pp.38-46
• /
• 2004

This paper introduces the software life-cycle V&V (verification and validation) tasks for the KNICS (Korea nuclear instrumentation and control system) project. The objectives of the V&V tasks are mainly to develop a programmable logic controller (PLC) for safety critical instrumentation and control (I&C) systems, and then to apply the PLC to developing the prototype of an engineered safety features-component control system (ESF-CCS) in nuclear power plants. As preparative works for the software V&V, various kinds of software plans and V&V task procedures have been developed according to the software life-cycle management. A number of software V&V tools have been adopted or developed to efficiently support the V&V tasks. The V&V techniques employed in this work include a checklist-based review and inspection, a requirement traceability analysis, formal verification, and life-cycle based software testing.

• 대한전기학회:학술대회논문집
• /
• 대한전기학회 2007년도 제38회 하계학술대회
• /
• pp.1201-1202
• /
• 2007

Safety critical systems are those in which a failure can have serious and irreversible consequences. Nowadays digital technology has been rapidly applied to critical system such as railways, airplanes, nuclear power plants, vehicles. The main difference between analog system and digital system is that the software is the key component of the digital system. The digital system performs more varying and highly complex functions efficiently compared to the existing analog system because software can be flexibly designed and implemented. The flexible design make it difficult to predict the software failures. This paper reviews safety standard and criteria for safety critical system such as railway system and introduces the framework for the software lifecycle. The licensing procedure for the railway software is also reviewed.

• Nuclear Engineering and Technology
• /
• 제44권6호
• /
• pp.663-672
• /
• 2012

As software based digital I&C (Instrumentation and Control) systems are used more prevalently in nuclear plants, enhancement of software dependability has become an important issue in the area of nuclear I&C systems. Critical attributes of software dependability are safety and reliability. These attributes are tightly related to software failures caused by faults. Software testing and V&V (Verification and Validation) activities are hence important for enhancing software dependability. If the risky modules of safety-critical software can be predicted, it will be possible to focus on testing and V&V activities more efficiently and effectively. It should also make it possible to better allocate resources for regulation activities. We propose a prediction technique to estimate risky software modules by adopting machine learning models based on software complexity metrics. An empirical study with various machine learning algorithms was executed for comparing the prediction performance. Experimental results show SVMs (Support Vector Machines) perform as well or better than the other methods.

• Nuclear Engineering and Technology
• /
• 제32권6호
• /
• pp.537-548
• /
• 2000

The requirement of ultra high reliability of the safety critical software can not be demonstrated by testing alone. The specification based on formal method is recommended for safety system software. But there exist various kinds of formal methods, and this variety of formal method is recognized as an obstacle to the wide use of formal method. In this paper six different formal method have been applied to the same part of the functional requirements that is calculation algorithm intensive. The specification results were compared against the criteria that is derived from the characteristics that good software requirements specifications should have and regulatory body recommends to have. The application experience shows that the critical characteristics should be defined first, then appropriate method has to be selected. In our case, the Software Cost Reduction method was recommended for internal condition or calculation algorithm checking, and statechart method is recommended for the external behavioral description.