Practical experience with safety analyses at the software architectural level

In this article, we show how to perform HAZOP and fault tree analyses at the software architectural level and describe our experiences with these analysis methods.

 

Safety analyses at the software architecture level

Table of contents

  • Motivation
  • Experiences with the HAZOP method at the software architectural level
  • Experiences with the FTA method at the software architectural level
  • Lessons learned
 

Executive summary

The new automotive safety standard ISO 26262 2nd Edition was approved at the end of 2018. Part 6 (Product development at the software level) contains a new informative appendix titled 'Appendix E – Application of safety analyses and analyses of dependent failures at the software architectural level'. The aim of safety analyses at the software architectural level is to examine and confirm the consistency of the assigned ASIL.
For an overview of possible safety analyses, refer, for example, to ISO/IEC 31010 'Risk management – Risk assessment techniques'. Among other things, this standard describes the bottom-up (inductive) HAZOP method and the top-down (deductive) fault tree analysis (FTA) method.

 

Resource type
Tech paper

 

Related content

EB’s safety solution: EB tresos Safety

 





yes

I agree that my usage behaviour is being documented for optimization purposes. I would like to receive additional Information on EB products and events. Via the unsubscribe link at the bottom of our mailings I can withdraw my consent. For more information click here.

yes

I would also like to subscribe to the EB Newsletter.

captcha