Verification & Validation
Master ISO 26262 V&V strategies across all development levels from unit testing through vehicle validation, with comprehensive coverage of independence requirements, coverage criteria, back-to-back testing, and evidence capture.
- Chapters
- 14
- Chapters
- Coverage
- MC/DC
- Coverage
- Test Environments
- HIL/SIL
- Test Environments
- Independence
- ASIL-D
- Independence
Quick answers
- What is verification and validation in ISO 26262?
- Verification and validation are distinct obligations distributed across ISO 26262 Parts 4, 6 and 8. Verification checks that each work product correctly implements its inputs - unit tests against the unit design, integration tests against the architecture, system tests against the technical safety requirements - answering "did we build it right?". Validation checks the item against its safety goals at vehicle level, answering "did we build the right thing?". The V-model pairs every left-side development activity with a right-side verification activity, each with defined verification criteria, coverage requirements scaled by ASIL, and independence requirements for who performs the check.
- What test coverage does ISO 26262 require for ASIL D?
- ISO 26262-6 scales structural coverage with ASIL through its method tables. At unit level, statement coverage is the baseline for lower ASILs, branch coverage is highly recommended from ASIL B upward, and MC/DC (modified condition/decision coverage) is highly recommended at ASIL D. At the architectural level, function and call coverage apply. Coverage is evidence, not the goal: gaps must be analyzed and justified - dead code, defensive code, or missing tests - and requirements-based test derivation comes first, with structural coverage measuring how thoroughly those tests exercised the code. The guide covers how to achieve MC/DC in practice and how tools measure it.
Why it pays for itself
Plan V&V across every level
Build a coherent strategy from unit testing through integration, system and vehicle testing, with each right-side V-model activity tied to the left-side artifact it verifies and the criteria it must meet.
Hit the coverage bar for your ASIL
Understand structural coverage from statement and branch up to MC/DC, which criteria ISO 26262-6 expects at which ASIL, and how to actually achieve and measure them with tool support.
Produce evidence that survives assessment
Implement I1 to I3 independence in the test organization, apply back-to-back and fault injection testing where required, and compile the V&V evidence package the safety case will cite.
What you’ll be able to do
Plan Compliant V&V Activities
Structure verification and validation plans covering all required activities, methods, independence levels, and coverage criteria per ISO 26262 Parts 4, 5, and 6.
Achieve MC/DC Coverage
Apply Modified Condition/Decision Coverage correctly for ASIL-C and ASIL-D software with proper test case design and coverage measurement tooling.
Implement Independence
Organize and document verification independence at I1, I2, and I3 levels appropriate to ASIL requirements and activity type.
Design HIL/SIL Test Environments
Build Hardware-in-the-Loop and Software-in-the-Loop test environments with fault injection capability and proper equivalence arguments.
Execute Fault Injection Testing
Plan and execute fault injection campaigns to verify safety mechanism effectiveness and demonstrate diagnostic coverage achievement.
Compile V&V Evidence Packages
Assemble complete, assessment-ready verification and validation evidence packages with traceability, coverage data, and review records.
Chapter by chapter
- 01
V&V Fundamentals
Establish the distinction between verification and validation in ISO 26262 context. Understand verification aims, confirmation measures, and how V&V activities are distributed across Parts 4, 5, 6, and 8.
- Verification vs. validation
- Confirmation measures
- Cross-part distribution
- 02
V-Model Overview
Navigate the ISO 26262 V-Model from concept through system integration, understanding how each right-side verification activity corresponds to a left-side development activity and what verification criteria are required at each level.
- Level correspondence
- Verification criteria
- Cross-phase traceability
- 03
Unit Testing
Design and execute unit tests per ISO 26262-6 requirements. Covers test case derivation methods, boundary value analysis, equivalence class partitioning, and structural coverage requirements per ASIL.
- Test case derivation
- Boundary value analysis
- Structural coverage
- 04
Integration Testing
Plan and execute software and hardware-software integration testing. Learn integration test strategies, interface testing, stub and driver design, and coverage requirements for integration test levels.
- Integration strategies
- Interface testing
- Stub/driver design
- 05
System Testing
Validate the complete item against system-level requirements. Covers functional testing, safety mechanism activation testing, boundary testing at system level, and regression testing strategies for system integration.
- Functional testing
- Safety mechanism testing
- Regression strategy
- 06
Vehicle Testing
Conduct vehicle-level validation including driving tests, fault injection scenarios, boundary condition evaluation, and safety goal verification on real vehicles or proving grounds.
- Driving test scenarios
- Vehicle fault injection
- Safety goal verification
- 07
Coverage Requirements (MC/DC)
Master structural coverage criteria from statement coverage through MC/DC (Modified Condition/Decision Coverage). Understand ASIL-specific requirements, how to achieve MC/DC, and tool support for coverage measurement.
- MC/DC explanation
- ASIL coverage table
- Coverage tool integration
- 08
Independence Requirements
Understand and implement independence requirements for verification activities per ISO 26262. Learn the difference between I1, I2, and I3 independence levels and how to demonstrate independence in project organization.
- I1/I2/I3 levels
- Independence demonstration
- Organizational measures
- 09
Test Case Derivation
Derive test cases from multiple sources including requirements, risk analysis, design, and fault models. Learn systematic derivation methods for both black-box and white-box testing with traceability to test coverage goals.
- Requirements-based
- Risk-based derivation
- Fault-model-based
- 10
Back-to-Back Testing
Apply back-to-back testing for model-based development and for comparing production code against reference implementations. Understand when back-to-back testing is required, how to set it up, and what coverage it provides.
- MBD back-to-back
- Coverage equivalence
- Setup methodology
- 11
HIL/SIL/MIL
Design and execute Model-in-the-Loop, Software-in-the-Loop, and Hardware-in-the-Loop test environments for automotive functional safety verification. Covers environment modeling, fault injection capability, and equivalence arguments.
- MIL/SIL/HIL overview
- Environment modeling
- Equivalence arguments
- 12
Fault Injection
Apply fault injection testing to verify safety mechanism effectiveness. Covers software fault injection, hardware fault injection via HIL, and fault injection methodology for achieving diagnostic coverage demonstration.
- SW fault injection
- HW fault injection
- DC demonstration
- 13
Review & Inspection
Apply formal review and inspection methods including walk-throughs, technical reviews, and inspections per ISO 26262. Learn checklist design, review records, and how to demonstrate review independence for ASIL-C and D.
- Review methods
- Checklist design
- Independence demonstration
- 14
Evidence Capture
Systematically capture and organize V&V evidence for the safety case. Learn test report requirements, coverage evidence formats, review records, and how to assemble assessment-ready V&V documentation packages.
- Test report requirements
- Coverage evidence
- Safety case integration
Not just text: the visual toolkit
Interactive V-Model Navigator
Clickable V-Model showing all verification activities, their inputs/outputs, ASIL requirements, and cross-links between development and verification levels.
Coverage Requirement Table
Interactive ISO 26262 coverage tables showing statement, branch, MC/DC, and requirement coverage targets per ASIL with worked examples and tool configuration guidance.
MC/DC Visualizer
Step-by-step visual demonstration of Modified Condition/Decision Coverage with truth table construction, independence condition identification, and minimum test case selection.
HIL Test Environment Diagram
Architecture diagram of a typical HIL test environment showing ECU connection, environment models, fault injection capabilities, and test automation interfaces.
Fault Injection Coverage Map
Visual mapping of injected faults to safety mechanisms, showing coverage ratios, diagnostic time intervals, and ASIL-appropriate demonstration completeness.
Independence Level Checker
Decision tool for determining required independence level based on ASIL and activity type, with organizational measure examples and documentation templates for each level.
V&V Plan for ASIL-D Brake Control Software
Complete verification and validation planning and execution walkthrough for an ASIL-D brake control software component, from unit testing through HIL vehicle simulation.
- Unit test campaign design with MC/DC coverage targets for 12 critical functions
- Integration test strategy for SPI communication and actuator interfaces
- HIL environment setup with brake system plant model and fault injection capabilities
- Safety mechanism activation testing covering 23 fault injection scenarios
- Back-to-back testing between Simulink model and generated C code
- V&V evidence package assembly for TÜV safety assessment
Unlock 5 more V&V phases
Who this guide is for
- Test engineers and test leads on their first ASIL-rated project
- Software leads establishing structural coverage targets and toolchains
- V&V planners distributing verification activities across MIL, SIL and HIL environments
- Engineers assembling verification evidence for a functional safety assessment
Frequently Asked Questions
Common questions about Verification & Validation
Start the course today
A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov simulator, and 5 practice exams per month. The Pro and Expert plans unlock more of the 78-guide library. No credit card required.