ISO 26262: Software Architectural Design — Clause 7 Principles That Get Checked

Date
2027-02-24
Location
Online
Host
Zach L

About this event

A live 30-minute expert session on Software Architectural Design — Clause 7 Principles That Get Checked (ISO 26262 — Automotive Functional Safety). What We'll Cover: What software architectural design covers in Part 6 Clause 7 and its place before unit design The method step by step: component decomposition, interface definition, and applying Table 3 principles How restricted coupling, size limits, and scheduling choices map to the architecture spec produced Common mistakes: architectures drawn after the code exists and metrics with no thresholds The architecture-to-requirement allocation and analysis evidence assessors trace Related topics: software architecture · iso 26262 clause 7 · coupling and cohesion · hierarchical design · component interfaces · cyclomatic complexity · architecture

Topics

Registration

View event page

About Functional Safety Foundations

This online session delivers expert-led instruction on the regulatory landscape and implementation approach for Functional Safety Foundations.

The cross-sector fundamentals underlying every functional safety standard: risk as severity × likelihood, the safety function concept, integrity levels, the safety lifecycle, and the split between random and systematic failures.

What it regulates

Shared vocabulary and reasoning: hazard → risk → risk reduction allocation → safety requirement → verified implementation → maintained integrity in operation.

Who must comply

Everyone entering the field — the conceptual base of the entire catalog.

Key requirements of Functional Safety Foundations

  • Hazard and risk fundamentals
  • Safety function anatomy: sensor-logic-actuator with defined safe state
  • Integrity ladders (SIL/PL/ASIL/DAL) as risk-reduction currencies
  • Random vs systematic failure treatment
  • Lifecycle and management of functional safety incl. competence

Key concepts: Functional Safety Foundations

Random vs systematic
Hardware wear-out/chance failures quantified statistically versus design/process errors controlled by rigor.
Risk reduction allocation
Distributing required risk reduction among mechanical design, safeguards, control functions and procedures.
Functional safety management
Planning, competence, documentation and assessment wrapped around technical work.
Safe state
The defined condition a function drives the equipment to on demand or fault.

Frequently asked questions: Functional Safety Foundations

Why can't testing alone prove safety?

Rare-event targets (like 1e-7/h) are unverifiable by test duration, and systematic errors evade random testing — hence the standards' dual machinery of quantified hardware analysis plus process rigor and independent assessment.

Standard information based on the published text of Functional Safety Foundations. Event content is provided by the host. For authoritative guidance, consult the official standard body.