|
Functionality
- Are functional requirements that affect multiple Use Cases identified?
For example, all Use Cases may be subject to access control, audit trail,
general responses to abnormal situations (overflow, communication facilities,
error handling and recovery ) and so on.
- For each of these requirements, are they behavioral and better captured
in a common Use Case?
- For each of these functions, is it clear how input
and shared data generate output and shared data?
|
Usability
- Are critical tasks and critical usability factors identified for each Supporting
Requirement?
- Are the requirements specified in a way that
is verifiable, including metrics and target values?
-
Do they accommodate novice to expert users?
|
Reliability
-
Have reliability requirements been specified as measurable requirements or prioritized design goals?
-
Is error checking and recovery required?
-
Are undesired events considered and their required responses specified?
- Are initial or special states considered (such as cold starts or abnormal
termination)?
|
Performance
-
Have the resource and performance margin requirements been stated (speed, response time, recovery time of various
software functions)?
|
Supportability
-
Are there any requirements that will enhance the supportability or maintainability of the system being built?
|
Constraints
-
Are there any required standards in effect, implementation language, policies for database integrity, resource
limits, operating environment(s), etc.?
-
Has the use of inherited design or code or pre-selected tools been specified?
|
External Interfaces
-
Is it clear how the software interacts with people, the system's hardware, other hardware, and other software?
-
Are all data elements crossing application boundaries identified?
|
Business Rules
-
Are the rules relevant to the use cases identified (data validation rules, formulas, flow decisions)?
|
Standards and Regulatory Compliance
-
Have all requirements derived from existing standard and regulations been specified?
|
|
