NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

  • Created by Unknown User (mahiousb), last modified on Apr 05, 2010

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

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

 

Information/Response

Date:
(MM/DD/YYYY) 


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


 


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:  

  • 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)


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? 


  • No labels