| Deliverable | Content | ISO 21448 Clause |
|---|---|---|
| Item definition + ODD | LKA functional spec; ODD YAML | Cl. 5 |
| TC register | 15+ triggering conditions across taxonomy | Cl. 6.3 |
| SOTIF HARA | Hazard table with severity/probability/controllability | Cl. 6 |
| Acceptance criteria | Quantitative targets per high-risk hazard | Cl. 6.5 |
| V&V plan | Simulation + track + public road plan | Cl. 8 |
| Residual risk argument | GSN safety argument; evidence summary | Cl. 9 |
Lab: Complete SOTIF Analysis for LKA
Exercise 1: LKA SOTIF Analysis Pipeline
"""Complete SOTIF analysis pipeline for Lane Keeping Assist."""
LKA_ODD = {
"speed_kmh": {"min": 60, "max": 130},
"road_types": ["motorway", "dual_carriageway"],
"lane_marking": "visible_and_painted",
"weather": {"rain_max_mmh": 2, "fog_vis_min_m": 200},
"lighting": ["daylight", "well_lit_night"],
}
LKA_TC_REGISTER = [
{"id":"LKA_TC_001","cat":"Road", "desc":"Faded lane markings","severity":2},
{"id":"LKA_TC_002","cat":"Road", "desc":"Construction zone: temporary markings","severity":3},
{"id":"LKA_TC_003","cat":"Weather", "desc":"Rain streaks on camera","severity":2},
{"id":"LKA_TC_004","cat":"Lighting","desc":"Sun glare on wet road surface","severity":3},
{"id":"LKA_TC_005","cat":"Road", "desc":"Multiple parallel road markings","severity":2},
{"id":"LKA_TC_006","cat":"Human", "desc":"Driver inattention: not monitoring steering","severity":3},
{"id":"LKA_TC_007","cat":"Target", "desc":"Road edge matching lane marking width","severity":2},
{"id":"LKA_TC_008","cat":"Human", "desc":"Driver over-corrects during LKA correction","severity":2},
]
LKA_ACCEPTANCE_CRITERIA = [
{"id":"AC_LKA_001","desc":"Lane detection loss < 0.5% in dry daylight","target": 0.005},
{"id":"AC_LKA_002","desc":"False intervention rate < 0.1/100km","target": 0.001},
{"id":"AC_LKA_003","desc":"Scenario coverage > 90%","target": 0.90},
]
print("LKA SOTIF Analysis Summary:")
print(f" ODD parameters: {len(LKA_ODD)} categories")
print(f" Triggering conditions: {len(LKA_TC_REGISTER)}")
print(f" Acceptance criteria: {len(LKA_ACCEPTANCE_CRITERIA)}")
critical = [t for t in LKA_TC_REGISTER if t["severity"] == 3]
print(f" S3 (fatal) TCs requiring priority analysis: {len(critical)}")Exercise 2: SOTIF Release Decision
"""SOTIF release decision: verify all criteria and argument completeness."""
EVIDENCE_SUMMARY = {
"simulation_scenarios": 3500,
"simulation_pass_rate": 0.998, # 0.2% failure (above limit)
"track_scenarios": 120,
"track_pass_rate": 1.0,
"public_road_km": 55000,
"false_intervention_per_100km": 0.05,
"new_q4_discovered": 0,
"q2_unresolved": 0,
"lane_detection_loss_pct": 0.003,
}
def release_decision(evidence: dict) -> str:
issues = []
if evidence["simulation_pass_rate"] < 0.995:
issues.append(f"Sim pass rate {evidence['simulation_pass_rate']:.3f} < 0.995")
if evidence["q2_unresolved"] > 0:
issues.append(f"{evidence['q2_unresolved']} unresolved Q2 scenarios")
if evidence["lane_detection_loss_pct"] >= 0.005:
issues.append("Lane detection loss exceeds AC_LKA_001 target")
if issues:
return "NOT APPROVED: " + "; ".join(issues)
return "APPROVED: All SOTIF acceptance criteria met"
decision = release_decision(EVIDENCE_SUMMARY)
print(f"SOTIF Release Decision: {decision}")Summary
The complete SOTIF analysis lab demonstrates the full loop from ODD definition through to release decision. The LKA analysis is intentionally designed so the initial simulation pass rate (99.8%) is below the 99.5% target, triggering a "NOT APPROVED" decision -- forcing the analyst to trace back to the failing scenarios, identify the TC causing them (construction zone temporary markings with high false-intervention rate), and define an additional design measure (HMI warning for construction zone + speed reduction) before re-running. This rejection-and-iteration cycle is the realistic SOTIF workflow: the first hazard analysis and V&V run rarely meets all acceptance criteria, and the value is in the systematic identification of remaining gaps and the targeted design improvements they drive.
🔬 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.