Master

Suggested Checklist Items for Requirements Specification Reviews
Organization and Completeness ο ο ο ο ο ο ο ο Are all internal cross-references to other requirements correct? Are all requirementswritten at a consistent and appropriate level of detail? Do the requirements provide an adequate basis for design? Is the implementation priority of each requirement included? Are all externalhardware, software, and communication interfaces defined? Have algorithms intrinsic to the functional requirements been defined? Does the specification include all of the known customer or system needs? Isthe expected behavior documented for all anticipated error conditions?

Correctness ο ο ο ο ο ο ο ο Do any requirements conflict with or duplicate other requirements? Is each requirement written inclear, concise, unambiguous language? Is each requirement verifiable by testing, demonstration, review, or analysis? Is each requirement in scope for the project? Is each requirement free from contentand grammatical errors? Is any necessary information missing from a requirement? If so, is it identified as TBD? Can all of the requirements be implemented within known constraints? Are any specifiederror messages unique and meaningful?

Quality Attributes ο Are all performance objectives properly specified? ο Are all security and safety considerations properly specified? ο Are other pertinentquality attribute goals explicitly documented and quantified, with the acceptable tradeoffs specified? Traceability ο Is each requirement uniquely and correctly identified? ο Is each softwarefunctional requirement traceable to a higher-level requirement (e.g., system requirement, use case)? Special Issues ο Are all requirements actually requirements, not design or implementation solutions? ο Areall time-critical functions identified, and timing criteria specified for them? ο Have internationalization issues been adequately addressed?

Copyright © 2001 by Karl E. Wiegers. Permission is...