Back-to-Back Testing (MIL vs SIL) - SIL/MIL Testing

Back-to-Back Testing: Rationale and Standard

ISO 26262 Part 6 Clause 9 Requirement

ISO 26262 Part 6 Clause 9.4.2 requires that for software units with ASIL-B and above, the equivalence of the model (specification) and the generated code (implementation) is verified by back-to-back testing. The standard specifies:

The same test cases used for MiL testing are re-run in SiL mode
Output signals are compared; differences must be within the quantisation error of the production data types
Any difference larger than quantisation error is a code generation defect that must be resolved

The back-to-back comparison is not just a quality check -- it is a safety argument: it demonstrates that the generated code faithfully implements the algorithm specified in the model, closing the gap between the design artefact (model) and the implementation artefact (code).

Back-to-Back Comparison Script

MATLABb2b_comparison.m

% Back-to-back MiL vs SiL comparison
% Runs same test cases in both modes; compares all output signals
model = "SpeedController";

% Define outputs to compare
compare_signals = {"VehicleSpeed", "PedalRequest",
                   "FaultActive", "GearPosition"};

% Tolerance: quantisation from single-precision (2^-23 relative)
% For signals in range 0-120: tolerance = 120 * 2^-23 ~ 1.4e-5
% Use 1e-4 as practical tolerance (allows for rounding mode diffs)
tolerance = 1e-4;

% Step 1: MiL run
set_param(model, "SimulationMode", "normal");
mil_out = sim(model, 20.0);

% Step 2: SiL run (same model, compiled code)
set_param(model, "SimulationMode", "software-in-the-loop (sil)");
sil_out = sim(model, 20.0);

% Step 3: Compare
all_pass = true;
for i = 1:numel(compare_signals)
    sig = compare_signals{i};
    mil_data = mil_out.logsout.getElement(sig).Values.Data;
    sil_data = sil_out.logsout.getElement(sig).Values.Data;
    max_diff = max(abs(double(mil_data) - double(sil_data)));
    passed = max_diff <= tolerance;
    all_pass = all_pass && passed;
    fprintf("  %s: max_diff = %.2e  %s\n", sig, max_diff,
        passed ? "PASS" : "FAIL");
end

assert(all_pass, "Back-to-back MiL/SiL comparison FAILED");
fprintf("B2B comparison: PASS\n");

Summary

Back-to-back testing is the technically rigorous evidence that the code generator has not introduced errors. The tolerance definition deserves careful attention: for single-precision floating-point signals, the theoretical tolerance is the machine epsilon relative to the signal range (approximately 1e-5 for 0-120 km/h). Using a tolerance of 1e-4 provides a small margin for legitimate rounding mode differences between the Simulink simulation engine and the target compiler. Any difference significantly larger than this tolerance -- say, 0.1 or 1.0 -- indicates a code generation error: a wrong data type, a missing saturation, or an incorrect scaling factor. These bugs are invisible in MiL testing (which uses the model) but caught immediately in back-to-back comparison.

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