Requirements extraction

Every requirement the project has extracted, with its source, its classification and whether anybody has accepted it.

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

Why

Requirements are read from the project's specifications and contract appendices. A clause from an unlicensed standard is cited and never reproduced.

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

Requirements

Mandatory

Suggested by the model

never verified on arrival

Accepted

In conflict

Requirements (2)
Reference	Requirement	Source	Clause	Class	Discipline	Confidence
REQ-D-003	An inspection and test plan shall be submitted for each work package, identifying every hold point and witness point.	ZRF-CTR-APX-D	Appendix D clause 3.2	mandatory	QUA	90%Unverified	Accepted
REQ-D-011	Pressure testing shall be witnessed by the Company representative and the record signed before reinstatement.	ZRF-CTR-APX-D	Appendix D clause 6.4	mandatory	QUA	85%Unverified	Not accepted

Showing 1 to 2 of 2 requirements

Per page10 25 50 100

Page 1 of 1

A model suggestion is not a requirement

A requirement the model proposed is marked as suggested and is never accepted on arrival. Somebody has to agree that an extracted sentence is a requirement before it is treated as one, or the model is writing the contract.

Accept a requirement

Cited, never quoted

A requirement from a standard the project holds no licence for shows its reference, clause and applicability, and the clause text is marked as not reproduced. The reference is the project’s own work; the text belongs to the standards body, and reproducing it in a deliverable is a copyright problem the client inherits.

Applicability is not classification

“Mandatory” says how the source phrases it. Whether it applies to a particular deliverable is a separate judgement, made per deliverable, and shown on the traceability matrix.