Why it exists
Electronics now steer, brake and accelerate vehicles. Random hardware faults and systematic software errors can cause accidents. ISO 26262 defines how to develop E/E systems so that this risk is acceptably low.
What the key ideas are
- HARA (Hazard Analysis and Risk Assessment): for each hazardous event, rate severity, exposure and controllability.
- ASIL (Automotive Safety Integrity Level): QM, A, B, C, D — derived from those ratings; D is the most demanding.
- Safety goals → functional safety concept → technical safety concept → hardware and software requirements.
- Safety case: the argument plus evidence that the system is safe enough.
HARA combines severity, exposure and controllability; QM indicates that no ASIL is assigned.
How it shapes engineering
Higher ASILs require stricter methods (reviews, testing depth, tool qualification), hardware with high diagnostic coverage (e.g. lockstep cores, ECC) and architectural measures like redundancy. ASIL decomposition splits a requirement over independent redundant elements.
Best practices
- Do the HARA early with representative driving situations; involve experts from vehicle dynamics and operations.
- Keep safety requirements traceable from goals down to tests.
- Maintain the safety case across software updates — not just at start of production.
Common pitfalls
- Treating ISO 26262 as documentation work after development.
- ASIL decomposition without real independence (shared power, shared software).