Requirement Analyser
Paste any requirement and get an instant AI quality score against all 6 IREB CPRE criteria — with automatic EARS rewrites and risk flags. Free, no login, results in under 3 seconds.
Why Requirement Analyser Exists
Most bad requirements aren't wrong on purpose — they're written in natural language, under deadline pressure, with no way to self-check before they ship. "The system shall be fast" passes a skim-read and fails the moment two engineers implement two different definitions of "fast." Requirement Analyser catches exactly this class of problem — ambiguous language, missing acceptance criteria, untestable statements — the moment you draft a requirement, not weeks later when a reviewer or an ASPICE assessor finds it.
The 6 IREB CPRE Quality Criteria
Every requirement is scored against all six criteria defined by IREB's Certified Professional for Requirements Engineering (CPRE) framework — not a proprietary scoring system invented for this product, but the industry-standard definition of what makes a requirement good.
Does the requirement contain everything needed to understand and implement it, with no missing conditions or edge cases left implicit?
Can the requirement only be interpreted one way? Words like "fast," "user-friendly," or "appropriate" fail this test — they mean something different to everyone who reads them.
Is there a concrete, testable way to prove the requirement was met? A requirement you can't write a test case for isn't really a requirement yet.
Does the requirement contradict any other requirement in the same set — conflicting timing constraints, incompatible states, or duplicated obligations phrased differently?
Can this actually be built with realistic time, budget, and technical constraints — or does it quietly assume something that isn't achievable?
Does this requirement trace back to an actual stakeholder need, or is it scope creep that crept into the document without anyone deciding it should be there?
EARS Pattern Enforcement
Beyond scoring, Analyser automatically detects which EARS (Easy Approach to Requirements Syntax) pattern a requirement should follow — Ubiquitous, Event-Driven, State-Driven, Unwanted Behaviour, Optional Feature, or Complex — and rewrites it into that pattern where it doesn't already conform. This is the same rewrite logic that powers ReqM's and ReqCompass's requirement generation, available standalone for any single requirement you paste in.
What You Get
- 6-criteria IREB CPRE scoring on every requirement, in under 3 seconds
- EARS pattern detection and rewrite — not just a score, a corrected version
- Batch analysis — up to 50 requirements at once on Pro
- Safety, security & compliance risk flags, automatically surfaced
- CSV & Word export, with full analysis history on Pro
Pricing
Free
$0/mo
3 analyses per day, 6-criteria IREB scoring, EARS rewrite. No login, no credit card, no time limit.
Pro
$19/mo
Unlimited analyses, batch mode (50 at once), full history, CSV & Word export.
Frequently Asked
Try it right now
Paste a requirement you already have. See what it actually scores.
Open Requirement Analyser → Explore ReqCompass → Explore ReqM v3 →