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)

Initpm3

Originator/Customer's Name:

Brian Davis : forum posting

Originator/Customer's Company:

3rd Millenium

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

Summary of requirement pre-interview, by Reviewer:

There is a distinct lack of and need for a metadata repository that can store information models in a way that they can easily be searched and visualized in a UML-centric manner.  Furthermore, this repository/interface should allow users to easily traverse between UML, ontologies, metadata, XML Schemas, and APIs, as well as begin searching and visualizing from each of these items.  The baseline use case is that users (Information Technologists) come to caBIG looking for ways to interoperate and/or build interoperable systems from different backgrounds/viewpoints.  This is especially true coming from the UML world (which is the lingua franca of software development), and there is no way to search and visualize information models in a UML visualized manner.

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

Follow-up interview


  • No labels