|
Requirements Inspection Checklist |
|
|
This checklist can help
business and technical users to verify system and software requirements. |
|
|
For
individual requirements |
|
|
Correct |
|
|
¨ |
Does this requirement
agree with the stated needs? |
|
¨ |
Does this requirement
agree with the intended environment or intended scenarios? |
|
Necessary |
|
|
¨ |
Would the product or
system function improperly without this requirement? |
|
Clear |
|
|
¨ |
Is there only one way to
interpret this requirement? |
|
Attainable |
|
|
¨ |
Can this requirement be
implemented given current environment, technology, cost, schedule, and
resources? |
|
Verifiable |
|
|
¨ |
Is this requirement
measurable? |
|
¨ |
Is it clear how the final
product can be tested to prove that this requirement is met? |
|
Traceable |
|
|
¨ |
Is this requirement
uniquely identified? |
|
¨ |
Is this requirement traced
correctly to needs? |
|
For the
requirements set |
|
|
Complete |
|
|
¨ |
Are all known needs
addressed by the requirements set? |
|
¨ |
Are all known assumptions
documented? |
|
¨ |
Are all known exceptions
addressed? |
|
¨ |
Are all known scenarios for
use of the product or system addressed? |
|
Consistent |
|
|
¨ |
Do all requirements
coexist without conflict? |
|
¨ |
Are all requirements
unique (no duplicates)? |
|
¨ |
Are all terms used
consistently? |
|
Modifiable |
|
|
¨ |
Are all requirements
expressed individually (no compound requirements)? |
|
¨ |
Are all requirements
categorized? |
|
¨ |
Can addition or deletion
of a requirement be done without disrupting the structure of the requirements
set or causing loss of traceability? |