ASPICE-Compliant Reporting - Static Analysis & MISRA

ASPICE SWE.4 Static Analysis Requirements

Base Practice	Requirement	Static Analysis Evidence
BP1	Define SW unit test specification	Static analysis tool configuration as specification
BP3	Select appropriate test environment	Tool selection rationale; version documentation
BP4	Execute tests; record results	Static analysis report with finding list and status
BP5	Measure coverage	Rule coverage report; compliance percentage per category

ASPICE Evidence Assembly

Pythonassemble_sa_evidence.py

"""Assemble ASPICE SWE.4 static analysis evidence package."""
import os
import shutil
import datetime

COMPONENT = "SpeedController"
VERSION   = "2.4.1"
OUTDIR    = f"evidence/{COMPONENT}_v{VERSION}_StaticAnalysis"

os.makedirs(OUTDIR, exist_ok=True)

evidence = {
    # Tool identification and configuration
    "01_ToolConfig/misra_tool_config.xml":     "config/misra_cppcheck.xml",
    "01_ToolConfig/polyspace_config.xml":      "config/polyspace_bugfinder.xml",
    "01_ToolConfig/tool_versions.txt":         "config/tool_versions.txt",

    # MISRA compliance report
    "02_MISRA/misra_compliance_report.html":   "reports/misra.html",
    "02_MISRA/deviation_register.yaml":        "config/deviation_register.yaml",
    "02_MISRA/misra_violation_summary.json":   "reports/misra_summary.json",

    # Bug finder report
    "03_BugFinder/polyspace_report.html":      "reports/polyspace/report.html",

    # Quality gate result
    "04_QualityGate/gate_result.txt":          "reports/gate_result.txt",
}

for dest_rel, src in evidence.items():
    dest = os.path.join(OUTDIR, 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"Evidence: {OUTDIR}/")

Summary

The ASPICE static analysis evidence package is the deliverable that converts the CI pipeline outputs into formal quality records. The most common gap in static analysis evidence packages is the tool configuration document: ASPICE assessors need to verify that the tool was configured to check the right rules (all mandatory and required MISRA rules enabled, no inappropriate suppressions in the configuration). Without the tool configuration file as evidence, the compliance report cannot be validated -- the assessor cannot determine whether "zero violations" means genuinely clean code or a tool configured with most rules disabled.

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