Checklist: System-Wide Requirements (FURPS+) |  |
This check list is used to verify that the different types of system-wide requirements covered by FURPS+ have been considered.
Relationships
Related Elements | Developing System-Wide Requirements Specification
Check Items
Have global functional requirements been captured and validated?
Are functional requirements that affect multiple use cases identified? For example, all use cases may be subject to access control, audit trails, general responses to abnormal situations (overflow, communication facilities, error handling and recovery and so on). For each of these requirements, are they behavioral and could be 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?
Have usability requirements been captured and validated?
Have the efficiency and usability factors of user tasks been considered? Are the requirements specified in a way that is verifiable, including metrics and target values? Have novice as well as expert users been considered?
Have reliability requirements been captured and validated?
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)?
Have performance requirements been captured and validated?
Have the resource and performance margin requirements been stated (for example speed, response time, recovery time of various software functions)?
Have supportability requirements been captured and validated?
Are there any requirements that will enhance the supportability or maintainability of the system being built?
Have constraints been captured and validated?
Are there any required standards in effect, implementation language, policies for database integrity, resource limits, operating environments, and so forth? Has the use of inherited design or code or pre-selected tools been specified?
Have external interfaces been identified?
Is it clear how the software interacts with people, the system's hardware, other hardware, and other software? Have all critical data elements that cross system boundaries been identified for those scenarios that will be implemented next?
Have business rules been captured and validated?
Are the rules relevant to the use cases identified (data validation rules, formulas, flow decisions)?
Have applicable standards and regulatory compliance requirements been identified?
Have all requirements derived from existing standard and regulations been specified?
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright.