ISO 26262: Software Safety Requirements and Architecture

Date: 2026-10-27
Location: Online
Host: Zach L

About this event

A live 30-minute expert session on Software Safety Requirements and Architecture, part of the ISO 26262 track from Critical Systems Analysis. Recurs monthly. Related topics: software safety requirements and architecture · software · safety · requirements · architecture · functional safety · ASIL · HARA · safety lifecycle · safety goal · functional safety concept · technical safety requirements · hardware metrics · SPFM · LFM · PMHF. Browse the whole track: ISO 26262](https://luma.com/critical-systems-analysis?tag=iso-26262)) All ISO 26262 sessions (43 more): ISO 26262: The Role of the Safety Manager](https://luma.com/critical-systems-analysis?tag=iso-26262-the-role-of-the-safety-manager)) · ISO 26262: Writing Technical Safety Requirements (TSRs)](https://luma.com/critical-systems-analysis?

Topics

Registration

View event page

About ISO 26262 (Automotive Functional Safety)

This online session delivers expert-led instruction on the regulatory landscape and implementation approach for ISO 26262.

ISO 26262 adapts functional safety to road vehicles: a lifecycle from item definition and hazard analysis (HARA) through system, hardware and software development, production, operation and decommissioning, with integrity expressed as ASIL A-D.

What it regulates

Safety lifecycle management, HARA and ASIL determination, functional and technical safety concepts, hardware metrics (SPFM/LFM/PMHF), software development rigor, supporting processes (configuration, tools, safety analyses) and confirmation measures.

Who must comply

OEMs, tier suppliers, and semiconductor vendors delivering E/E systems for series production road vehicles.

Key requirements of ISO 26262

Part 3: concept phase — item definition, HARA, functional safety concept

Part 4: system-level development and technical safety concept

Part 5: hardware — architectural metrics and evaluation of random failures

Part 6: software development

Part 8: supporting processes incl. tool qualification and qualification of components

Part 9: ASIL-oriented analyses (decomposition, dependent failures)

Part 11: application to semiconductors

Key concepts: ISO 26262

Safety goal

Top-level safety requirement per hazardous event, parent of the functional safety concept.

ASIL (A-D)

Automotive Safety Integrity Level from HARA parameters severity, exposure and controllability — D the most stringent.

HARA

Hazard Analysis and Risk Assessment on vehicle-level hazardous events determining ASILs and safety goals.

ASIL decomposition

Splitting a requirement across sufficiently independent elements at lower ASILs with evidence of independence.

SPFM/LFM/PMHF

Hardware architectural metrics: single-point and latent fault coverage plus probabilistic metric targets per ASIL.

Frequently asked questions: ISO 26262

What is a safety element out of context (SEooC)?

A component (chip, software library, sensor) developed against assumed requirements before the vehicle context exists; the integrator must validate the assumptions of use against the actual item.

Does ISO 26262 cover autonomous driving hazards?

It covers malfunction-caused hazards. Hazards from functional insufficiencies without failure (perception limits, scenario gaps) are the domain of ISO 21448 SOTIF, used together with 26262 for automated driving.

How do ASIL and SIL relate?

They are siblings from IEC 61508 but not convertible: ASIL derives from automotive-specific S/E/C parameters and drives different hardware metrics and process tables. Cross-domain reuse requires re-derivation, not a mapping table.