Page History
Wiki Markup |
---|
{scrollbar:icons=false}
h1. { |
Page info |
---|
...
|
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: |
...
_ |
...
Jean |
...
Zhao |
...
x |
...
246 |
...
301-251-1355 |
...
| ||
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? | --- |
Wiki Markup |
---|
\_ \\ {color:#000000}mapping requirements ({color}{color:#000000}CTCAE 3 => 4 mappings):{color} \\ {color:#000000}Shanda Finnigan, RN, BSN, CCRC{color} \\ {color:#000000}Operations and Informatics Branch{color} \\ {color:#000000}NCI, DCTD, CTEP{color} \\ {color:#000000}301-435-9105{color} |
| {color:#000000}{*}Requirement Type (required)*{color} | Analyst's assessment of the most appropriate category/type of requirement: \\
* *Functional:* Fundamental or essential to the product - describes what the product has to do or what processing is needed \\
* *Nonfunctional:* properties the functions must have such as performance, usability, training or documentation \\
** *Project constraint:* schedule or budget constraints \\
** \*Design constraint:*impose restrictions on how the product must be designed, such as conformant to ISO 11179, utilizes 21090 or is able to work on a particular type of device \\
** *Project driver:* business-related forces such as descriptions of stakeholders or purpose of the product/project \\
** *Project issue:* conditions that will contribute to the success or failure of the project | --\- |
| {color:#000000}{*}Conflicts / Dependencies(required)*{color} \\
_Requirements Analyst/ Business Analyst_ | {color:#000000}Are there any conflicts with other requirements / use cases? {color} \\
Yes OR No - If yes, what and why? \\ | \--\- \\ |
\\
{scrollbar:icons=false} |