| ASPICE Process | Purpose | MBD Artefact |
|---|---|---|
| SWE.3 SW Detailed Design | Detailed design of software units | Simulink/Stateflow model (IS the design doc) |
| SWE.4 SW Unit Verification | Unit test spec, execution, coverage | Simulink Test suite + coverage report + MiL/SiL results |
| SWE.5 SW Integration Test | Integration test of units into components | Component-level HIL test + inter-model interface tests |
| SWE.6 SW Qualification Test | System-level software qualification | HIL test suite covering all SSRs; HiL report |
ASPICE SWE Processes and MBD Artefacts
SWE.3: Model as Design Document
| SWE.3 Base Practice | Requirement | MBD Evidence |
|---|---|---|
| BP1: Develop SW detailed design | Detailed design at unit level | Model hierarchy with subsystems + Stateflow charts |
| BP2: Describe dynamic behaviour | State machines, timing, event handling | Stateflow charts with documented transitions |
| BP3: Evaluate design | Review for correctness and testability | Model Advisor report; design review checklist |
| BP4: Communicate design | Design is available to SWE.4 testing | Model in version control; accessible to test team |
| BP5: Identify interfaces | All inports/outports defined | Bus object definitions; AUTOSAR port types |
Generating ASPICE Traceability Matrix
MATLABaspice_traceability.m
% Generate ASPICE SWE.4 traceability matrix
% Links: SSR -> Model block -> Test case -> Result
% Step 1: Get all requirement links in model
links = rmi("getLinks", "SpeedController");
linked_ssrs = {links.id};
% Step 2: Get all test cases and their linked requirements
ts = sltest.testmanager.loadTests("SpeedController_Tests.mldatx");
test_cases = ts.getTestCases;
tc_reqs = cellfun(@(tc) tc.Requirements, test_cases, ...
"UniformOutput", false);
% Step 3: Get test results
results = sltest.testmanager.run(ts);
passed = {results.TestCaseResults.Name};
% Step 4: Build matrix
ssrs = unique([linked_ssrs, [tc_reqs{:}]]);
T = table;
T.SSR = ssrs(:);
T.ModelLink = cellfun(@(s) any(strcmp(linked_ssrs,s)), ssrs(:));
T.TestCase = cellfun(@(s) any(cellfun(@(r) any(strcmp(r,s)),tc_reqs)), ssrs(:));
T.TestPassed = cellfun(@(s) any(strcmp(passed,s)), ssrs(:));
disp(T); % or export to Excel for ASPICE submission
writetable(T, "ASPICE_SWE4_Traceability_Matrix.xlsx");Summary
The ASPICE traceability matrix is the central evidence document for SWE.4 audits. It must show that every software requirement (SSR) has at least one linked model element (design traceability), at least one test case (test coverage), and that every test case passed (test results). Gaps in any column are audit findings: an SSR with no test case is a coverage gap; a test case with no SSR link has no justification for existing; a failed test means the software does not meet its requirement. Generating this matrix programmatically from the model links, test manager, and test results ensures it is always current and eliminates the manual data gathering that turns ASPICE audit preparation into a multi-week exercise.
🔬 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.