Requirements Review Checklist

From DIT Experimental Gaming Group

Purpose of this page
Each requirement should be checked for clarity, correctness, completeness, and relevance. This page acts as a checklist of questions to ask when reviewing requirements.

It might be useful to keep a printout of this page to hand while reviewing requirements.

Questions to ask about each requirement:

• Is each requirement written in clear, concise, unambiguous language?
• Is each requirement free from content and grammatical errors?
• Is any necessary information missing from a requirement? If so, is it identified for discussion?
• Have internationalisation issues been adequately addressed? (eg have different languages' money/number/date formats been considered)
• Is each requirement in scope for the project?
• Are all requirements actually requirements, not design or implementation solutions?
• Is each requirement verifiable by testing, demonstration, review, or analysis?
• Can all of the requirements be implemented within known constraints? (time/budget/technology)
• Do any requirements conflict with or duplicate other requirements?
• Are there any legal issues relating to each requirement?