Node A2

Requirements Statement Checker

Paste requirements — one per line — and get them back marked up like a reviewer with a red pen: EARS pattern classification plus defect flags for the failure modes that survive most peer reviews.

What gets checked

Each statement is classified against the EARS patterns — ubiquitous, event-driven (when), state-driven (while), optional (where), and unwanted behaviour (if/then) — and then run through defect rules drawn from INCOSE-style guidance: weak verbs in place of shall, unverifiable vague terms, escape clauses, compound requirements, unresolved pronouns, passive voice that hides the actor, open-ended lists, and numbers missing units.

Everything runs locally in your browser. Nothing you paste is transmitted anywhere, which matters when the spec is not yours to share.

New to the notation the checker classifies against? The guide How to write EARS requirements (with worked examples) walks through all five patterns and rewrites weak requirements step by step.