MIL Test Architecture Design - SIL/MIL Testing

MiL Test Harness Architecture

MiL Test Harness Structure

  Test Harness Model (.slx)
  +------------------------------------------+
  |  Test Stimuli Block                      |
  |  (Signal Builder / From File / MATLAB Fcn)|
  +------------------------------------------+
              |
  +------------------------------------------+
  |  Model Under Test (MUT)                  |
  |  [Model Reference: SpeedController.slx]  |
  +------------------------------------------+
              |
  +------------------------------------------+
  |  Verification Block                      |
  |  (Assertion, Verify blocks, To Workspace)|
  +------------------------------------------+
              |
  Test Manager (.mldatx)
  Collects results, generates ASPICE SWE.4 report

Test Data Management

MATLABtest_data_management.m

% Structured test data management for MiL test suite

% Test vectors stored as MATLAB structures
function tc = create_test_vector(name, req_id, description)
    tc.name        = name;
    tc.req_id      = req_id;
    tc.description = description;
    tc.time        = [];
    tc.inputs      = struct();
    tc.expected    = struct();
    tc.tolerance   = struct();
end

% Define test case TC_001
tc001 = create_test_vector("TC_001_StepResponse",
    "SSR-SPEED-042", "Step from 0 to 50 km/h; settle within 3s");
tc001.time = (0:0.01:10);
tc001.inputs.SpeedRef = [zeros(1,100), 50*ones(1,900)]; % step at 1s
tc001.expected.VehicleSpeed_at_t4s = 50.0;
tc001.tolerance.VehicleSpeed = 0.5;  % +/- 0.5 km/h

% Save test library
test_library.TC_001 = tc001;
save("test_vectors/SpeedController_Tests.mat", "test_library");

% Load and run in Simulink Test Manager
data = load("test_vectors/SpeedController_Tests.mat");
tc = data.test_library.TC_001;
set_param("TestHarness/SpeedRef", "Value",
    mat2str(tc.inputs.SpeedRef));

Summary

MiL test architecture design determines whether a test suite is maintainable over the vehicle lifetime or becomes an unmaintainable collection of one-off scripts. The key architectural decision is separating test data (what to test) from test execution logic (how to test). Test vectors stored in structured MATLAB files or Excel sheets can be updated by domain engineers without MATLAB knowledge; the execution harness reads them generically. This separation also enables requirements traceability: every test vector has a req_id field that links to the SSR, enabling automatic generation of the ASPICE SWE.4 traceability matrix from the test data itself rather than from manual documentation.

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