Analysis / Development of Formal Requirement Statement:
Item |
Description |
Information/Response |
---|---|---|
Date: |
(MM/DD/YYYY) |
|
Requirement # |
a unique identifier |
--- |
Originator/Customer's Name: |
Originator of the requirement, if submitter is different from originator |
Larry Wright |
Originator/Customer's Company: |
Company Name |
--- |
Stakeholder Community: |
Enter appropriate category of stakeholder from Primary Stakeholders:
|
--- |
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. |
Terminologists need to develop new content in EVS using the LexEVS services. Additional contacts are: |
Requirement Type (required) |
Analyst's assessment of the most appropriate category/type of requirement:
|
--- |
Conflicts / Dependencies(required) |
Are there any conflicts with other requirements / use cases? |
--- |