Topic · requirement review

Requirement review

Gist

Requirement review is one shall with its traces, witnesses, and impact in one brief. Proof runs proof review req SYS-REQ-010. A Slack walkthrough is not that brief. It does not move status. Jama still authors.

proof review req SYS-REQ-010

Keep Visure if you already run the meeting. Keep Jama if you author shalls. Proof will not treat a Slack “we reviewed it” as the brief.

Request demo Last Slack walkthrough vs this brief

01 · The missed slice

The shall is open. The slices never sat together.

Status says review. The tests exist. The impact list is in another command. Approval is a guess until they are one brief.

Bridging the Gap and Visure will tell you a requirement review is a walkthrough meeting. SRR is the milestone where the system shalls are declared testable. That is not this URL. Proof's proof review req is the deterministic brief for one id: what the shall currently says, which tests and witness rows support it, which implementation and suspect-link evidence surrounds it, whether the spec looks too weak for the observed code, and what to inspect next.

The motivating miss is mechanical. SYS-REQ-010 is in review. proof req show prints the text. The verifying tests exist. Nobody opened proof mcdc show, proof trace impact, and the suspect-link list in the same sitting. The reviewer approved the paragraph. The richer tests and the weaker variables never met.

The command does not call a model. It does not change lifecycle status. Status stays on requirement lifecycle. The SRR gate stays on system requirements review.

proof review req SYS-REQ-010
proof review req SYS-REQ-010 --gate --run

The first command is the brief. The second is the checklist-ready loop. A green show next to an unopened impact list is how the guessed shall shipped.

02 · The exhibit

Same shall. A Slack walkthrough, or this brief.

The id is in review. The slices are not. Click the tabs.

The thread

Status review
Show the paragraph, no traces
Chat we reviewed it

Thread green

This hop

Impact, witnesses, and suspect links sit in other commands. The approval is a guess.

No brief

The thread

Keep Slack. Keep the meeting. They are not the review hop.

Keep the meeting

Proof

Ask one shall, traces, witnesses, impact
Out the brief, or the next file to open

A Slack done is not a brief

Same shall. A Slack walkthrough, or this brief. Click the tabs.

Surface	What they do	What Proof does	What we lose
Visure / walkthrough	A meeting. Stakeholders walk the document page by page.	One id. Traces, witnesses, impact in one brief.	Not the meeting. Keep the room they already run.
System requirements review	The milestone that the system shalls are testable. SRR.	Per-requirement brief. Not the gate.	Not `proof gate srr`.
Requirement lifecycle	The status field: draft, review, approved. requirement lifecycle.	The brief. It does not move status.	Not `proof req status`.
Jama	The authoring programme. Reviews live on the item.	Fail the missing slice on the files. Next file to open.	Not Jama's review. Jama still authors.

The teaching graph is still a shall in review next to an unopened impact list. Run the brief before you approve. Three traps ship through hand-edits that did not open the slices: show-only, tests without witnesses, and richer code than the variables explain.

proof review req SYS-REQ-010
proof review req SYS-REQ-010 --format json
proof review req SYS-REQ-010 --gate --run --full

JSON is for the agent. --gate --run is the checklist loop. Neither writes a new status. See requirement lifecycle if the failure is a Slack done that never became review. See system requirements review if the failure is the milestone, not one id.

03 · The honest loss

Proof names the brief. It does not run the meeting.

A complete brief is not a proof of the Go. Jama still authors.

Proof does not implement Visure's walkthrough, Bridging the Gap's stakeholder meeting, or an SRR board. It does not call a model. It does not move lifecycle status. A brief that lists traces is not proof the Go matches the shall. We have not scored this against a frozen Visure review pack. The loss is named, not scored.

Status stays on requirement lifecycle. The SRR gate stays on system requirements review. Jama still authors.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What is a requirement review? Same question. Same URL.

What is a requirements review? Same cluster. The meeting is the room. This URL is the brief on one id.

What is a system requirements review? The milestone. system requirements review.

What is requirement lifecycle? The status field. This command does not move it. requirement lifecycle.

What is approvals current? Whether a required approval still matches the authored fingerprint. See approvals current.

What is requirements quality? Whether rationale and FRETish are present. requirements quality.

Is Proof a Jama alternative for reviews? No. Jama still authors. Proof vs Jama.