| Base Practice | Requirement | MiL/SiL Evidence |
|---|---|---|
| BP1: Develop unit test specification | Test spec for each SW unit including test cases, inputs, expected outputs | Test case descriptions in .mldatx with req links |
| BP2: Select test cases | Systematic selection: ECT, BVA, state-based | Test case design rationale document |
| BP3: Select test harness | Appropriate test environment (harness, stubs, scripts) | Test environment description; MCAL stub inventory |
| BP4: Execute unit tests | Run tests and record results | Simulink Test Report / pytest HTML report |
| BP5: Measure coverage | Statement, branch, MC/DC as required by ASIL | Coverage report HTML/PDF with percentages |
| BP6: Verify code vs model | Back-to-back MiL vs SiL comparison | B2B comparison report; max diff < tolerance |
ASPICE SWE.4 Base Practice Requirements
Evidence Package Assembly Script
Pythonassemble_evidence.py
"""Assemble ASPICE SWE.4 evidence package for delivery."""
import os
import shutil
import datetime
COMPONENT = "SpeedController"
VERSION = "2.4.1"
OUTPUT_DIR = f"evidence/{COMPONENT}_v{VERSION}_SWE4"
os.makedirs(OUTPUT_DIR, exist_ok=True)
evidence_files = {
# BP1: Test specification
"01_TestSpec/SpeedController_TestSpec.pdf": "docs/test_spec.pdf",
"01_TestSpec/SpeedController_Tests.mldatx": "tests/SpeedController_Tests.mldatx",
# BP4: Test results
"02_TestResults/MiL_Test_Report.pdf": "reports/MiL_Test_Report.pdf",
"02_TestResults/SiL_Test_Report.pdf": "reports/SiL_Test_Report.pdf",
# BP5: Coverage
"03_Coverage/MiL_Coverage_Report.html": "reports/Coverage_Report.html",
"03_Coverage/coverage_summary.json": "reports/coverage_summary.json",
# BP6: Back-to-back
"04_BackToBack/B2B_Comparison_Report.pdf": "reports/B2B_Report.pdf",
# Traceability
"05_Traceability/Traceability_Matrix.xlsx": "reports/Traceability_Matrix.xlsx",
}
for dest_rel, src in evidence_files.items():
dest = os.path.join(OUTPUT_DIR, dest_rel)
os.makedirs(os.path.dirname(dest), exist_ok=True)
if os.path.exists(src):
shutil.copy2(src, dest)
print(f" OK {dest_rel}")
else:
print(f" MISSING {src}")
print(f"\nEvidence package: {OUTPUT_DIR}")Summary
Assembling the ASPICE SWE.4 evidence package is the final step that turns a well-tested component into a deliverable that passes an ASPICE assessment. The most common finding in ASPICE SWE.4 audits is not missing tests but missing links: test cases that exist but are not linked to requirements (BP2 gap), coverage reports that exist but are not labelled with component version and date (traceability gap), or back-to-back reports that exist but do not reference the specific test cases used (BP6 gap). The evidence assembly script enforces completeness by checking that all required files exist before packaging -- failing loudly if any document is missing rather than delivering an incomplete package that fails the audit.
🔬 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.