Abstract
Safety analysis is often performed independent of the system design life cycle, leading to inconsistency between the system design and the safety artifact. Additionally, the process of generating safety artifacts is manual, time-consuming, and error-prone. As a result, safety analysis often requires re- work, is expensive, and increases system development time. Several model-based systems engineering (MBSE) approaches have been developed to automatically generate certain safety artifacts. However, these approaches only cover part of the system design and safety life cycle. To truly leverage the benefits of MBSE, system design must be undertaken together with safety analysis for the entire life cycle, and multiple safety artifacts must be generated from the same model. Moreover, MBSE approaches that require a model transformation between the system design and the safety model suffer from the inability to automatically reflect changes made to a safety artifact in the system and the safety model. This paper presents a framework to integrate the entire system design and safety life cycle using an MBSE approach. Both the system design and the safety data are captured in a single SysML model, from which safety artifacts such as failure modes and effects analysis (FMEA) tables and fault trees are automatically generated. This framework ensures consistency between the system design and the safety analysis by requiring no model transformation, thus reducing the resources required for safety analysis. The proposed Integrated System Design and Safety (ISDS) framework comprises three phases that together cover the entire system design and safety life cycle. In this paper, the application of Phase 1 of the framework to a real-world case study is demonstrated.
Highlights
The need for greater functionality and a rapid decrease in the size of hardware components has led to the design of complex systems with highly interdependent hardware/software architectures
A script traverses the SysML models to generate the reliability diagram for each failure case. While this method only focuses on generating a single safety artifact and is limited in its applicability over the entire safety life cycle, it demonstrates that a safety artifact can be automatically generated by embedding the required safety data directly into the SysML model without the need for a model transformation
Integrated System Design and Safety (ISDS) FRAMEWORK: PHASE 1 DESCRIPTION The description for each stage in the ISDS framework starts with the design life cycle-related activity, followed by the safety life cycle activity and the SysML modeling activity
Summary
The need for greater functionality and a rapid decrease in the size of hardware components has led to the design of complex systems with highly interdependent hardware/software architectures. To address the limitations highlighted above, researchers have adopted a model-based systems engineering (MBSE) approach to safety analysis This improves the completeness and consistency in system development [17], fosters improved communication across design teams [17], provides added traceability between different models of the system [18], and makes integration with other engineering analyses easy [19]. Safety artifacts can be automatically generated to reduce the development time and resources required for safety assessment and design changes These benefits of MBSE and SysML can be leveraged to resolve the problems in safety analysis and to automatically generate safety artifacts at different stages of the system design life cycle.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
