Automotive SPICE

Automotive SPICE (ASPICE) evaluates process capability across development, testing, and support processes. TRF helps teams collect the evidence needed for capability levels 1–3.

Key process areas and TRF artifacts

ASPICE process	Evidence expectations	TRF mapping
SYS.2 System Requirements	Documented, traceable system requirements	requirement artifacts with status, rationale, acceptance criteria
SYS.3 System Architectural Design	System architecture and interfaces	design artifacts (interfaces, constraints), links implements
SWE.1 Software Requirements	Software requirements and traceability	Namespaced requirement artifacts grouped by subsystem
SWE.3 Software Detailed Design	Module-level designs and interfaces	design/component artifacts with interface definitions
SWE.4 Software Construction	Implementation units and build data	component artifacts with build_info, dependencies
SWE.5 Software Integration & SWE.6 Qualification Testing	Test plans, results, coverage	test artifacts, verified_by links, coverage reports
MAN.3 Project Management	Plans, monitoring, risk tracking	requirement + custom types (project_plan, risk_register)

Capability level checklist

Level	What TRF helps demonstrate
CL1 – Performed	Existence of work products (requirements, designs, tests) recorded as artifacts with completion status.
CL2 – Managed	Evidence of planning, monitoring, and traceability (links, coverage metrics, versioned TWPack releases).
CL3 – Established	Standardized processes captured in profiles, automated validation, clear responsibilities via created_by/approved_by fields.

Linking patterns

• requirement → design (implements) → component (realizes).
• requirement → test (verified_by).
• hazard → safety_requirement for safety-related processes.
• Use confidence to flag weak or manual trace links for follow-up during assessments.

Evidence packages for assessments

1. Build a TWPack per release or major milestone.

2. Export summary reports for assessors:

   tw export out/traceability.twpack --format aspice --output reports/aspice-summary.html

3. Provide the TWPack plus HTML/PDF exports ahead of the on-site assessment.

4. During the audit, use the viewer to answer drill-down questions quickly.

Tips

• Tag artifacts with process identifiers (tags: ["SWE.1"]) to filter evidence per process area.
• Store ASPICE assessment findings as custom artifacts (assessment_finding) linked to remediation tasks.
• Use coverage thresholds in profiles to enforce minimum verification levels before gate reviews.

For cross-standard mappings, continue to Compliance Mapping or review detailed automotive safety requirements in ISO 26262.