Date: | 
(MM/DD/YYYY)

—

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

—

Originator/Customer's Name:

Summary of requirement initial analysis, by Reviewer:

(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 how
(3) what the system might do to support the actor's ability to achieve their goal.

—

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.

---

Priority: (choose must, should)

---

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

—

Recommended Next Step

Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Prototype, Waiting Room

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

• 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 Data and metadata managers
• Clinicians
• Patients
• Medical research study participants
• Broader Study participantsBroader Stakeholders:
  • caBIG® Community WS, NIH projects
  and
  • , related commercial COTS vendors, Project teams (i.e. caEHR
  , SDO's (
  • , NHIN), Standards Development Organizations (i.e. HL7, CDISC)
  ;
  • , International Collaborators (i.e.
  g
  • NCRI, cancerGrid, China), Government and regulatory bodies (i.e. FDA, CDC, ONC)
  
  
  • (
  link to view
  • see SemConOps Stakeholders description
  _
  • )
  ._

—

Requirement Type (required)
Analyst's assessement assessment of the most the most appropriate category/type of requirement (no need to ask interviewee):

• 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
  
• Select most appropriate initiative: (click for descriptions) 
• Initiative 1 - Distributed, federated metadata repositories and model repositories and operations
  • 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

ConOp Initiative(s)
Requirements Analyst/Business Analyst

• • 
    
  Initiative 2

-

-

-

High Level Use Case Summary)
Requirements Analyst/Business Analyst

Please write a short descriptive narrative use case; the steps or activities in this use case are usually the things the user wants to accomplish with the system (user/actor's goals).  

Link to use case Use Case Linkage (required)
Business Analyst
Which Record link to use case(s) is this requirement linked to?  (should follow Use Case numbering scheme <SemCon Ops Initiative>.<analysts initials><requirement number>.<use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc. Use case Number(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?

Next Step (required)
(Requirement Analyst / Business Analyst)

After reviewing the results of the interview, the forum, and all other materials related to this requirement, the analyst should recommend the next step, then attach the Tiny Link (on the Info tab) for this page to the Master List table.

—