NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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)

Init1pm11

Originator/Customer's Name:

Frank Hartel - forum posting

Originator/Customer's Company:

NCI

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 decription).

Software and Application designers and architects

Summary of requirement pre-interview, by Reviewer:

Domain analysis models play a central role in providing a common framework for implementation models. Within the life sciences domain a first pass domain analysis model called the LSDAM is being produced. Ultimately this model will need to be revised and refined so that it can play a role in the life sciences domain analogous to the role played by the BRIDG model in the clinical trial space. The architectural and semantics expectations regarding future development of this model will play a role in driving refinement, however the functional and structural requirements of the life sciences domain must drive the evolution of the model and the tactics that are defined for its use.  DAMs are authored by Information Modelers, overseen by Metadata Curators, and reused by Information Modelers and Software Engineers.

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

...