Hands-On: Complete Analysis Pipeline - Static Analysis & MISRA

Lab: Complete Static Analysis Pipeline

Stage	Tool	Pass Criterion
MISRA check	cppcheck + MISRA	Zero mandatory violations; all required have deviations
Bug finding	Polyspace Bug Finder	Zero Red findings; Orange reviewed and accepted
Complexity	Custom script (radon/ccm)	All functions complexity <= 15
Quality gate	Python gate script	All gates PASS
Evidence package	Python assembly script	All 6 evidence files present

Exercise 1: Complete Pipeline Script

Bashrun_full_sa_pipeline.sh

#!/bin/bash
# Complete static analysis pipeline
set -e
COMPONENT="SpeedController"
VERSION=$(git describe --tags --always)
REPORT="reports/${VERSION}"
mkdir -p "${REPORT}"

echo "=== Stage 1: MISRA Check ==="
cppcheck \
    --addon=misra \
    --suppressions-list=config/suppressions.txt \
    --xml --output-file="${REPORT}/misra.xml" \
    -I include/ src/
python3 scripts/parse_cppcheck.py "${REPORT}/misra.xml" \
    --output "${REPORT}/misra_summary.json"

echo "=== Stage 2: Complexity Metrics ==="
python3 scripts/compute_complexity.py src/ \
    --output "${REPORT}/complexity.json" \
    --threshold 15

echo "=== Stage 3: Quality Gate ==="
python3 scripts/quality_gate.py \
    --misra "${REPORT}/misra.xml" \
    --complexity "${REPORT}/complexity.json" \
    --deviations config/deviation_register.yaml

echo "=== Stage 4: Evidence Package ==="
python3 scripts/assemble_sa_evidence.py \
    --component "${COMPONENT}" \
    --version "${VERSION}" \
    --report-dir "${REPORT}"

echo ""
echo "PIPELINE COMPLETE: ${COMPONENT} v${VERSION}"

Exercise 2: Inject and Detect a MISRA Violation

Cinject_violation.c

/* Inject a Rule 14.4 violation and verify CI catches it */

/* Before (compliant): */
if (error_code != 0u) { handle_error(); }

/* After (violation): */
if (error_code) { handle_error(); }  /* Rule 14.4: non-boolean condition */

/* Expected CI result:
 * cppcheck: [misra-c2012-14.4] condition is not boolean
 * quality_gate.py: REQUIRED violation without deviation
 * Pipeline: FAIL
 *
 * Fix: revert to != 0u comparison
 * Rerun: PASS
 * Purpose: verify pipeline reliably catches MISRA violations
 */

Summary

The complete static analysis pipeline lab consolidates all techniques from this course into a single automated workflow that produces ASPICE-ready evidence with every clean build. The violation injection exercise (deliberately introducing and then fixing a MISRA violation) serves the same purpose as the regression injection exercise in SiL testing: it proves that the pipeline actually catches real violations rather than running silently without detecting anything. Every static analysis pipeline should be validated this way before being declared CI-ready: if the pipeline does not catch a deliberately injected mandatory violation, it cannot be trusted to catch accidentally introduced ones in production code.

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