Brief Outline |
The following attributes can be stored.
Attributes
|
Description
|
Possible Values
|
Name
|
Short name of the requirement
|
|
Description
|
Requirement statements
|
|
Requirement type
|
Type of requirement
|
-
Feature (a set of logically related functional requirements that provides a capability to the
user)
-
Non-Functional (the description of a property or characteristic that a software system must have,
other than an observable system behavior)
-
Supporting Document
-
Term
-
User Story Elaboration (a statement explaining the intent of a user; it can be elaborated through
conversations and confirmation, leveraging techniques such as sketching and storyboarding)
|
Default format
|
Default format for requirement artifact
|
Text, Collection, Sketch, Storyboard
|
Business Priority
|
Priority of requirement from business perspective
|
Must, Should, Could, Won't
|
Priority
|
Priority of requirement from development perspective
|
Low, Medium, High
|
Status*
|
Status of requirement
|
Draft, Under Review, Approved, Rejected, Deprecated
|
Product Owner
|
Responsible Person
|
|
Origin
|
Source of requirement
|
Customers, Marketing
|
* If the requirement is newly added or edited, mark the status as "draft". While project participants review the
requirement, it's status is "under review". After all of the project participants commit to the requirement, the change
the status to "approved". Mark those requirements that are not approved as "rejected". Over time, a particular
requirement might become irrelevant or out of scope - rather than deleting an irrelevant requirement, mark it as
"deprecated".
|