CONCEPT PHASE (Part 3)
├── Item definition
├── Hazard Analysis & Risk Assessment (HARA)
├── Safety Goals (ASIL rating)
└── Functional Safety Concept (FSC)
│ │
▼ ▲
SYSTEM LEVEL (Part 4) SYSTEM INTEGRATION TEST
├── Technical Safety Requirements ├── System safety validation
├── System architecture design └── ASIL-appropriate test methods
└── Hardware-Software Interface (HSI)
│ │
▼ ▲
HARDWARE LEVEL (Part 5) HW INTEGRATION TEST
├── Hardware design ├── Diagnostic coverage verification
├── SPFM/LFM/PMHF calculation └── Random failure rate test
└── Hardware safety analysis
│ │
▼ ▲
SOFTWARE LEVEL (Part 6) SW INTEGRATION TEST
├── Software safety requirements ├── Interface testing
├── Software architecture ├── Back-to-back testing
├── Unit design └── Coverage measurement
└── Unit implementation
│
▼
SW UNIT TEST (MC/DC, etc.)
Supporting processes (Part 8) run throughout all phases:
configuration management, tool qualification, documentation, reviewsISO 26262 V-Model and Safety Lifecycle
Phase-by-Phase Overview
| Phase | ISO 26262 Part | Duration (typical) | Key Output |
|---|---|---|---|
| Concept | Part 3 | 3–6 months | HARA, Safety Goals, FSC |
| System development | Part 4 | 6–12 months | TSRs, system architecture, HSI specification |
| Hardware development | Part 5 | 6–12 months | HW design, SPFM/LFM/PMHF report |
| Software development | Part 6 | 12–24 months | SW architecture, code, unit tests, integration tests |
| Integration & validation | Parts 4–6 | 3–6 months | Integration test reports, safety validation report |
| Release | Part 2 | 1–2 months | Safety case, functional safety assessment |
| Production | Part 7 | Vehicle lifetime | Production monitoring, field data collection |
| Decommission | Part 7 | — | End-of-life safety considerations |
Key Work Products per Phase
| Work Product | Phase | ASIL-D Required? | Owner |
|---|---|---|---|
| Item Definition | Concept | Yes | System Architect |
| HARA Report | Concept | Yes | Safety Manager |
| Safety Goals | Concept | Yes | Safety Manager |
| Functional Safety Concept (FSC) | Concept | Yes | Safety Engineer |
| Technical Safety Requirements (TSRs) | System | Yes | Systems Engineer |
| Hardware Safety Analysis (FMEA/FTA) | Hardware | Yes | HW Safety Engineer |
| Software Safety Requirements (SSRs) | Software | Yes | SW Safety Engineer |
| Software Architectural Design Doc (SWDD) | Software | Yes | SW Architect |
| Unit Test Report (with MC/DC coverage) | Software | Yes | SW Developer |
| Safety Case | Release | Yes | Safety Manager |
| Functional Safety Assessment | Release | Yes (by independent assessor) | External Assessor |
Summary
The ISO 26262 V-model is not just a documentation structure — it defines the verification and validation activities that must occur at each level before proceeding to the next. The left side of the V represents development (requirements → design → implementation); the right side represents testing against each level of requirements. A key practical discipline: requirements at each level must be traceable to the level above and the level below. A safety goal without a traceable FSR, a TSR without a traceable safety goal, or a software requirement without a traceable TSR is a safety gap that an assessor will flag during the functional safety assessment.
🔬 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.