Skip to content

Glossary Requirements & traceability

What is requirements traceability?

Requirements traceability links each requirement to where it came from, what satisfies it and how it is verified, so the effect of a change can be followed.

Also called requirements tracing.

Requirements traceability

Requirements traceability is the ability to follow a requirement in both directions: back to its source, such as a stakeholder need or a parent requirement, and forward to the design elements that satisfy it and the verification that proves it. The links are usually typed, for example derives, satisfies and verifies, and are often reviewed as a traceability matrix.

Why it matters

Requirements change. Traceability tells you what a change touches: which parts, which derived requirements and which verification activities. It also shows the gaps, such as requirements nothing satisfies and requirements with no plan to verify them.

How it goes wrong

  • Keeping requirements in a spreadsheet with no link to the design
  • Rebuilding the trace matrix by hand just before a review
  • Reading a requirement's status as proof that it has been verified

In Cairn

In Cairn, trace links are records in the model, each with a type: satisfies, implements, verifies, derives or depends on. A requirement counts as traced when a link that hasn't been rejected touches it. The Trace tool lists every requirement with the node that owns it, what satisfies it, what verifies it and its status, and AI can suggest links that you review in Change Review. Untraced, unverified and failing requirements show as gap chips in the Requirements lens. Cairn connects to no requirements tool outside it: requirements export as a CSV table, and the full project export holds every trace link as JSON.

Questions

Is a requirements spreadsheet traceability?
Only if it records the links: where each requirement came from, what satisfies it and what verifies it. A list of requirements on its own is not traced.
What is a traceability matrix?
A table that lists requirements against what they link to, such as the design elements that satisfy them and the activities that verify them. Its empty cells are the gaps.

See it on your own system.

Describe what you are building and Cairn interviews you, then builds the first model with you.