Requirements Quality Check

Purpose

Evaluate whether requirements are clear, feasible, testable, prioritised, and traceable.

Use when

• a requirements set is nearing signoff
• acceptance or implementation work depends on requirement quality
• the team wants objective gates

Inputs

• artifact or analysis output under review
• source material and assumptions
• project context and quality bar

Procedure

1. Inspect the artifact systematically.
2. Look for omissions, contradictions, weak assumptions, and vague language.
3. Distinguish evidence-backed claims from inference.
4. Record issues by severity.
5. Recommend targeted fixes, not generic criticism.
6. Re-state what would make the artifact review-ready.

Outputs

• requirement quality assessment
• ambiguous/non-testable items
• prioritisation issues
• traceability gaps
• release readiness judgement

Guardrails

• Be concrete.
• Do not rewrite the whole artifact unless necessary.
• Focus on the highest-leverage defects first.
• Prefer explainable quality gates.

Completion criteria

• key defects identified
• fixes proposed
• pass/fail or ready/not-ready decision given