RequiCheck checks every requirement with 18 context-sensitive rules, condenses the result into seven quality characteristics and shows the score per characteristic as a radar – strengths and gaps are immediately visible.
- Unambiguity
- Verifiability
- Measurability
- Completeness
- Atomicity
- Obligation
- Comprehensibility
From finding to solution
RequiCheck shows where things get stuck. If you want to fix the root causes within your team – clear writing rules, reviews, a robust requirements process – we support you: as a training provider recognised by IREB® or directly in your project.
Why requirements quality drives test effort
Unclear requirements are one of the most common causes of expensive defects: anything ambiguous is understood differently in development and testing – and only surfaces during acceptance, when fixing it costs a multiple. A requirement that cannot be verified unambiguously inevitably creates room for interpretation in the test case.
What RequiCheck checks – and what it does not
RequiCheck applies 18 context-sensitive rules and condenses the result into seven characteristics: unambiguity, verifiability, measurability, completeness, atomicity, obligation and comprehensibility. Each characteristic receives a score from 1 to 10, shown as a radar. The characteristics cover the linguistically and formally checkable subset of the quality characteristics in ISO/IEC/IEEE 29148 – unambiguity maps to unambiguous, verifiability and measurability to verifiable, completeness to complete, atomicity to singular.
Beyond the individual requirement, the tool also checks the requirement set: terminology consistency, duplicates, gaps in ID allocation and cross-references. Necessity, feasibility and technical correctness cannot be assessed automatically – those require project context and a team review.
Typical weaknesses and how to fix them
- Vague wording (“user-friendly”, “fast”, “if possible”) – replace with measurable values including number and unit.
- Several statements in one sentence – split them so each can be verified on its own.
- Passive voice without an actor (“it is checked”) – name who or which system acts.
- Missing boundary conditions – add validity ranges, error cases and volume figures.
The IREB® CPRE Foundation Level covers this systematically; our requirements management consulting shows how to embed testable requirements in a project. How good requirements turn into a solid test concept is explained in our knowledge section.