| Measure | Purpose | Frequency | ASIL-D Requirement |
|---|---|---|---|
| Design Review | Verify work product quality and completeness | Per work product | Required; I1 for most; I2 for HARA, architecture |
| Safety Audit | Assess whether safety activities comply with the safety plan | At least twice (mid-project, pre-release) | Required; I2 minimum |
| Functional Safety Assessment | Independent assessment of entire safety case | End of development (pre-release) | Required; I3 (external company) for ASIL-D |
ISO 26262 Part 2 Confirmation Measures
Safety Audit: Process and Checklist
Markdownsafety_audit_checklist.md
# Safety Audit Checklist — ASIL-D Project
## 1. Safety Plan Compliance
☐ Safety plan is current and approved
☐ All work products listed in safety plan are present (or justified as not applicable)
☐ Safety plan changes have been impact-assessed
☐ Confirmation measures completed as planned (no overdue items without justification)
## 2. Requirements Quality
☐ All safety goals have ASIL level and justification
☐ HARA is complete: all operational scenarios considered; S/E/C justified
☐ Bidirectional traceability: Safety Goal → FSR → TSR → SSR → Test Case
☐ No orphaned requirements (no parent or no child link)
☐ All requirements reviewed per independence requirements
## 3. Software Development Compliance
☐ MISRA C:2012 compliance: zero unresolved mandatory violations
☐ All deviations documented with justification and independent review
☐ Static analysis tool qualified (ISO 26262 Part 8 Clause 11)
☐ MC/DC coverage achieved for all ASIL-D functions: report attached
☐ Unit test review completed (I1) for all ASIL-D test cases
## 4. Hardware Analysis
☐ FMEA complete: all ASIL-D hardware elements included
☐ SPFM ≥ 99% (ASIL-D), LFM ≥ 90% (ASIL-D), PMHF < 10 FIT
☐ FIT data sources justified (IEC TR 62380, manufacturer FMEDA, or field data)
☐ DFA completed: independence evidence for all ASIL decompositions
## 5. Configuration and Change Management
☐ All safety-relevant items under version control with baseline defined
☐ Change impact assessment performed for all post-baseline changes
☐ Safety impact assessments approved by safety manager
## 6. Open Issues
☐ All high-severity audit findings from previous audit closed
☐ Risk assessment for remaining open findings documentedManaging Audit Findings
| Finding Severity | Definition | Required Action | Closure Criterion |
|---|---|---|---|
| Major | Safety gap that requires design/process change to close | Corrective action plan within 5 business days | Work product updated; independent re-review completed |
| Minor | Process non-conformance not affecting safety case validity | Corrective action within agreed sprint/milestone | Process updated; evidence of compliance |
| Observation | Improvement recommendation; no safety impact | Optional improvement; considered in next project | Documented as closed or accepted risk |
| Open question | Clarification needed; may escalate to finding | Answer provided within 2 business days | Finding re-classified or closed |
Summary
Confirmation reviews and audits are the ISO 26262 process quality assurance mechanisms — they verify that the safety activities are being performed correctly, not just that documents exist. A common audit finding: MC/DC coverage reports show 100% coverage, but the tests were written to match the existing code rather than to satisfy the SSRs. This is a process failure (tests not written to requirements) that the audit can identify by comparing the test cases against the SSRs rather than against the code. The functional safety assessment at the end of development is the final gate — a major finding from the assessor after months of development is very expensive to resolve. Early assessor engagement (attending mid-project reviews) prevents late surprises.
🔬 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.