• Journal of the Korea Safety Management & Science
• /
• v.13 no.4
• /
• pp.9-16
• /
• 2011

Modern systems become more complex and the demand for systems safety goes up sharply. Thus, the proper handling of the safety requirements in the systems design is getting greatly increased attention these days. Hazard analysis has been one of the active areas of research in connection with systems safety. In this paper, we study a subject on how the hazard analysis results can be incorporated in the systems design. To this end we set up a goal on how to systematically generate safety requirements that should reflect hazard analysis results and be implemented in the systems design and development. To do so, we first review the process for systems design and suggest the associated Model. Then the process and results of hazard analysis are analyzed and Modeled particularly with emphasis on the safety data. The resulting data Model incorporating both the hazard analysis and system life cycle is used in the generation of safety requirements. Based on the developed data Model, the generation of the requirements, the construction of requirements DB, and the change management later on is demonstrated through the use of a computer-aided software tool.

• Journal of Applied Reliability
• /
• v.14 no.1
• /
• pp.81-91
• /
• 2014

The IEC 61508 standard was established to specify the functional safety of E/E/PE safety-related systems. Safety life cycle to provide the framework and direction for the application of IEC 61508 is included in this standard. In this paper, we describe overviews, objects, scopes, requirements and activities of each phase in safety life cycle. In addition, we introduce safety integrity level(SIL) which is used for verifying the safety integrity requirements of E/E/PE system and perform a case study to estimate hardware SIL by FMEDA. The SIL is evaluated by two criteria. One of them is the architectural constraints which restrict the maximum SIL by combination of SFF and HFT. The other is the probability of failure which is classified into PFD and PFH based on frequency of demand and calculated by safe or dangerous failure rates.

• Proceedings of the Safety Management and Science Conference
• /
• 2004.11a
• /
• pp.277-287
• /
• 2004

This study presents a method of quality category classification by safety, maturity, complexity, and what types and extent of controls and verifications are applied to specific products and services during the various stages of a nuclear facility life cycle. All products, services and processes have various controls and verifications built in to ensure they perform their functions satisfactorily. The highest grade should require the most stringent application of the quality assurance requirements ; while, the lowest grade should require the least stringent. When products or services are modified, the assigned grade of quality assurance requirements could become more stringent or less stringent depending on the significance in nuclear safety. Applying QA program always costs money, and they should be applied and focused to the extent where necessary and not applied or applied to a lesser degree for less important activities. An efficient QA program should be developed to satisfy the necessary requirements and to ensure the required confidence in quality, but without unnecessary stipulations. Not all the requirements of QA standard must be applied identically to all products and services which are to be provided.

• Journal of the Korea Safety Management & Science
• /
• v.11 no.3
• /
• pp.19-26
• /
• 2009

It is becoming more and more important to develop safety-critical systems with special attention. Examples of the safety-critical systems include the mass transportation systems such as high speed trains, airplanes, ships and so forth. Safety critical issues can also exist in the development of atomic power plants that are attracting a great deal of attention recently as oil prices are sky-rocketing. Note that the safety-critical systems are in general large-scale and very complex for which case the effects of adopting the systems engineering (SE) approach has been quite phenomenal. Furthermore, safety-critical requirements should necessarily be realized in the design phase and be effectively maintained thereafter. In light of these comments, we have considered our approach to developing safety-critical systems to be based on the method combining the systems engineering and safety management processes. To do so, we have developed a design environment by constructing a whole life cycle model in two steps. In the first step, the integrated process model was developed by integrating the SE (ISO/IEC 15283) and systems safety (e.g., hazard analysis) activities and implemented in a computer-aided SE tool environment. The model was represented by three hierarchical levels: the life-cycle level, the process level, and the activity level. As a result, one can see from the model when and how the required SE and safety processes have to be carried out concurrently and iterately. Finally, the design environment was verified by the computer simulation.

• Journal of the Korea Safety Management & Science
• /
• v.15 no.1
• /
• pp.11-19
• /
• 2013

In modern systems design and development, one of the key issues is considered to be related with how to reflect faithfully the stakeholder requirements including customer requirements therein, thereby successfully implementing the system functions derived from the requirements. On the other hand, the issue of safety management is also becoming greatly important these days, particularly in the operational phase of the systems under development. An approach to safety management can be based on the use of the failure mode effect and analysis (FMEA), which has been a core method adopted in automotive industry to reduce the potential failure. The fact that a successful development of cars needs to consider both the complexity and failure throughout the whole life cycle calls for the necessity of applying the systems engineering (SE) process. To meet such a need, in this paper a method of FMEA is developed based on the SE concept. To do so, a process model is derived first in order to identify the required activities that must be satisfied in automotive design while reducing the possibility of failure. Specifically, the stakeholder requirements were analyzed first to derive a set of functions, which subsequentially leads to the task of identifying necessary HW/SW components. Then the derived functions were allocated to appropriate HW/SW components. During this design process, the traceability between the functions and HW/SW components were generated. The traceability can play a key role when FMEA is performed to predict the potential failure that can be described with the routes from the components through the linked functions. As a case study, the developed process model has been applied in a project carried out in practice. The results turned out to demonstrate the usefulness of the approach.

• Proceedings of the KSR Conference
• /
• 2007.11a
• /
• pp.683-688
• /
• 2007

The importance of reliability and safety, recently, shows a tendency to increases in railway system constructions and projects. At the point of view of safety, especially, the railway authority proposes an establishment of the safety case that is the documented demonstration that products comply with the specific safety requirements in railway industry. In case of reliability activities, there is no systematic documented demonstration in the railway industry. At this circumstance, this study presents the establishment of Reliability, Availability and Maintainability Case for railway system based on the MoD(Ministry of Defence) 00-42. This RAM Case will support that systems and products produced from suppliers or manufacturers meet the specific RAM requirements during the system life cycle(i.e, from design to operation & maintenance) through systematic process and evidences. Also, it is expected that railway system operations will be managed and supported from reliability activities in accordance with RAM Case.

• Journal of the Society of Disaster Information
• /
• v.5 no.2
• /
• pp.10-21
• /
• 2009

This study contains the fire protection safety of the public-utilization shops. The toll of fires in the public-utilization shops is so heavy in spite the less occurency. The shops are mostly compartmented into small rooms by partition wall which hinders the evacuation of the people on fire. This study provides additional requirements on the fire safety of the public-utilization shops needed for human life and property.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.12
• /
• pp.543-548
• /
• 2017

In recent years, the importance of the safety of medical device software has been emphasized because of the function and role of the software among components of the medical device, and because the operation of the medical device software is directly related to the life and safety of the user. To this end, various standards have been set up that provide activities that can effectively ensure the safety of medical devices and provide their respective requirements. The activities that standards provide to ensure the safety of medical device software are largely divided into the development life cycle of medical device software and the risk management process. These two activities should be concurrent with the development process, but there is a limitation that the risk management requirements to be performed at each stage of the medical device software development life cycle are not classified. As a result, developers must analyze the association of standards directly to develop risk management activities during the development of medical devices. Therefore, in this paper, we analyze the relationship between medical device software development life cycle and risk management process, and extract risk management requirement items. It enables efficient and systematic risk management during the development of medical device software by mapping the extracted risk management requirement items to the development life cycle based on the analyzed associations.

• Proceedings of the KSR Conference
• /
• 2010.06a
• /
• pp.1118-1125
• /
• 2010

This paper presents the methods to acquire the Safety Certificate from Independent Safety Assessment based on the IEC standard62279 which is commonly applied to railway system for Automatic Train Control(ATC) system in accordance with Urban Maglev project. This also shows approach methods and relative activities for project life-cycle to accomplish and ensure the system requirements of ATC system, RAMS and S/W quality activities. Furthermore, the key tasks conducted with ISA are noted in detail. These kind of activities for software quality of ATC system to obtain Safety Certificate could be a CASE model to improve the quality of domestic railway system and products, and also contribute to the growth of railway business and toward the achievement of overseas' railway signaling markets.

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