Date:
(MM/DD/YYYY) 

04/23/2010

Requirement # 
a unique identifier
e.g <SemConOps Initiative>.<analysts initials><requirement number> 
Init1dbw1
(eventually linked to Use Cases) 

InitotherSD75

Summary/Formal Requirement Statement:
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) what the system might do to support the actor's ability to achieve their goal.

Actor: Cancer researcher
Business Goal: To achieve integration of clinical, pathological, genomic and proteomic and imaging data to better predict patient outcome and standardize the treatment modalities

Revised Summary/Formal Requirement Statement:
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. 

There is strong consensus that phenotypic imaging data will add meaningful discovery in the research setting and to diagnosis, staging, and prognosis in the clinical setting when cross correlated with molecular profiling and pathology data. 

Priority: (choose must, should)

Should

Analysts Name (linked to their Email address):

Shantanu Deshpande

Originator/Customer's Name:
Originator of the requirement, if submitter is different from originator 

Tony Pan

Originator/Customer's Company:
Company Name 

---

Stakeholder Community:
Enter appropriate category of primary, direct stakeholder(s):  

• Software and Application designers and architects
• Software and Application engineers and developers
• Scientific and medical researchers
• Medical research protocol designers
• Data and metadata managers
• Clinicians
• Patients
• Study participantsBroader Stakeholders:
  • caBIG® Community WS, NIH projects, related commercial COTS vendors, Project teams (i.e. caEHR, NHIN), Standards Development Organizations (i.e. HL7, CDISC), International Collaborators (i.e. NCRI, cancerGrid, China), Government and regulatory bodies (i.e. FDA, CDC, ONC) (see SemConOps Stakeholders description)

Scientific and medical researchers

Requirement Type (required)
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
    

---

Link to use case (required)
Business Analyst
Record link to use case(s) 

---

Conflicts / Dependencies(required)
Requirements Analyst/ Business Analyst
Are there any conflicts with other requirements / use cases?  Yes OR No - If yes, what and why? 

---