• Journal of Software Assessment and Valuation
• /
• v.16 no.2
• /
• pp.87-98
• /
• 2020

Recently, IoT, artificial intelligence, cloud, big data, and mobile fields have converged, leading to a new industrial era called the 4th industrial revolution. This 4th industrial revolution has been expanded to all industry area and Software has been taken as important role in this revolution. Thus Software Safety is the huge factor because Software is highly relevant to human safety in accordance with Software expansion. However this Software Safety has been focused on not organization improvement activities but current design/development, In this paper, to solve this issue, Software Safety Maturity level and relevant Process Area is defined. This study is expected to contribute to systematic software safety activities.

• Journal of IKEEE
• /
• v.16 no.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.

• International Journal of Safety
• /
• v.8 no.2
• /
• pp.31-36
• /
• 2009

In accordance with the development of recent computer technology, railway signaling software became more complex for the intellectualization. Therefore the importance and dependency of railway signaling system on the computer software is getting more increased further, and the testing for the safety and reliability of railway signaling system software became more important. It is started to become influential as very important issue for the reliability and safety of vital embedded software like railway signaling system. The software coding which can have an effect on the safety at the coding level of software shall not be included preferentially, for the safety of software, and must be checked. This thesis suggested an automated testing tool for coding rules on this railway signaling system software, and presented its applied result for railway signaling system software. The testing items in the implemented tool had referred to the international standards in relation to the software for railway system and MISRA-C standards. This automated testing tool for railway signaling system can be utilized at the assessment stage for railway signaling system software also, and it is anticipated that it can be utilized usefully at the software development stage also.

• Proceedings of the KSR Conference
• /
• 2007.05a
• /
• pp.272-279
• /
• 2007

Recently, train control system is adopting computer system replacing mechanical system and its software is taking more responsibility than ever. Train control system software is a safety-critical embedded software with realtime and high reliability requirements. In this paper, we propose a safety assessment method for the train control system software. We review characteristics of train control system software and analyze related international software safety standards to derive requirements for safety assessment. Testing tools used for embedded software are surveyed to find a feasible safety assessment architecture. The proposed safety assessment method is to use safety activity results generated during development processes and feed them to the runtime embedded software testing tool.

• Journal of Information Processing Systems
• /
• v.17 no.5
• /
• pp.960-971
• /
• 2021

As the era of the 4th Industrial Revolution enters, the importance of software safety is increasing, but related systematic educational curriculum and trained professional engineers are insufficient. The purpose of this research is to propose the high priority elements for the software safety education program through needs analysis. For this purpose, 74 candidate elements of software safety education program were derived through contents analysis of literature and nominal group technique (NGT) process with five software safety professionals from various industries in South Korea. Targeting potential education participants including industrial workers and students, an on-line survey was conducted to measure the current and required level of each element. Using descriptive statistics, t-test, Borich needs assessment and Locus for focus model, 16 high priority elements were derived for software safety education program. Based on the results, suggestions were made to develop a more effective education program for software safety education.

• Nuclear Engineering and Technology
• /
• v.39 no.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.

• Journal of Electrical Engineering and Technology
• /
• v.2 no.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
• /
• v.27 no.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.

• International Journal of Safety
• /
• v.3 no.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.

• Nuclear Engineering and Technology
• /
• v.44 no.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.