| Clause | Title | Key Content |
|---|---|---|
| Cl. 4 | General | Terms, definitions, applicability criteria |
| Cl. 5 | SOTIF-related item definition | Functional description; operational design domain (ODD) |
| Cl. 6 | Hazard analysis and risk assessment | SOTIF-specific HARA; acceptance criteria |
| Cl. 7 | Design measures | Algorithm requirements; sensor requirements; HMI requirements |
| Cl. 8 | V&V measures | Scenario-based testing; simulation; field testing |
| Cl. 9 | Residual risk evaluation | Confidence building; statistical evidence |
ISO 21448 Standard Structure
SOTIF Process Overview
ISO 21448 Process Flow
[1] Define SOTIF Item
- Functional description of ADAS feature
- Operational Design Domain (ODD)
- Boundaries: speed, weather, road type
|
[2] Identify Hazards
- Sensor limitations (camera, radar, lidar)
- Algorithm insufficiencies (false pos/neg)
- Human factors (misuse, over-trust)
- Triggering conditions
|
[3] Define Acceptance Criteria
- Scenario coverage targets
- False positive/negative rate limits
- Residual risk threshold
|
[4] Design Measures
- Algorithm improvements
- Sensor fusion
- HMI warnings
|
[5] V&V
- Simulation (known scenarios)
- Real-world testing
- Statistical evidence
|
[6] Evaluate Residual Risk
- Acceptable? Release
- Not acceptable? Back to [4]Key SOTIF Concepts
| Term | Definition | Example |
|---|---|---|
| Operational Design Domain (ODD) | Set of conditions within which the ADAS function is designed to operate | AEB: 10-80 km/h, dry road, visibility > 100m, no snow |
| Triggering condition | Environmental or operational condition that causes hazardous behaviour | Heavy rain reducing camera detection range below AEB activation distance |
| Functional insufficiency | Limitation of the intended algorithm that can cause unsafe behaviour | AEB algorithm does not distinguish stationary car from road sign |
| Known safe scenario | Scenario within ODD; tested; behaviour verified safe | AEB at 50 km/h approaching stationary car -- detected and brakes correctly |
| Known unsafe scenario | Scenario where hazardous behaviour has been identified and confirmed | AEB approaching pedestrian in fog at 70 km/h -- not detected |
| Unknown scenario | Scenario not yet identified in analysis -- coverage gap | Any scenario not yet tested or simulated |
Summary
The ISO 21448 framework is built around the concept of the Operational Design Domain (ODD) -- the specific conditions under which the ADAS function is designed and validated. Everything within the ODD must be verified safe; everything outside the ODD must trigger appropriate warnings or system deactivation. The known/unknown, safe/unsafe scenario matrix is the practical tool for tracking this: the goal of SOTIF V&V is to move scenarios from "unknown" to "known safe" by testing them, while ensuring the population of "known unsafe" scenarios is reduced through design improvements until the residual risk is acceptable.
🔬 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.