Business Analysis Academy · Interactive Learning Tool

Requirements Traceability Matrix

Build bidirectional traceability from business need and source through requirement, solution deliverable, acceptance criteria, verification evidence and status. Detect coverage gaps and use linked artifacts to assess the impact of change.

Start the Demonstration View Quick Reference
Demonstration at a glance
Level Foundation–Intermediate
Typical duration 15–20 minutes
Traceability Upstream · Requirement · Deliverable · Acceptance · Test
Mobile design Traceability cards below 1180px; no compressed matrix text
Demonstration overview

Trace Every Requirement From Rationale to Verification.

A Requirements Traceability Matrix (RTM) provides structured evidence that each requirement is justified, implemented and appropriately verified. It also makes gaps and change impacts visible.

  • Trace requirements upstream to business need and source.
  • Trace requirements downstream to solution deliverables and verification evidence.
  • Use stable requirement identifiers to preserve link integrity.
  • Detect requirements that lack test coverage or complete acceptance evidence.
  • Use bidirectional links to assess change impact quickly.
Guided Demonstration

Requirements Traceability Matrix — Step by Step

Eight locked stages move from traceability purpose and requirement baseline through upstream/downstream links, verification coverage, change impact and management review.

Learning stages
Foundation Stage 1 of 8

Understand the Traceability Purpose

Current instruction
Interactive RTM Workspace

Customer Onboarding Portal — Release 1

Reveal the traceability context before building the matrix.

100%
RTM status: Review the traceability context.
Supporting Traceability Register

Requirement Traceability Register

The complete requirement set is shown as responsive cards so rationale, implementation and verification links remain readable on smaller screens.

Experiment Mode

Trace the Impact of a Requirement Change

Experiment Mode is isolated from the guided RTM. Select a requirement and simulate a change to see which linked artifacts should be reviewed.

Check Your Understanding

Quick Knowledge Check

Choose an answer, then check it.
RTM Quick Reference

Traceability Directions and Uses

Upstream

Requirement → business need, objective, stakeholder source, policy or other rationale.

Downstream

Requirement → solution component, design artifact, deliverable, test case or operational artifact.

Bidirectional

Links can be followed both backward and forward to support coverage and impact analysis.

Coverage

Check whether every baselined requirement has the required rationale, implementation and verification evidence.

Traceability principle: a requirement that exists in a matrix but has no meaningful upstream or downstream links is not fully traceable.