Topic · System requirements review

What is a system requirements review, and how do I keep it true in CI?

Gist

A system requirements review is a NASA lifecycle gate: are the requirements complete enough to start design. Proof assesses that gate from the current graph with proof gate srr, then fails the merge when a criterion is not ready.

proof gate srr

Keep Jama if you author the programme. Keep the review board if a human has to accept the shalls. Proof is not that meeting, and last month's SRR pack is not this push.

Request demo Last pack vs this graph

01 · The dated pack

A procedure PDF is not an SRR. Last review's pack is not this push.

The review board looks at whether the requirements are defined, testable, and consistent with cost and risk. A person can sign that once. The next commit does not reopen the room.

The architecture gate lives on preliminary design review. The detailed-design gate lives on critical design review. The test gate lives on test readiness review. This page is the first gate: requirements exist, validate, levels connected, not all still draft, no blocking accepted risk.

SRR does not invent a shall you did not write. It does not sit in the review. It does not replace NPR 7123. Keep proof validate.

proof validate
proof gate srr
proof audit --fail-level warn

The first command is still the YAML. The second assesses the SRR criteria and exits 0 (ready), 1 (not ready), or 2 (ready with observations). The third is the standing merge gate. Printing last review's pack after the gate is how the minutes got stale.

02 · The exhibit

Same agenda. A date, or this graph.

The pack still has requirement headings. Every active shall is still draft. Click the tabs.

Word / Confluence

Opened shalls from last SRR
SYS-REQ-010 still listed in the pack

Agenda present

This push

Every active requirement is still draft. The pack did not say that.

No re-assess

Word / Confluence

Still last SRR. Still a date.

Keep the review minutes

Proof

Ask does srr still pass
Exit 1 if all active reqs are draft

Merge blocked if the gate is not ready

Same agenda. A date, or this graph. Click the tabs.

Criterion	What the graph asks	What a green cell is not
Requirements exist	`stakeholder_requirements_exist`	Not a stakeholder workshop. Keep the board.
Requirements validated	`validate_passes`	Not a proof the shall is the right shall.
Levels connected	`l0_stakeholder_complete`, `l1_system_complete`, `levels_connected`	Not NPR 7123 system-of-systems allocation.
Reviewed beyond draft	no active requirement remains `draft`	Not a signature. Mid-review is a warning, not a pass.
No blocking accepted risks	no active risk with release disposition `block`	Not a residual-risk certificate. Keep `proof risk list`.

The same assessment also asks for stakeholder acceptance criteria, system requirements linked, gaps clean, and quality clean. Formats for the assessment itself:

proof gate srr
proof gate srr --format json
proof gate srr --format markdown

Table is the default. JSON is for CI. Markdown is for a comment. SRR does not write a SAS. That pack is only proof gate sar --output sas.html on software accomplishment summary.

We have not run these gates against a frozen NASA review-board corpus, and we have not scored them against an AAF or AcqNotes pack on the same branch. The loss is named, not scored.

03 · The honest loss

A green Proof gate is not a system requirements review.

The command reports criteria on the authored model. Proof will not pretend that exit 0 is a board signature.

NPR 7123 still wants a human to judge whether the system requirements are defined and the project is ready to proceed into design. The CLI name is Software Requirements Review. It lists what you declared on the corpus: existence, YAML, levels, draft status, blocking risks. It does not independently prove those declarations are the right system. Keep the SRR. Keep the minutes.

Proof is not NASA. It is not OSMA IV&V. It is not DO-330 qualified. It is not a configuration control board. Tests are not executed by proof gate srr. Keep proof validate. Jama still authors the shall. VectorCAST or LDRA still win at a qualified C toolchain.

The architecture gate still lives on preliminary design review. The detailed-design gate still lives on critical design review. The NASA SRS still lives on NPR 7150.2D. The four jobs still live on DO-178C-style verification.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What is a software requirements review? Same command. proof gate srr. The Ads head people type is system requirements review. One URL.

What is a preliminary design review? PDR is architecture and interfaces before detailed design. That H1 lives on preliminary design review as proof gate pdr.

What is a critical design review? CDR is detailed design against the code annotations. That H1 lives on critical design review as proof gate cdr.

What is a test readiness review? TRR is the test gate. That H1 lives on test readiness review as proof gate trr.

What is a software accomplishment summary? The SAR pack. That H1 lives on software accomplishment summary as proof gate sar --output sas.html.

Is Proof an alternative to an SRR board? No. The board still signs. Proof re-assesses the graph you already keep. Jama still authors.

What is NPR 7150.2D? NASA's software engineering procedure. The SRS artefact lives on that URL. This page is the first gate, not a twin.