ZRF-PEP-0001-RA validation
Every gate between this deliverable and issue, with what would have to happen for each failure.
Demonstration project - no figure here describes a real facilityChanges are not saved
Why
Each gate is evaluated against the project's own records when the page renders.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Gates
8
Passed
6
Failed
2
Blocking issue
1
This deliverable cannot be issued
1 gate fails. A validation page that reported a score would let somebody read “eight of ten passed” as nearly ready, when one of the two failures is a safety-critical value two documents disagree about.
Gates
| Gate | Outcome | What was found | What would fix it |
|---|---|---|---|
| Required inputs present | Pass | every required input is held | — |
| Source documents readable | Pass | every source document has been read | — |
| Requirements accepted | Pass | every attached requirement has been accepted | — |
| No open blocking comment | Pass | no blocking comment is open | — |
| Independent check assigned | Pass | checked by R. Haddad | — |
| Approver is not the author | Pass | approval would be by R. Haddad | — |
| No safety-critical value in conflict | Fail | P-1201A, PT-1201, HV-3101, 12-CD-1201-150-A1A in conflict | decide which document governs on the reconciliation page |
| Template conformance | Cannot be checked | no client template has been supplied, so conformance cannot be checked | obtain the client's controlled template |
A gate nobody can check
Template conformance is reported as not checkable rather than as passing. No client template has been supplied, so there is nothing to conform to - and a gate that passes because the check was skipped is worse than one that fails, because it appears in the record as evidence.