Page 127 -

Document modifiability
Is the document structured so that any changes can be made easily, completely, and
consistently?
Document feasibility
Can every element of the SRS be implemented with the available resources and tools?
The following checklist items apply to the use cases.

Use case clarity
Does each use case have a clear flow of events?
Is every action that the system takes performed in response to an action by the user or
to a specific event?
Has unnecessary duplication been removed using generalization and/or references?
Is each use case uniquely identified with a name and a number?
Use case completeness
Are all of the steps in each use case necessary?
Are there any steps that are missing?
Are all alternative paths and exceptions accounted for?
Use case level of detail
Does any use case contain details (such as specific calculations, constraints, or other
internals that would not directly be observed by the user) that should really be part of
the functional requirements instead?
Does any use case unintentionally constrain the design?

Use case testability
Is each use case testable?

The following checklist items apply to the functional and nonfunctional requirements.
Requirement clarity
Is each requirement clear, unambiguous, and readable?

Is each requirement uniquely identified with a name and a number?
Requirement completeness
Is each requirement complete?
Are there requirements that are missing?
Requirement level of detail
Do any requirements unintentionally constrain the design?
Requirement consistency
Are the requirements consistent?
Does any requirement contradict another requirement?

Are all data structures, calculations, and functions named and used consistently?

SOFTWARE REQUIREMENTS 119