Requirements Traceability Template

Template for documenting requirement relationships and coverage
Auteur
Affiliations

Emmanuel BRUNO

Université de Toulon

LIS UMR CNRS 7020

Date de publication

2026-10-03

This template provides a structured format for maintaining traceability between requirements artifacts. For more information, see the Requirements Engineering Guide.

Key Relationships

1. Business to System Requirements

Business Req ID System Req ID Description Status Verification Method
BR-001 SR-001, SR-002 [Brief description] [Status] [Test/Review/Demo]

2. Requirements to Implementation

System Req ID Component ID Design Doc Reference Status Verification
SR-001 COMP-001 design/component-001.md [Status] [Method]

3. Requirements to Verification

Requirement ID Test Case ID Test Description Status Last Execution
SR-001 TC-001 [Test description] [Status] [Date]

User Stories to Requirements

User Story ID Requirement ID Story Points Sprint Status
US-001 SR-001, SR-002 [Points] [Sprint] [Status]

Interface Requirements to Components

Interface ID Component ID Documentation Ref Status Notes
IF-001 COMP-001 interfaces/if-001.md [Status] [Notes]

Cross-Reference Matrix

ID BR SR TC US IF
001 ✓ ✓ ✓ ✓ -

Coverage Analysis

Requirement Coverage

  • Business Requirements: [Percentage]% covered
  • System Requirements: [Percentage]% covered
  • Test Coverage: [Percentage]% covered

Gap Analysis

  • Uncovered Requirements: [List of IDs]
  • Missing Test Cases: [List of requirements]
  • Incomplete Traces: [List of items]

Version History

Version Date Description Author
1.0 YYYY-MM-DD Initial version [Name]

Appendices

Legend

  • ✓: Direct relationship
  • △: Indirect relationship
  • -: No relationship
  • TBD: To be determined

Réutilisation