The review method
A clear standard for clearer requirements.
These rubrics are versioned snapshots of Kryterea’s requirements evaluation criteria, based on BABOK requirement quality and classification.
Each dimension is scored 0 (absent), 1 (weak), 2 (adequate), or 3 (strong). Where external context is missing, it is unassessed. Quoted evidence must match the submitted text.
Open the free requirements review →Requirement quality
Version 2026-10-18.1 · 9 dimensions
- Atomic
- Each requirement is self-contained and can be understood independently.
- Complete
- Each is complete enough to guide further work at the appropriate level of detail.
- Consistent
- Each aligns with the stakeholder needs and does not conflict with others.
- Concise
- Each contains no extraneous or unnecessary content.
- Feasible
- Each is reasonable and possible within the agreed risk, schedule, and budget.
- Unambiguous
- Each is stated so it is clear whether a solution meets it.
- Testable
- Each can be verified as fulfilled.
- Prioritised
- Each is ranked, grouped, or negotiated in terms of importance.
- Understandable
- Each is expressed in terms its stakeholders understand.
For a complete assessment: preliminary pass at 22 or higher, with no zero or weak dimension; pass with changes from 16 or higher with no zero. Any zero requires changes. An incomplete assessment is marked “Context needed”, even if its partial score is high.
This free AI review is a preliminary assessment, not independent validation or stakeholder approval. Review its findings with your team.
Functional requirements
Version 2026-10-18.1 · 9 dimensions
- Behaviour focus
- Each requirement states a behaviour the solution performs or information it manages, not a quality level or a design choice.
- Atomic
- Each requirement is self-contained, carries a single requirement, and can be understood independently of the others.
- Complete
- The functional scope is covered: inputs, outputs, flows, and rules for each capability are present, with no silent gaps.
- Unambiguous
- Each requirement admits one interpretation, so it is clear whether a solution does or does not meet it.
- Testable
- Each has acceptance criteria and can be verified as met or not met.
- Consistent
- Requirements align with the stakeholder needs and do not conflict with each other.
- Traceability
- Each traces up to a stakeholder requirement or objective and back to a source.
- Prioritised
- Requirements are ranked or grouped by value or importance, with stakeholder agreement.
- Feasible
- Each is achievable within the agreed risk, schedule, and budget, or is flagged for further investigation.
For a complete assessment: preliminary pass at 22 or higher, with no zero or weak dimension; pass with changes from 16 or higher with no zero. Any zero requires changes. An incomplete assessment is marked “Context needed”, even if its partial score is high.
This free AI review is a preliminary assessment, not independent validation or stakeholder approval. Review its findings with your team.
Non-functional requirements
Version 2026-10-18.1 · 9 dimensions
- Quality-attribute focus
- Each requirement defines how well the solution must perform, not what behaviour it carries out, and names the functional area or whole solution it qualifies.
- Categorised
- Each is assigned to a quality category such as performance, reliability, availability, security, usability, maintainability, or compliance.
- Measurable
- Each states a metric with a scale and unit, not a vague adjective such as fast or user-friendly.
- Target and threshold
- The required level is stated, with the acceptable minimum or maximum that constitutes pass or fail.
- Testable
- A method exists to verify the level objectively under defined conditions.
- Operating conditions
- The context and load under which the level must hold are stated.
- Traceability
- Each traces to a stakeholder need, a constraint, or a policy that requires it.
- Prioritised
- Requirements are ranked, and trade-offs between competing attributes are acknowledged.
- Feasible
- Each level is reasonable within the technology, risk, and budget available.
For a complete assessment: preliminary pass at 22 or higher, with no zero or weak dimension; pass with changes from 16 or higher with no zero. Any zero requires changes. An incomplete assessment is marked “Context needed”, even if its partial score is high.
This free AI review is a preliminary assessment, not independent validation or stakeholder approval. Review its findings with your team.
Business requirements
Version 2026-10-18.1 · 8 dimensions
- Enterprise perspective
- The requirement is stated from the enterprise view, not one team's.
- Problem, opportunity, or constraint
- It is framed clearly as a problem, an opportunity, or a constraint, not a solution.
- Grounded in current state
- It is defined from an understanding of the current state.
- Strategic importance
- Why it matters, and why now, is clear.
- Value
- It is tied to a value the enterprise cares about, such as revenue, cost, risk, or experience.
- Measurable
- The impact or need is quantified where possible.
- Solution-free
- No solution is presumed in the statement.
- Owned
- A sponsor or owner is accountable for it.
For a complete assessment: preliminary pass at 20 or higher, with no zero or weak dimension; pass with changes from 14 or higher with no zero. Any zero requires changes. An incomplete assessment is marked “Context needed”, even if its partial score is high.
This free AI review is a preliminary assessment, not independent validation or stakeholder approval. Review its findings with your team.