Abstract
ISO 26262, a functional-safety standard, uses Automotive Safety Integrity Levels (ASILs) to assign safety requirements to automotive-system elements. System designers initially assign ASILs to system-level hazards and then allocate them to elements of the refined system architecture. Through ASIL decomposition, designers can divide a function’s safety requirements among multiple components. However, in practice, manual ASIL decomposition is difficult and produces varying results. To overcome this problem, a new tool automates ASIL allocation and decomposition. It supports the system and software engineering life cycle by enabling users to efficiently allocate safety requirements regarding systematic failures in the design of critical embedded computer systems. The tool is applicable to industries with a similar concept of safety integrity levels.
Highlights
A new tool automates Automotive Safety Integrity Levels’ allocation and decomposition
We developed automatic Automotive Safety Integrity Levels (ASILs) decomposition and allocation as an extension to HiP-HOPS, an advanced safety analysis and design optimization tool used at several large automotive companies.[6,7]
There has been some discussion in the functional-safety community concerning the definition of the most realistic ASIL-dependent cost function, and people have proposed many theories
Summary
Luís da Silva Azevedo, David Parker, Martin Walker, and Yiannis Papadopoulos, University of Hull. A new tool automates Automotive Safety Integrity Levels’ allocation and decomposition It supports the system and software engineering life cycle by letting users allocate safety requirements regarding systematic failures in the design of critical embedded computer systems. We’ve developed a tool that supports ISO 26262 by employing ASILs to help its users manage topdown allocation and verification of safety requirements regarding systematic failure—including software failure—during the design of complex systems. It will likely support any similar future standards derived from ISO 26262 in other application domains and generally support the design of safetycritical systems in their systems-engineering life cycle
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.