Brief Outline |
The following attributes can be stored.
Attributes
|
Description
|
Possible Values
|
Requirement name
|
Short name of the requirement
|
|
Requirement description
|
Requirement statements
|
|
Requirement type
|
Type of requirement
|
Functional requirement, Usability requirement
|
Priority
|
Priority of requirement
|
Low, Medium, High
|
Status
|
Status of requirement
|
Proposed, Approved, Incorporated, Validated
|
Difficulty
|
Difficulty of requirement
|
Low, Medium, High
|
Stability
|
Stability of requirement
|
Low, Medium, High
|
Origin
|
Source of requirement
|
Customers, Executive Committee
|
Assigned To
|
Responsible Person
|
|
Obsolete
|
Relevance of requirement to the project
|
True, False
|
If the requirement is newly added or editted, the status will be "proposed". After all of the project participants
commit to the requirement, the status will be changed to "approved". "Incorporated" status is used when the requirement
is incorporated into project plans and "Validated" status is assigned when the corresponding function
or feature is implemented and validated as completed.
Over time, a particular requirement might become irrelevant or out of scope. Rather than deleting an irrelevant
requirement, mark it as obsolete.
|