| Level | Definition | Examples | Notes |
|---|---|---|---|
| S0 | No injuries | Cosmetic damage; no occupant harm | Results in QM regardless of E and C |
| S1 | Light and moderate injuries | Whiplash; minor lacerations; light concussion | Reversible injuries; full recovery expected |
| S2 | Severe and life-threatening injuries (survival probable) | Broken bones; serious head injury; organ damage | Survival likely but long recovery; potential permanent disability |
| S3 | Life-threatening injuries (survival uncertain) or fatal | High-speed collision; head-on impact; pedestrian fatality | Most conservative class; fatalities or near-certain fatal injuries |
Severity Classification (S0–S3)
Exposure Classification (E0–E4)
| Level | Definition | Frequency | Examples |
|---|---|---|---|
| E0 | Incredible | < once in vehicle lifetime | Theoretical failure mode; practically impossible scenario |
| E1 | Very low probability | < once per year | Rare events; ice road in tropical country |
| E2 | Low probability | A few times per year | Winter driving in temperate climate; mountain roads |
| E3 | Medium probability | Once per month or week | City driving in rainy conditions; regular highway use |
| E4 | High probability | Daily exposure or continuous | Highway driving; normal city traffic; parking manoeuvres |
Controllability Classification (C0–C3)
| Level | Definition | Examples | Driver Population |
|---|---|---|---|
| C0 | Controllable in general | Almost all drivers can avoid hazard | 99%+ of drivers |
| C1 | Simply controllable | Most drivers can avoid with normal reactions | 99% of drivers |
| C2 | Normally controllable | Average driver can avoid with attentive reaction | 90% of drivers |
| C3 | Difficult to control or uncontrollable | Less than 90% of drivers can avoid; time < 1s; surprise | < 90% of drivers |
Justification of S, E, C Parameters
Markdownsec_justification.md
# S/E/C Justification: Inadvertent AEB Activation at Highway Speed
## Severity = S3 — JUSTIFICATION
Worst-case scenario: AEB activates at 130 km/h with following vehicle at 2s gap.
Following vehicle impact speed: 130 × 2 - (deceleration × t²/2) ≈ 80 km/h delta-v.
Reference: EuroNCAP data shows rear impacts at 80 km/h delta-v: fatality probability > 50%.
ISO 26262 S3 applies when fatality or near-certain severe injury is the credible outcome.
→ S3 confirmed by reference to accident database (GIDAS, NASS/CDS data).
## Exposure = E4 — JUSTIFICATION
AEB operates at all speeds > 7 km/h. Highway driving: average German driver ≈ 30% of
drive time on motorway at > 100 km/h (ADAC driving data, 2022).
Continuous exposure: every motorway journey is a potential exposure event.
E4 definition: '≥ once per day or frequent / continuous' → confirmed.
→ E4 confirmed.
## Controllability = C3 — JUSTIFICATION
At 130 km/h, following vehicle gap of 2s = 72 m. After AEB activation:
- Deceleration: up to 0.8g
- Time for following driver to react: 1.2s (average brake reaction time)
- Distance to stop: 72 m at 130 km/h + reaction distance
Reference: Human Factors data (Petzoldt, 2014): < 10% of drivers can avoid rear-end
collision when leading vehicle decelerates at 0.8g from 130 km/h at 2s gap.
→ C3 confirmed: < 90% controllable.Summary
The S, E, C parameters must be supported by objective evidence — accident databases (GIDAS, NASS/CDS, CARE), human factors research, driving statistics, and vehicle dynamics calculations. Using 'worst credible case' for severity (not theoretical maximum, not most likely) is the ISO 26262 guidance. Controllability is particularly difficult to justify — it requires human factors expertise and reference to published research on driver response times. A common error: applying C3 to all hazards without justification, resulting in inflated ASIL levels. An equally common error: applying C1 without justification to reduce ASIL and save development cost — this will be challenged by the assessor.
🔬 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.