| Activity | Question Answered | Examples | When |
|---|---|---|---|
| Verification | Did we build the product right? (conformance to specification) | Code review, unit test, FMEA, static analysis | Throughout development (V-model left and right sides) |
| Validation | Did we build the right product? (fitness for purpose) | Vehicle-level test, HIL test, HARA confirmation, prototype driving | End of development; confirms safety goals are met |
Validation vs Verification
Safety Validation Methods
| Method | Coverage | ASIL Applicability | Limitations |
|---|---|---|---|
| Analysis (safety case review) | All aspects; no execution | All ASIL levels | Does not discover emergent behaviour |
| Hardware-in-the-loop (HIL) simulation | Full system with real ECUs; simulated plant | ASIL-B/C/D; high confidence | Simulator model accuracy; may miss real-world edge cases |
| Prototype vehicle testing | Full real-world environment | All ASIL levels; highest confidence | Expensive; limited reproducibility; safety risk during testing |
| Vehicle-level simulation (SiL) | Complete virtual vehicle | Early validation; concept check | Model accuracy; not as credible as HIL or vehicle |
| Fault injection on HIL | Validates safety mechanisms in realistic environment | Required for ASIL-D DC claims | Complex test infrastructure; time-consuming |
Safety Validation Plan Structure
Markdownvalidation_plan.md
# Safety Validation Plan — FCAB Item (ASIL-D)
## Objective
Demonstrate that Safety Goals SG-01 to SG-04 are met by the developed system
under representative real-world conditions.
## Validation Items
### SG-01: No unintended AEB activation
| Test ID | Test Method | Environment | Pass Criterion |
|-------------|----------------------|--------------|---------------------------------------|
| VT-SG01-001 | HIL fault injection | HIL rig | AEB not activated when TTC > 2s under all radar fault modes |
| VT-SG01-002 | Vehicle test (flat road) | Test track | No inadvertent braking in 500km test run |
| VT-SG01-003 | HIL: camera false detection | HIL | AEB not activated on false positive camera |
### SG-02: AEB activates when collision imminent
| Test ID | Test Method | Environment | Pass Criterion |
|-------------|----------------------|--------------|---------------------------------------|
| VT-SG02-001 | Soft target vehicle test | Test track | AEB activates for all TTC < 1.5s scenarios; decel ≥ 5 m/s² |
| VT-SG02-002 | HIL: pedestrian scenarios | HIL rig | AEB activates for all EuroNCAP pedestrian test scenarios |
| VT-SG02-003 | Night / rain scenarios | Proving ground | AEB meets EuroNCAP thresholds in poor visibility |
## Regression Validation
All validation tests shall be repeated after any change to:
- FCAB software (any SSR-relevant module)
- Hardware (any ASIL-D component)
- Configuration (ASIL-D parameter change)
## Validation Environment Qualification
- HIL simulator model validated against measured vehicle data (< 5% error)
- Test tools calibrated and qualified per ISO 26262 Part 8 Clause 11Summary
Safety validation provides the top-level evidence in the safety case that the safety goals are met in the real operational environment. Verification activities (reviews, unit tests, static analysis) demonstrate conformance to requirements — but requirements can be wrong. Validation asks: does the system actually prevent the hazardous events identified in HARA? HIL testing with fault injection is the most cost-effective method for ASIL-D validation: it combines realistic ECU hardware with reproducible fault injection scenarios and automated pass/fail assessment. Vehicle-level testing remains essential for validating scenarios that are too complex to model in simulation.
🔬 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.