Understanding the Level of Abstraction in ISO 26262
To illustrate this, the qualitative analysis of requirements can be performed at multiple levels: A system level analysis to ensure…
Random Failure vs. Systematic Failure: Through the Looking Glass
Put more simply, systematic failures are mistakes or oversights in the design. A systematic failure is caused by human error….
Methods to Navigate the Complex Landscape of Embedded Software
I’ll be presenting on this topic at the upcoming medini analyze User Conference scheduled to be held in Troy, MI on…
Software Safety Analysis: An Overview
In Part 4 and Part 5, clauses 4.7 and 5.7 respectively, the ISO 26262 standard requires engineers to perform safety…
How can we specify safety-critical time intervals?
So what does the ISO 26262 standard say? Part 1, 1.44 defines FRTI as, “time-span from the detection of a…
The Safety FMEA
One can argue that safety is something needed to satisfy the customer. Notwithstanding, so is comfort, reliability, performance, etc. These…
Fault Tree Analysis: Getting to the Root Cause
The basic question when doing a Fault Tree Analysis is “What lower-level faults or failures could cause a hazard?” The…
Setting the Stage for Failure Diagnostics
Recall the purpose of the HARA is to identify hazardous events, classify them and develop safety goals to prevent unreasonable…