Arc Skills / Technical management and design reviews

Prepare a system requirements review

Use Arc Skills to prepare a system requirements review around whether the requirements basis is credible enough for the next phase. Get an evidence index, readiness findings and board questions about scope, feasibility, interfaces and verification.

Use this skill

Use Arc Skills to prepare a system requirements review.

Inputs:
- Mission scenarios, stakeholder sources and requirement baseline
- Interface/environment definitions and feasibility evidence
- Verification concepts, risks, open actions and review criteria

Return an SRR readiness matrix, evidence index and board questions. Preserve exact requirement revisions. Distinguish requirement-basis blockers from issues with a supported closure plan.

Set up the toolkit · Read the skill instructions

What you provide and what you get

Inputs and outputs
What you have	How it is used	What you get
Sources, scenarios and requirements	Check the basis and scope	Coverage and conflict findings
Feasibility and verification concepts	Check credible obligations	Unresolved limits and methods
Project review criteria and actions	Frame phase-entry decisions	An evidence-backed SRR packet

An SRR finds a missing operating environment and conflicting timing

Illustrative engineering example.

The draft baseline contains 24 requirements. A targeted packet checks the decisions needed to make that basis coherent; it does not pretend that sampling constitutes review of all 24 rows.

Scope: 24-row baseline R3; sampled concerns below.
REQ-04 latency ≤100 ms; REQ-19 allows a 150 ms polling interval for the same mode.
REQ-12 uses operating environment [TBD]. Customer loss-of-power scenario has no recorded requirement.
REQ-07 dimension limit has a proposed inspection method and allocation.

An SRR finds a missing operating environment and conflicting timing
Review question	Available evidence	Finding	Required action / owner
Requirement consistency	REQ-04 / REQ-19 in R3	Potentially conflicting timing obligations under the same mode	Timing owner reconciles behavior and confirms interpretation
Operating environment	REQ-12 environment [TBD]	Feasibility and qualification basis incomplete	Mission owner supplies controlled environment before baselining that obligation
Scenario coverage	Loss-of-power customer scenario, no trace	Missing obligation candidate	Requirement owner determines needed shutdown/recovery requirements
Verifiability sample	REQ-07 dimension limit and inspection concept	Sample has a measurable acceptance basis	Retain evidence; do not extrapolate to the remaining 23 requirements
Board packet	R3 inventory, evidence locators and owner list	Material open decisions identified	Board applies project SRR criteria to proceed, condition or defer

The SRR asks whether the requirements basis can support development. It does not require production drawings or completed qualification as its central evidence.

The table gives a bounded review sample, not a 24-row coverage claim. An owner can now see which missing decisions threaten the baseline and which already have a credible verification concept.

Prepare decisions about the requirements basis

Reconcile the requirement inventory, sources, modes and operating environments.
Check conflicts, omissions and feasibility with the supplied architecture and budgets.
Sample or fully review verifiability according to the declared scope; expose absent acceptance limits.
Build an evidence index and specific board questions using the project’s entrance and success criteria.

Questions about this task

Must every open action prevent SRR completion?

Use the governing criteria. An undefined mission environment can undermine the requirements basis; a bounded documentation action may have an accepted closure plan. Describe the consequence and required authority.

Sources and further reading

NASA NPR 7123.1D, Appendix G: life-cycle review criteria: A NASA reference for different review purposes. Use your project’s governing review criteria.
NASA Systems Engineering Handbook: technical assessment: Background on measures, review evidence and action resolution.

References inspected on 3 October 2026. The worked output is an authored example using the stated inputs.