Topic · requirements quality

Requirements quality

Gist

Requirements quality is whether each shall still has a rationale, a human-readable description, and FRETish when it should be formalized. Proof fails proof gaps specs/system --check quality when those fields are empty. A green description is not that. Jama still scores the programme. Jama still authors.

proof gaps specs/system --check quality

Keep INCOSE if you already teach the writing rules. Keep Jama if you author shalls. Proof will not treat an empty FRETish as a silent zero-of-zero pass.

Request demo Last green description vs this record

01 · The silent empty formula

A readable shall that the solver never saw.

The YAML landed. The description is English. The FRETish field is still blank.

Jama will score a requirement for completeness, consistency, correctness, clarity, testability. That is a programme score. Proof's quality check is narrower. It looks at five classes on the files you already have: missing rationale, missing description, empty FRETish on a requirement that should be formalized, a stale draft that has already been revised, and high churn.

The motivating miss is mechanical. SYS-REQ-410 says the system rejects expired tokens. A reviewer can read the sentence. fretish is "". Downstream solver checks report zero of zero, because there is nothing to discharge. The suite is green. The intended deny path was never a formula.

The command is deterministic. It does not score IEEE quality attributes. It does not run an INCOSE workshop. It lists the files that still fail the five classes.

proof gaps specs/system --check quality --verbose
proof workflow check --stage spec --verbose

The first command names the files. The second fails the spec stage when an actionable class is still open. A green suite next to empty FRETish is how the guessed shall shipped.

02 · The exhibit

Same YAML. A green description, or this record.

The sentence is there. The formula is not. Click the tabs.

The file

Said System rejects expired tokens
FRETish empty string
Solver zero of zero, nothing to discharge

Suite green

This hop

No rationale. No formula. No quality finding. The deny path is still English, on main.

No record

The file

Keep the description. Keep the id. They are not the quality hop.

Keep the sentence

Proof

Ask did this shall leave FRETish empty when it should be formalized
Out fail until the class is closed

A green description is not quality

Same YAML. A green description, or this record. Click the tabs.

Surface	What they do	What Proof does	What we lose
Jama	Score completeness, consistency, correctness, clarity, testability on the programme.	Fail five classes on the files: rationale, description, empty FRETish, stale draft, high churn.	Not Jama's quality score. Jama still authors.
INCOSE Guide	Writing rules for the shalls. INCOSE.	Whether the fields that those rules need are actually present. Different command.	Not the Guide. Keep the course they already run.
Requirements completeness	Whether catalog ids, classes, signal rules, and checklists still agree. requirements completeness.	Quality of one shall, not agreement of four ids.	Not `catalog_completeness`.
ASD-STE100	Simplified Technical English as a lint on the YAML. ASD-STE100.	Whether rationale and FRETish exist, not whether the prose is STE.	Not the STE dictionary.
Requirement lifecycle	The status hop on one shall. requirement lifecycle.	Stale draft is one quality class. The hop itself stays on that URL.	Not `proof req status`.

The teaching graph is still an empty FRETish next to a readable sentence. Write the formula, or move the requirement to an informal strategy on purpose. High churn alone is informational. The check still passes unless another class is open.

id: SYS-REQ-410
description: System rejects expired tokens.
fretish: ""

proof gaps specs/system --check quality --verbose
proof audit --check quality_clean
proof workflow check --stage spec --verbose
proof help quality_clean

Actionable classes are missing rationale, missing description, empty FRETish, and stale draft. High churn is a signal to split the shall, not a red by itself. Per-class waivers need a reviewer, a reason, and an expiry. See requirements assumptions if the missing field is an assumption, not a quality hole.

03 · The honest loss

Proof names the empty field. It does not score the programme.

A present rationale is not a proof of the Go. Jama still authors.

Proof does not implement Jama's quality dashboard, INCOSE's attribute list, or IIBA's quality requirements. It does not infer FRETish from English. A filled formula is not proof the Go matches the shall. We have not scored this against a frozen Jama quality pack. The loss is named, not scored.

quality_clean stays on this URL as the CI floor, not a twin. Completeness of the catalog stays on requirements completeness. The writing rules stay on INCOSE. Jama still authors.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What is requirements quality? Same question. Same URL.

What are quality requirements? PMI and ICR mean non-functional criteria the product must meet. Different cluster. Not this URL.

How do I measure requirements quality? Same cluster. Jama's score is the programme. This URL is the five classes on the files.

What is requirements completeness? Whether four ids still agree, not whether FRETish is empty. requirements completeness.

What is the INCOSE Guide for Writing Requirements? The writing rules for the shalls. INCOSE.

What is a requirement lifecycle? The status hop, not the quality classes. requirement lifecycle.

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