Skip to main content

ISO 26262

ISO 26262 governs functional safety for road vehicles. TRF supports ISO 26262 compliance by capturing hazard analysis, safety requirements, verification evidence, and safety case documentation in a single package.

Part-by-part coverage​

ISO 26262 partTRF focus
Part 3 – Concept phasehazard, safety_goal, and item_definition artifacts with ASIL ratings and operational context
Part 4 – Product development at system levelSystem requirements (requirement), architecture (design), safety mechanisms, integration tests
Part 5/6 – Hardware & software developmentComponent artifacts with build_info, unit/integration test evidence, failure rate data
Part 7 – Production & serviceProcess artifacts (work_instruction, maintenance_plan) plus linkage to compliance reports
Part 8 – Supporting processesConfiguration management (manifest.json history), change management links (change_request artifacts)
  • Start with the automotive_safety profile (core + safety extension + validation rules).
  • Enable the cybersecurity extension if ISO/SAE 21434 or UN-R155 is also in scope.
  • Add custom artifact types for company-specific templates (e.g., safety_case_argument, tool_qualification).

Traceability model​

hazard --> safety_goal --> safety_requirement --> design --> component --> test
  • hazard artifacts capture HARA entries (severity, exposure, controllability).
  • safety_goal collects top-level goals with FTIs and safe states.
  • safety_requirement is derived and allocated (hardware, software, human) with ASIL decomposition captured in validation rules.
  • design and component artifacts implement safety requirements.
  • test artifacts verify requirements; link coverage demonstrates achieved ASIL.

Safety case packaging​

  • Assemble the safety case using structured artifacts (safety_case, evidence_reference).
  • Link claims to supporting evidence (tests, analyses, design reviews).
  • Use the viewer’s coverage dashboard to demonstrate requirement/test completeness per ASIL.

Verification and confirmation measures​

  • Store confirmation reviews (FMEA, FTA, code walk-throughs) as artifacts with reviewer metadata.
  • Attach supporting documents (PDF reports, spreadsheets) under attachments/ with hashes.
  • Use tw export --format iso26262 to generate assessor-friendly summaries.

Tips for assessments​

  • Baseline each safety release by tagging the TWPack in git (safety-v1.4) and archiving the signed package.
  • Provide assessors with the package plus a viewer snapshot; they can inspect coverage and drill into attachments.
  • Track open assessment findings as artifacts linked to the impacted requirements/tests.

For related standards and cross-mappings, see Automotive SPICE and UN-R155/R156.