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-S-3300-22	The test pressure shall be held for not less than 2 hours with no visible leakage and no pressure loss.	ZRF-SPC-3300	ZRF-HTP-0015	Drafted, not approved	Open

REQ-S-3300-22

mandatory · PIP

What it says

The test pressure shall be held for not less than 2 hours with no visible leakage and no pressure loss.

Where it comes from

Document: ZRF-SPC-3300
Revision: C1
Location: clause 22.1
Taken: Read from the source
Extraction confidence: 93%

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

Verified against the source

Contradicted by

REQ-D-011Open
Pressure test hold period
The specification requires a 2 hour hold; Appendix D requires the hold to be witnessed and signed, which the contractor has read as 1 hour. The contract takes precedence over the specification and the question is which clause actually states a duration.

Two requirements that disagree cannot both be satisfied, and an undecided one blocks: recording either as verified would record an agreement the project has not reached.

What has to satisfy it

ZRF-HTP-0015in review

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 Trace it