Hands-On: Compliance Matrix Creation - Standards & Compliance

Compliance Matrix Purpose and Structure

Compliance Matrix Column Structure

  Req ID | Requirement Text | ASIL | Responsible Role | Work Product | Status | Evidence Ref | Tailoring

  Req ID:          Unique clause reference (e.g., ISO26262-6:2018 §7.4.4)
  Requirement Text: Quoted or paraphrased requirement from standard
  ASIL:            Applicable ASIL level (A/B/C/D/QM or N/A)
  Responsible Role: Safety Engineer / SW Architect / Test Engineer / etc.
  Work Product:    Document / report / record that satisfies requirement
  Status:          Planned | In Progress | Complete | N/A (with justification)
  Evidence Ref:    Hyperlink to DMS document or Polarion work product ID
  Tailoring:       Justification if requirement is excluded or modified

💡 Matrix as Living Document

The compliance matrix is not a one-time artifact — it is the primary project management tool for compliance activities. Update it every two weeks with new evidence links and status changes. Before every gate review, the Safety Manager walks the matrix looking for stale 'In Progress' items. During the FSA or ASPICE assessment, the auditor uses the matrix as their primary navigation tool — a well-maintained matrix significantly reduces assessment duration and finding count.

ISO 26262 Part 6 Matrix Template

Pythongenerate_iso26262_matrix.py

#!/usr/bin/env python3
# Generate ISO 26262 Part 6 compliance matrix skeleton from clause list
import openpyxl
from openpyxl.styles import PatternFill, Font

wb = openpyxl.Workbook()
ws = wb.active
ws.title = "ISO 26262 Part 6"

headers = ["Req ID", "Clause", "Requirement Summary", "ASIL",
           "Responsible", "Work Product", "Status", "Evidence Ref", "Tailoring Note"]
for col, h in enumerate(headers, 1):
    ws.cell(1, col, h).font = Font(bold=True)
    ws.cell(1, col).fill = PatternFill("solid", fgColor="1F4E79")
    ws.cell(1, col).font = Font(bold=True, color="FFFFFF")

# Key ISO 26262 Part 6 requirements
requirements = [
    ("ISO26262-6:7.4.3", "7.4.3", "Software Safety Requirements derived from TSR", "C", "Safety Eng", "SW Safety Requirements Spec", "In Progress", "", ""),
    ("ISO26262-6:7.4.4", "7.4.4", "Software safety requirements are testable", "C", "Test Eng", "SW Safety Req Spec + Test Spec", "Planned", "", ""),
    ("ISO26262-6:8.4.2", "8.4.2", "SW architecture supports ASIL decomposition", "C", "SW Architect", "SW Architecture Design Document", "In Progress", "", ""),
    ("ISO26262-6:8.4.5", "8.4.5", "Freedom from Interference between ASIL partitions", "C", "SW Architect", "FFI Analysis Report", "Planned", "", ""),
    ("ISO26262-6:9.4.2", "9.4.2", "Defensive implementation techniques applied", "C", "SW Developer", "Code Review Checklist + Source Code", "Planned", "", ""),
    ("ISO26262-6:9.4.3", "9.4.3", "MISRA C:2012 applied", "C", "SW Developer", "Static Analysis Report (Helix QAC)", "In Progress", "", ""),
    ("ISO26262-6:9.4.5", "9.4.5", "Robust programming techniques (range checks)", "C", "SW Developer", "Code Review Records", "Planned", "", ""),
    ("ISO26262-6:11.4.3", "11.4.3", "MC/DC coverage criteria for ASIL C/D", "C", "Test Eng", "Unit Test Coverage Report (TESSY)", "Planned", "", ""),
    ("ISO26262-6:12.4.4", "12.4.4", "SW integration test covers component interactions", "C", "Test Eng", "SW Integration Test Report", "Planned", "", ""),
]

for row, req in enumerate(requirements, 2):
    for col, val in enumerate(req, 1):
        ws.cell(row, col, val)
    # Colour-code status
    status = req[6]
    colour = {"Complete":"70AD47", "In Progress":"FFC000", "Planned":"BFBFBF"}.get(status, "FF0000")
    ws.cell(row, 6).fill = PatternFill("solid", fgColor=colour)

wb.save("ISO26262_Part6_Compliance_Matrix.xlsx")
print("Matrix generated: ISO26262_Part6_Compliance_Matrix.xlsx")

ISO/SAE 21434 Matrix Structure

Pythongenerate_21434_matrix.py

#!/usr/bin/env python3
# ISO/SAE 21434 compliance matrix — Clauses 8-15
import openpyxl

wb = openpyxl.Workbook()
ws = wb.active
ws.title = "ISO SAE 21434"

clauses = [
    ("21434-8.3",   "8.3",  "Cybersecurity Policy established",                    "CSMS Manager", "CS Policy Document",      "Complete"),
    ("21434-8.5",   "8.5",  "Cybersecurity monitoring process defined",             "CS Engineer",  "Monitoring SOP",          "In Progress"),
    ("21434-9.3",   "9.3",  "Distributed cybersecurity activities (supply chain)",  "CS Engineer",  "Supplier CS requirements","In Progress"),
    ("21434-10.3",  "10.3", "Cybersecurity goals derived from TARA",                "CS Analyst",   "Security Goal Register",  "In Progress"),
    ("21434-10.4.1","10.4.1","Cybersecurity requirements specified",                "CS Analyst",   "CS Requirement Spec",     "Planned"),
    ("21434-10.4.5","10.4.5","Vulnerability analysis (TARA+pen test)",              "CS Tester",    "Pen Test Report",         "Planned"),
    ("21434-15.3",  "15.3", "TARA performed for each vehicle/component",            "CS Analyst",   "TARA Report",             "In Progress"),
    ("21434-15.4",  "15.4", "Threat catalogue maintained and updated",              "CS Analyst",   "Threat Catalogue",        "In Progress"),
]

headers = ["Req ID","Clause","Requirement","Responsible","Work Product","Status","Evidence","Note"]
for c, h in enumerate(headers,1): ws.cell(1,c,h)
for r, row in enumerate(clauses,2):
    for c, v in enumerate(row,1): ws.cell(r,c,v)

wb.save("ISO_SAE_21434_Compliance_Matrix.xlsx")
print("Matrix generated: ISO_SAE_21434_Compliance_Matrix.xlsx")

Audit Preparation Use

Pre-Audit Step	Action	Timing
Evidence link audit	Test every hyperlink in Evidence Ref column — no 404s	4 weeks before assessment
Status review	Escalate all 'In Progress' items; create completion plans with dates	4 weeks before assessment
Evidence package assembly	Collect all documents into assessor package folder	2 weeks before assessment
Process owner briefing	Each role owner practises answering their ASPICE practice questions	1 week before assessment
Traceability walkthrough	Demo full requirement→test trace path end-to-end	1 week before assessment
Independence declarations	Collect signed assessor CV + independence declarations	Before assessment day

Summary

The compliance matrix is the single most important compliance management tool — it simultaneously serves as audit navigation, project status tracker, and evidence index. Generate the skeleton from the relevant standard clauses, assign owners for each requirement, and update status and evidence links bi-weekly throughout the project. A matrix with zero broken evidence links and no unexplained 'Unknown' statuses is the single most effective pre-assessment preparation investment.

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