Requirements traceability matrix

Requirement to deliverable and back again. The two directions fail differently and both are shown.

Demonstration project - no figure here describes a real facilityChanges are not saved

Why

A requirement counts as traced only when the deliverable answering it can actually be approved. An answer nobody has accepted is not an answer.

Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.

Requirements

Traced to an approved deliverable

Answered by a draft

Answered by nothing

Requirement to deliverable
Requirement	What it requires	Source	Answered by
REQ-SUG-001	Consider recording ambient temperature at the start and end of the hold period, to explain a pressure change that is thermal rather than a leak.	ZRF-SPC-3300	nothing	Unanswered	Start one

REQ-SUG-001

informative · PIP

Suggested by a model, not read from the document

This was proposed rather than extracted, so the wording here is a reading of the source and not a quotation from it. An engineer who builds a test to an inferred clause finds out at the hold point.

What it says

Consider recording ambient temperature at the start and end of the hold period, to explain a pressure change that is thermal rather than a leak.

Where it comes from

Document: ZRF-SPC-3300
Revision: C1
Location: clause 18
Taken: Model suggested
Extraction confidence: 50%

The clause, not only the document. A requirement cited to a forty-page specification without a location is one somebody has to find again.

Checked by a person

Not verified

Nobody has confirmed that this wording matches the clause it was taken from. The text may still be right; it has not been checked.

What has to satisfy it

No deliverable cites this requirement yet.

The deliverables that cite it. If this requirement moves, each of these has to be looked at again.

Applies to

HTP

Open the source clause

Resolve the conflict

Nothing contradicts this requirement.

Trace it