Requirement Statement:
Note to Business Analysts: If you work on a use case for this requirement, please put yourself on watch of this page, so that you will be automatically notified of any updates to this requirement.
Item |
Description |
Information/Response |
---|---|---|
Date: |
(MM/DD/YYYY) |
|
Requirement # |
a unique identifier |
|
Summary/Formal Requirement Statement, by Reviewer: |
Be sure to include these 3 elements in your narrative summary: as unambiguously as possible, describe (1) who (List of Actors) is interacting with the system, what the (2) business goal is and (3) how the system might support the actor's ability to achieve their goal. |
|
Revised Summary/Formal Requirement Statement, by Reviewer: |
In case a second analyst makes a major revision to the Requirement Statement (above), enter it here along with second analysts full name and date. |
|
Analysts Name (linked to their Email address): |
|
|
Originator/Customer's Name: |
Originator of the requirement, if submitter is different from originator |
|
Originator/Customer's Company: |
Company Name |
|
Stakeholder Community: |
Enter appropriate category of stakeholder from Primary Stakeholders:
|
|
Requirement Type (required) |
Analyst's assessment of the most appropriate category/type of requirement:
|
|
Link to use case (required) |
Record link to use case(s) |
|
Conflicts / Dependencies(required) |
Are there any conflicts with other requirements / use cases? Yes OR No - If yes, what and why? |
|