Checklist: Qualities of Good Requirements
This checklist provides guidance on assessing the quality of requirements.
Relationships
Check Items
Is the requirement correct?
  • Does the requirement specify a true need, desire, or obligation?
  • Have you identified the root cause that necessitates the requirement?
Is the requirement complete?
  • Is the requirement stated as a complete sentence?
  • Is the requirement stated entirely in one place and in a manner that does not force the reader to look at additional information to understand the requirement?
Is the requirement clear?
  • Is the requirement unambiguous and not confusing?
  • Does everyone agree on the meaning of the requirement?
Is the requirement consistent?
  • Is the requirement in conflict with other requirements?
  • Is the terminology used consistent with other requirement and glossary terms?
Is the requirement verifiable?
  • Can you determine whether the system satisfies the requirement?
  • Is it possible to define a clear, unambiguous pass or fail criterion?
  • Is it possible to determine whether the requirement has been met through inspection, analysis, demonstration, or test?
Is the requirement traceable?

Is the requirement uniquely identified so that it can be referenced unambiguously?

Is the requirement feasible?
  • Can the requirement be satisfied within budget and on schedule?
  • Is the requirement technically feasible with current technology?
  • Is the requirement physically achievable?
Is the requirement design independent?
  • Are all requirements that impose constraints on the design, thereby limiting design options, justified?
  • Is the requirement stated in such a way that there is more than one way that it can be satisfied?
Is the requirement atomic?
  • Does the requirement statement define exactly one requirement?
  • Is the requirement statement free of conjunctions (and, or, but) that could indicate multiple requirements?