ASIL Decomposition & Tailoring - Functional Safety (ISO 26262)

ASIL Decomposition: ISO 26262 Part 9 Clause 5

ASIL Decomposition Principle

  Original requirement: ASIL-D
  ├── Too expensive / complex to implement in one element
  └── Solution: split into two independent, redundant channels

  ASIL Decomposition (Part 9 Table 5):
  ASIL-D → ASIL-D(D) + ASIL-D(D)    (same ASIL in both; no credit for redundancy)
  ASIL-D → ASIL-C(C) + ASIL-C(C)    (NOT valid — sum must be ≥ original)
  ASIL-D → ASIL-B(D) + ASIL-D(B)    (VALID: B+D gives D with A/B suffix)

  Valid decompositions from ISO 26262 Part 9 Annex C:
  ASIL-D = ASIL-A(D) + ASIL-D(A)
  ASIL-D = ASIL-B(D) + ASIL-D(B)
  ASIL-D = ASIL-C(D) + ASIL-D(C)
  ASIL-C = ASIL-A(C) + ASIL-C(A)
  ASIL-C = ASIL-B(C) + ASIL-C(B)
  ASIL-B = ASIL-A(B) + ASIL-B(A)

  Notation: ASIL-X(Y) means "ASIL-X requirement allocated to element,
  which is part of an ASIL-Y decomposition"
  The suffix (Y) is NOT the element's ASIL — it is the original ASIL

Decomposition Requirements

Rule	Requirement	Consequence of Violation
Independence	The two channels must be sufficiently independent	Common cause failure (CCF) defeats decomposition — MUST do DFA
No shared software	ASIL-B(D) and ASIL-D(B) channels must have no shared code	Shared bug invalidates decomposition
No shared hardware	No shared power supply, clock, SRAM between decomposed elements	Single hardware fault kills both channels
No shared design	Different teams, different methods, or diverse implementations	Same design flaw in both channels
DFA required	Dependent Failure Analysis must confirm independence	Without DFA, decomposition claim is not valid

Decomposition Example: AEB ASIL-D

Markdownasil_decomp_example.md

# ASIL Decomposition: Emergency Braking Request

## Original Requirement (SG-01)
[ASIL-D] FCAB shall only issue AEB request when collision imminent

## Decomposition: ASIL-D = ASIL-C(D) + ASIL-D(C)

### Channel A (ASIL-C(D)): Primary Safety Monitor
- Function: Validate AEB request before forwarding to brake ECU
- Implementation: Safety monitor in FCAB Domain Controller main CPU
- ASIL development: ASIL-C methods (per Part 6 Table 1)
- Requirements allocated:
  * [ASIL-C(D)] Monitor shall check radar + camera confidence before enabling AEB

### Channel B (ASIL-D(C)): Independent Watchdog / Arbiter
- Function: Independent second check; can override Channel A
- Implementation: Separate MCU (external watchdog or second core) with independent sensors
- ASIL development: ASIL-D methods for this element
- Requirements allocated:
  * [ASIL-D(C)] Watchdog shall independently verify AEB conditions from redundant sensor path

## Independence Evidence (DFA mandatory)
- Different silicon (two separate MCUs)
- Different power domain (separate voltage regulators)
- No shared software code or libraries
- Different teams developed Channel A and B
- DFA report ref: DFA-FCAB-001 confirms independence at hardware and software level

## Result
Combined decomposed system achieves ASIL-D coverage:
- Random failures: covered by redundancy (PMHF calculation includes both)
- Systematic failures: ASIL-C and ASIL-D methods applied to respective channels

Summary

ASIL decomposition is not a shortcut to lower development cost — it is a legitimate architectural pattern for distributing safety requirements across two independent channels when a single element cannot meet the full ASIL requirement alone. The critical constraint is independence: if the two channels share any common cause of failure (shared power supply, shared code, shared design team, shared physical PCB area), the decomposition is invalid and the full ASIL-D requirement applies to both. The Dependent Failure Analysis (DFA) must explicitly verify independence — it is the evidence that the decomposition claim is justified.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.