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

Requirements Traceability in Architecture

Why Traceability Matters

ISO 26262 Part 3 (System-level) and ASPICE SYS.3 require bidirectional traceability between system requirements and architectural elements. Every requirement must be allocated to at least one architectural component, and every architectural component must be justified by at least one requirement. Gaps in either direction indicate either untested requirements or unjustified architecture elements.

  • Forward traceability: requirement → architecture element → SW/HW component
  • Backward traceability: component → requirement (why does this exist?)
  • Horizontal traceability: system req → sub-system req → SW req → test case

Requirements-to-Architecture Mapping

Pythonreq_arch_mapping.py
"""Requirements-to-architecture traceability matrix."""
from dataclasses import dataclass, field
from typing import List

@dataclass
class SystemRequirement:
    req_id:       str
    description:  str
    asil:         str
    allocated_to: List[str] = field(default_factory=list)  # component IDs

@dataclass
class ArchComponent:
    comp_id:      str
    name:         str
    ecu:          str
    justified_by: List[str] = field(default_factory=list)  # req IDs

def check_traceability(reqs: List[SystemRequirement],
                        comps: List[ArchComponent]) -> dict:
    """Find forward and backward traceability gaps."""
    comp_ids = {c.comp_id for c in comps}
    req_ids  = {r.req_id  for r in reqs}

    # Forward: requirements with no allocation
    unallocated_reqs = [r for r in reqs if not r.allocated_to]

    # Forward: allocation to non-existent component
    bad_allocations = [
        (r.req_id, cid)
        for r in reqs
        for cid in r.allocated_to
        if cid not in comp_ids
    ]

    # Backward: components with no requirement
    unjustified_comps = [c for c in comps if not c.justified_by]

    return {
        "unallocated_reqs":  unallocated_reqs,
        "bad_allocations":   bad_allocations,
        "unjustified_comps": unjustified_comps
    }

# Example
reqs = [
    SystemRequirement("SYS-001", "AEB shall detect stationary vehicle at >= 40m",
                      "ASIL-B", ["COMP-AEB-DETECT", "COMP-RADAR-DRV"]),
    SystemRequirement("SYS-002", "Vehicle speed available on backbone within 10ms",
                      "ASIL-B", ["COMP-SPEED-SVC"]),
    SystemRequirement("SYS-003", "OTA update shall complete without driver interaction",
                      "QM",     []),  # <-- unallocated gap!
]
result = check_traceability(reqs, [])
print(f"Unallocated reqs: {[r.req_id for r in result['unallocated_reqs']]}") 

Summary

Requirements-to-architecture mapping is the activity that makes architecture reviewable. Without explicit traceability, an architecture review is a qualitative discussion; with it, the review can answer objective questions: "Which components implement SYS-042?" and "Why does the Gateway ECU exist -- which requirements justify it?". The gap analysis script is the automated quality gate: any unallocated requirement is a potential scope gap (the feature was specified but never assigned to an implementation), and any unjustified component is a potential scope creep (the component was designed but no customer requirement asked for it).

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

← PreviousArchitecture Viewpoints and FrameworksNext →Architecture Decision Records