{scrollbar:icons=false}

Pre Interview:

Item

Information/Response

Date: 

12/14/2009

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

Init1bes8

Originator/Customer's Name:

Hannes Niedner                                                                                    

Originator/Customer's Company:

5AM Solutions (previously UCSD Moores Cancer Center)

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:

Business Goal: Removing current data element related constraints from information models
Actor: Information Specialist (Modeler) 
Currently CDEs are bound to an object class which hinders reuse for developers. Although this supports domain information modeling, where classes actually represent real life entities, it does not support non-domain information modeling (e.g. summary classes, report classes that combine many attributes from different domain classes). Supporting such non-domain modeling practices and removing object class/DE dependency will be needed.

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. 
Although requirement in clear,an interview may reveal alternative ways of handling the issue.  For instance the interviewee can suggest a mechanism that will be support "trace"/map any model entity (e.g. summary/report classes) back to a "domain analysis model"(or other) entities during registration. 


{scrollbar:icons=false}