Hands-On: Complete V&V Workflow - Model-Based Development

Lab: Complete V&V Workflow

Phase	Activity	Evidence Generated
MiL testing	Simulink Test Manager: 10 test cases covering all modes	Test report with PASS/FAIL; signal traces
Coverage analysis	Cumulative MC/DC coverage from all MiL tests	Coverage report; gap list
SLDV gap closure	Auto-generate tests for MC/DC gaps	Additional test cases; 100% MC/DC
SiL back-to-back	Run same tests in SiL mode; compare to MiL	B2B comparison report: max diff < 1e-4
Property proving	SLDV prove: output within bounds	SLDV proof report
ASPICE artefact	Consolidate: test spec + results + coverage + traceability	ASPICE SWE.4 evidence package

Exercise 1: Complete V&V Script

MATLABcomplete_vv.m

% Complete MBD V&V workflow script
model = "SpeedController";
load_system(model);

% ---- Phase 1: MiL testing ----
fprintf("--- Phase 1: MiL Testing ---\n");
set_param(model, "SimulationMode", "normal");
ts = sltest.testmanager.loadTests("SpeedController_Tests.mldatx");
mil_result = sltest.testmanager.run(ts);
sltest.testmanager.report(mil_result, "MiL_Test_Report.pdf");

% ---- Phase 2: Coverage ----
fprintf("--- Phase 2: Coverage Analysis ---\n");
% (coverage collected during MiL run above)
cov = mil_result.getCoverageData;
cvreport(cov, "Format","html","File","Coverage_Report.html");
mcdc_pct = cov.coverageData.mcdc.percentage;
fprintf("MC/DC: %.1f%%\n", mcdc_pct);

% ---- Phase 3: SLDV gap closure (if MC/DC < 100%) ----
if mcdc_pct < 100
    fprintf("--- Phase 3: SLDV Gap Closure ---\n");
    opts = sldvoptions; opts.Mode = "TestGeneration";
    opts.ModelCoverageObjectives = "MCDC";
    sldv.run(model, opts);
    sldv.exportToTest("sldv_output/sldv_data.mat", ...
        "SpeedController_Tests.mldatx", "AppendToFile", true);
end

% ---- Phase 4: SiL back-to-back ----
fprintf("--- Phase 4: SiL Back-to-Back ---\n");
set_param(model, "SimulationMode", "software-in-the-loop (sil)");
sil_result = sltest.testmanager.run(ts);
fprintf("SiL test PASSED: %d/%d\n", ...
    sil_result.NumPassed, sil_result.NumTests);
fprintf("V&V workflow COMPLETE\n");

Summary

The complete V&V workflow lab brings together all test techniques from this module into a single automated pipeline. The key insight is sequencing: MiL testing first (fastest; catches algorithm bugs early), then coverage analysis (identifies gaps in the test suite), then SLDV gap closure (fills gaps automatically), then SiL back-to-back (verifies code equivalence). Each phase produces evidence that maps directly to an ASPICE requirement: MiL results to SWE.4 BP4 (unit test results), coverage to SWE.4 BP5 (coverage measurement), SiL to SWE.4 BP6 (back-to-back verification). Running this pipeline in CI on every model change means the ASPICE evidence is always current and up to date - no sprint-end scramble to collect test evidence.

🔬 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.