Arc Skills / Verification and validation
Write a test procedure for a requirement
Arc Skills turns an approved requirement and criterion into operator-ready Test steps for a named article. It keeps missing safety or measurement choices as placeholders rather than recording a fictional Run.
Use this skill
Use Arc Skills to write a test procedure for the supplied requirement.
Inputs:
- Requirement revision and approved acceptance criteria
- Test article, configuration, interface events, and observation sources
- Facility safety limits, calibration, abort, and restoration rules
Return an objective, prerequisites, numbered action/expected-result steps, data fields, and decision rule.
Mark absent limits or sensor definitions as blocked. Draft procedure content only; do not invent a completed RunWhat you provide and what you get
| What you have | How it is used | What you get |
|---|---|---|
| Requirement and criterion | Fixes trigger, outcome, and pass bound | Test objective and rule |
| Article and equipment | Defines safe setup and measurement points | Prerequisites and data fields |
| Safety/restore instructions | Controls abort and as-left state | Executable step sequence |
Valve closure procedure excerpt
Illustrative engineering example.
The approved time bound is 2 s. The illustrative draft shows where the facility must supply closed-state confirmation, calibration status, and safe stop rules before execution.
R-4: Valve V-2 shall close within 2 s after Controller C2 accepts a valid close command.
Article: V-2 / C2, baseline B.
Open: closed-state sensor definition; approved abort threshold; timebase calibration record.| Step | Operator action | Expected result / record |
|---|---|---|
| Prerequisite | Confirm article B, valve open, safe facility state, and timebase calibration. | Record serials, configuration, calibration ID; block if absent. |
| 1 | Issue one valid close command through the approved interface. | Record command acceptance t0 and command ID. |
| 2 | Observe independent closed-state indication. | Record t1, raw trace, and sensor definition; stop if unsafe condition occurs. |
| 3 | Calculate t1 − t0 and compare with ≤2 s. | Record result and uncertainty under approved rule; log anomaly separately. |
| Restore | Return valve and facility to approved as-left state. | Record final position and any deviation. |
The procedure records both ends of the timing interval. A “command sent” indicator alone would prove only transmission, not valve closure. The raw trace and article identity make later reassessment possible.
The draft remains blocked for execution where closed-state confirmation, calibration, and abort conditions are not supplied. Those placeholders are project decisions, not reasons to fabricate safe limits.
Make every step produce useful evidence
- State objective, exact article, baseline, and approved criterion.
- Set preconditions and equipment records before applying the stimulus.
- Separate operator action from expected result and raw data to retain.
- Include credible abort, anomaly, and restoration paths without inventing thresholds.
Questions about this task
Is the calculated pass a recorded Run?
No. This is a procedure draft. A Run exists only after an actual execution record is created.
Can the operator infer closure from a command light?
No. The criterion requires a closed-state observation; specify and approve that indication first.
Sources and further reading
- NASA Systems Engineering Handbook: Lifecycle and requirements guidance; the example decisions are illustrative.