{scrollbar:icons=false}

h1. {page-info:title}

h2. Pre Interview:

|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 04/05/2009 |
| {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number>_ \\
e.g. Init1dbw1 \\
(eventually&nbsp;linked to Use Cases) | Init3bes20 |
| *Originator/Customer's Name*: | Sal Mungal, Guide to Mentors |
| *Originator/Customer's Company*: | Duke University |
| *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_|Semantic Infrastructure Concept of Operations Stakeholders]__)._ | Software and Application designers and architects \\
Software and Application engineers and developers |
| *Summary of requirement pre-interview, by Reviewer:* | The cyclic references in models is not a good practice and is&nbsp;preventing uploading of the XSD representations of the models to caGrid XSD repository (GME). More information is available from [attached presentation.|^Circular_References_20100401.ppt] A&nbsp;tool&nbsp;or model validation service that enforces the model policies/best practices (e.g. entity naming rules, prevention of cyclic references, association directionalities/naming etc.) for NCI-CBITT locale. This service&nbsp;can be utilized by model/knowledge repository loading tools, a tool like SIW and even code generators. |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Use case development. |
\\
{scrollbar:icons=false}