Characteristics of Requirements Checklist
Business requirements focus on what the product will do, and (to some extent) who will be using the
system. Requirements should specify the user, the end result, and the criteria that define a successful end
result. Gathering good business requirements up front saves time and money and is the key to the overall
quality of a product design.
Use the following checklist to help ensure that business requirements clearly describe what is to be
implemented and meet relevant quality standards before solution development begins.
The requirement is essential to meet business goals and objectives. If the
project can meet needs without it, the requirement is not necessary. The
requirement must be traceable to a goal stated in the project charter, vision
document, or other initiating document.
The requirement must be technically and operationally feasible and fall
within the funding and timing constraints of the project. Note, that even
though a requirement may be technically feasible, if it does not fall within
constraints, it is not attainable.
Testable requirements are designed to demonstrate the product satisfies
Measurable requirements. Tests may include functional, performance, regression and
and testable stress tests. If the requirement is impossible to test or measure, it should be
removed or revised.
The requirement can be allocated to an element of the project design where