Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

Pre-Assessment Checklist

Pythonpre_assessment_checker.py
#!/usr/bin/env python3
# Pre-assessment readiness checker — run 4 weeks before FSA/ASPICE assessment
import requests, json

COMPLIANCE_MATRIX_FILE = "compliance_matrix_iso26262.json"

def check_evidence_links(matrix_file):
    with open(matrix_file) as f:
        matrix = json.load(f)

    broken = []; incomplete = []; ok = 0
    for req in matrix["requirements"]:
        if req["status"] in ["Unknown", ""]:
            incomplete.append(req["id"])
        elif req["evidence_url"]:
            resp = requests.head(req["evidence_url"], timeout=10)
            if resp.status_code != 200:
                broken.append((req["id"], req["evidence_url"], resp.status_code))
            else:
                ok += 1

    print(f"Evidence links: {ok} OK, {len(broken)} broken, {len(incomplete)} incomplete")
    for req_id, url, code in broken:
        print(f"  BROKEN [{req_id}]: {url} → HTTP {code}")
    for req_id in incomplete:
        print(f"  INCOMPLETE [{req_id}]: No status or evidence — classify or complete")

    return len(broken) == 0 and len(incomplete) == 0

def check_process_owners_briefed(roles):
    print("\nProcess owner briefing status:")
    for role, briefed in roles.items():
        status = "READY" if briefed else "NOT BRIEFED"
        print(f"  {role}: {status}")
    return all(roles.values())

# Execute pre-assessment checks
roles = {
    "SWE.1 Requirements Engineer": True,
    "SWE.4 Test Engineer":         True,
    "SUP.8 CM Engineer":           False,  # needs briefing
    "Safety Manager":              True,
}

links_ok = check_evidence_links(COMPLIANCE_MATRIX_FILE)
owners_ok = check_process_owners_briefed(roles)

print(f"\nOverall readiness: {'READY' if links_ok and owners_ok else 'NOT READY — fix above gaps'}") 

Traceability Walkthrough Practice

ASPICE Traceability Walkthrough Demo Path
  Assessor request: "Show traceability from SWR-042 to test result"

  Step 1: Open Polarion → SW Requirements module → find SWR-042
          SWR-042: "EPS shall limit torque to ≤ 3 Nm within 10 ms of sensor input"

  Step 2: Navigate SW Architecture link
          SWR-042 → ARCH-TORQ-003 (Torque_Limiter SW component in architecture)

  Step 3: Navigate SW Unit link
          ARCH-TORQ-003 → UNIT-TL-001 (Torque_Limiter.c implementation)

  Step 4: Navigate Test Case link
          SWR-042 → TC-TL-042 in TESSY ("Test torque limit clamps at 3 Nm")

  Step 5: Navigate Test Result link
          TC-TL-042 → TR-TL-042 (TESSY report: PASS, 100% branch coverage, 2026-02-15)

  Reverse check: TC-TL-042 → SWR-042 (no orphan tests)
  MC/DC check: report shows all conditions covered

  Practice this path until it takes < 2 minutes — assessors time you

Common Audit Findings

FindingClause / ProcessPrevention
Incomplete traceability — test exists but not linked to requirementASPICE SWE.4, ISO 26262-6 §11Build traceability in requirements tool from first day of testing, not retrospectively
Informal review records — 'approved' stamp, no issue listISO 26262-6 §8; ASPICE SUP.1Review template must have issue table; no issue list = incomplete review
Tool qualification doesn't cover version actually used in buildISO 26262-8 §8.11Pin tool versions in Docker; verify TQK version matches CI tool version
Safety assumption not verified at integration level (SEooC gap)ISO 26262-7 §5Integration check documented: ASG vs actual Safety Goal comparison record
Co-author reviewed own work — independence violationISO 26262-2 §6.4Review assignment tool prevents same engineer from author + reviewer

Post-Audit Improvement Cycle

Pythonaudit_finding_tracker.py
#!/usr/bin/env python3
# Post-audit finding tracker: Major/Minor classification with action plans
from datetime import date, timedelta

findings = [
    {
        "id": "AF-2026-001",
        "type": "Major",
        "standard": "ASPICE SWE.4 (Level 2 GP 2.1.7)",
        "description": "Unit test process does not manage stakeholder interfaces "
                       "(test results not formally communicated to Safety Manager)",
        "root_cause": "GP 2.1.7 (manage stakeholder interfaces) not understood as applicable to testing process",
        "action": "Add Test Report distribution step to test process; Safety Manager on test report distribution list",
        "owner": "Test Process Owner",
        "target_date": str(date.today() + timedelta(days=30)),
        "follow_up_assessment": True,
        "status": "In Progress",
    },
    {
        "id": "AF-2026-002",
        "type": "Minor",
        "standard": "ISO 26262-6 §9 (MISRA)",
        "description": "3 MISRA C:2012 advisory violations in non-safety partition accepted without documented justification",
        "root_cause": "Deviation process not followed for advisory violations",
        "action": "Add justification comments per MISRA deviation process; update static analysis suppression policy",
        "owner": "Lead SW Engineer",
        "target_date": str(date.today() + timedelta(days=90)),
        "follow_up_assessment": False,
        "status": "Planned",
    },
]

for f in findings:
    days = (date.fromisoformat(f["target_date"]) - date.today()).days
    print(f"[{f['id']}] {f['type']} — {f['standard']}")
    print(f"  Finding: {f['description'][:80]}")
    print(f"  Action:  {f['action'][:80]}")
    print(f"  Owner: {f['owner']} | Due: {f['target_date']} ({days}d) | Status: {f['status']}")
    if f["follow_up_assessment"]:
        print(f"  ⚠️  Follow-up assessment required within 30 days for Major finding")
    print()

Summary

Audit preparation is a discipline, not an event. The four-week pre-assessment check — broken links, incomplete statuses, unbriefed process owners — addresses the top causes of unexpected findings. The traceability walkthrough drill reduces assessment anxiety and confirms that the evidence chain actually works end-to-end before the assessor sees it. Post-audit, every Major finding gets a 30-day follow-up assessment — treat it as a learning opportunity to strengthen the process rather than a compliance burden, and the ASPICE capability level trend will improve year over year.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousSupplier Compliance Management