How to mange functional safety under ISO 26262

Posted: November 19, 2026

In this article

ISO 26262 is the functional safety standard for road vehicles. Its goal is to reduce the risk of harm caused by malfunctioning electrical and electronic (E/E) systems. Managing it well means treating safety as work that runs through the whole product lifecycle, not as a check at the end of development.

This post is based on the SystemWeaver white paper SDV Applications for Automotive ECUs by Ahmed Majeed Khan, which shows how a Software Product Lifecycle Management (S-PLM) approach supports ISO 26262, ISO/SAE 21434 and ASPICE compliance in software-defined vehicles.

What the standard asks you to do

Functional safety work under ISO 26262 follows a clear chain of activities:

  • Hazard analysis and risk assessment (HARA): potential hazards are identified, using guidewords and a systematic review of operational situations.
  • Safety goals: these are established from the HARA and state what the system must not allow to happen.
  • Functional and technical safety concepts: the functional safety concept defines the scope, and the technical safety concept specifies the required safety mechanisms as safety requirements.
  • FTA and FMEA: fault tree analysis (deductive) and failure mode and effects analysis (inductive) make the design more robust.
  • Safety case: test and verification results are summarized as a structured argument, often using Goal Structuring Notation (GSN), that the system is safe to use.

A V-model with traceability at every stage

As summarized in section III.B of the white paper, ISO 26262 is built around a strict V-model that covers the full lifespan of the product. In the concept phase, the item is defined and the hazard analysis determines the functional safety concept. During product development, safety requirements are decomposed step by step into system, hardware and software requirements. Safety work then continues through production, operation and decommissioning. Traceability is required at every one of these stages.

Where it gets difficult

The standard provides the theoretical framework. The practical challenge is keeping everything connected while the design changes. Every safety goal must stay linked to the requirements derived from it, the analyses that support it and the tests that verify it, across many iterations. In software-defined vehicles this is harder, because safety requirements overlap with cybersecurity requirements under ISO/SAE 21434 and with process requirements under ASPICE.

What this looks like in practice

SystemWeaver’s case study in section IV of the white paper uses an immobilizer manager, an anti-theft function, as its example. A hazardous event, such as a thief cloning a key fob and starting the engine, is captured in the HARA and mapped to a safety goal: the immobilizer must prevent unauthorized engine start. A safety graph then shows how hazards, hazardous events, safety goals and safety requirements relate to each other, and traces failure modes through to defined safe states. The aim is end-to-end traceability, so that critical safety goals are not overlooked as the design iterates.

Sources

You may also be interested in

  • Abstract orange and blue

    How to mange functional safety under ISO 26262

    ISO 26262 is the functional safety standard for road vehicles. Its goal is to reduce the risk of harm caused by malfunctioning electrical and electronic (E/E) systems. Managing it well means treating safety as work that runs through the whole product lifecycle, not as a check at the end of development. This post is [...]

  • Nodes horizon

    White Paper: Sourcing a Toolchain for Software- and AI-Defined Products

    Download this White Paper as a PDF Overview Executive Summary A toolchain succeeds or fails on whether people adopt it, not on its feature list. Earn buy-in step by step, put your engineering data in context, and the technology will follow. Products in every industry are becoming software-defined (SDP) and, increasingly, AI-defined [...]

  • Abstract technology

    White Paper: Before You Choose a Model, Engineer the Context

    Download this White Paper as a PDF EXECUTIVE SUMMARY I. The Decisive AI Question Is Not Which Model In systems engineering, the decisive question is not which AI model to use. It is what the model will be allowed to read, retrieve and reason over. AI value flows through the layer that [...]