{scrollbar:icons=false}
h1. {page-info:title}
h2. Analysis / Development of Formal Requirement Statement:
|| Item || Description || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}:{color}\\ | {color:#000000}({color}MM/DD/YYYY) | \\ |
| {color:#000000}{*}Requirement # *{color} | {color:#000000}{*}a unique identifier{*}{color}\\
*e.g* _<SemConOps Initiative>.<analysts initials><requirement number>_ \\
Init1dbw1 \\
(eventually linked to Use Cases) | \--\- \\ |
| *Originator/Customer's Name*: | Originator of the requirement, if submitter is different from originator \\ | {color:#000000}Larry Wright{color} \\
\\ |
| *Originator/Customer's Company*: | Company Name \\ | \--\- \\ |
| *Stakeholder Community*: | Enter appropriate category of stakeholder from Primary Stakeholders:
* Software and Application designers and architects
* Software and Application engineers and developers
* Scientific and medical researchers
* Medical research protocol designers
* Clinical and scientific research data and metadata managers
* Clinicians
* Patients
* Medical research study participants
* Broader Stakeholders: caBIG® Community WS NIH projects and related commercial COTS vendors (caEHR, SDO's (HL7, CDISC); International Collaborators (e.g NCRI, cancerGrid, China), Government and regulatory bodies (FDA, CDC, ONC) \\
(view SemConOps Stakeholders description) \\ | \--\- \\ |
| *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*. \\ | {color:#000000}Terminologists need to develop new content in EVS using the LexEVS services. Additional contacts are:{color} \\ {color:#000000}Anne Tompkins, RN, MSN{color} \\ {color:#000000}Head, Protocol Information Office{color} \\ {color:#000000}Division of Cancer Prevention{color} \\ {color:#000000}National Cancer Institute{color} \\ {color:#000000}tompkinsa@mail.nih.gov{color} \\ {color:#000000}\_____________\_{color} \\ {color:#000000}for CTEP: Jean Zhao{color} \\ {color:#000000}Information Specialist{color} \\ {color:#000000}The EMMES Corporation{color} \\ {color:#000000}401 N. Washington Street, Suite 700{color} \\ {color:#000000}Rockville, MD 20850{color} \\ {color:#000000}E-mail:{color} {color:#000000}[mailto:jzhao@emmes.com]{color} \\ {color:#000000}Phone: 301-251-1161 x 246{color} \\ {color:#000000}Fax: 301-251-1355{color} \\
\______________\_ \\ {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} |