Document structure and contents
Proposed contents for the hydrotest procedure over SYS-12-01. Nothing is generated until you approve it.
WhyBack
Demonstration project - no figure here describes a real facilityChanges are not saved
Approve outline and generateWhy
The outline and the gap against each section are derived from the checklist over the project's own records. A section whose input is missing is shown with the gap, rather than generated with a plausible value in it.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Proposed contents
- 1. Purpose and scope1 gap(s)
- 2. Referencesmandatory
- 3. Responsibilities1 input(s)
- 4. Test medium1 input(s)
- 5. Test parameters2 gap(s)
- 6. Procedure2 gap(s)
- 7. Recordsmandatory
- 8. Hold points1 input(s)
- 9. Acceptance criteria1 input(s)
Section 1 Purpose and scope
Gap
Intent: State the system and lines covered and the purpose of the test
Waiting on: Lines within the boundary
Generation will state the gap in place of the value, with its reason.
Mandatory sections come from the type
Removing one is recorded, and appears in validation.
What generation will do
- Draft each section only from the evidence listed against it.
- Attach citations to every material statement.
- Insert the gap marker where evidence is missing, with the reason.
- Build the mandatory tables from the registers, not from prose.