NIH | National Cancer Institute | NCI Wiki  

  • Created by Unknown User (mcconnellp), last modified by Unknown User (wileyal) on Jan 23, 2012

Pre Interview:

Item

Information/Response

Date: 

12/17/2009

Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number>
e.g. Init1dbw1
(eventually linked to Use Cases)

Init1pm10

Originator/Customer's Name:

Tejas Dave : forum posting

Originator/Customer's Company:

Unknown

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)
    (link to view SemConOps Stakeholders description).
  • Software and Application designers and architects
  • Software and Application engineers and developers

Summary of requirement pre-interview, by Reviewer:

The metadata/semantic tools in caBIG provide a rich set of functionality that may be useful to Information Technologists (especially Software Engineers) in a programmatic/service manner. The tools themselves would need to be refactored to expose the underlying functionality as services so that an application engineer could invoke the services to perform add, change or delete content in the metadata registry, or retrieve content to use the metadata in their user interface. In this scenario, the same business rules that are applied in the manual curation of content would need to be in the services. Examples also include new services to perform Value Domain matching, CDE and/or UML oriented searches that easily bring back associated components.

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

Followup Interview


  • No labels