Scribd
Upload
80 views1 page

SRS Checklist

O Are all internal cross-references to other requirements correct? Are all external hardware, software, and communication interfaces defined? Are all expected behavior documented for all anticipated error conditions? Are all time-critical functions identified, and timing criteria specified for them?

Uploaded by

Osce Rovi
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
80 views1 page

SRS Checklist

O Are all internal cross-references to other requirements correct? Are all external hardware, software, and communication interfaces defined? Are all expected behavior documented for all anticipated error conditions? Are all time-critical functions identified, and timing criteria specified for them?

Uploaded by

Osce Rovi
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Suggested Checklist Items for Requirements Specification Reviews

Organization and Completeness

ο Are all internal cross-references to other requirements correct?


ο Are all requirements written 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 external hardware, 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?
ο Is the expected behavior documented for all anticipated error conditions?
Correctness

ο Do any requirements conflict with or duplicate other requirements?


ο Is each requirement written in clear, 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 content and 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 specified error messages unique and meaningful?
Quality Attributes

ο Are all performance objectives properly specified?


ο Are all security and safety considerations properly specified?
ο Are other pertinent quality attribute goals explicitly documented and quantified, with the
acceptable tradeoffs specified?
Traceability

ο Is each requirement uniquely and correctly identified?


ο Is each software functional 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?


ο Are all time-critical functions identified, and timing criteria specified for them?
ο Have internationalization issues been adequately addressed?

Copyright © 2001 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

You might also like