Page History

{scrollbar:icons=false}

h1. {page-info:title}

h2. Pre Interview:

|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 12/09/2009 |
| {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number>_ \\
e.g. Init1dbw1 \\
(eventually&nbsp;linked to Use Cases) | Init1bes5 |
| *Originator/Customer's Name*: | Ashwin Mathur&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
| *Originator/Customer's Company*: | NCI |
| *Stakeholder Community*: \\
Enter appropriate category of stakeholder from Primary Stakeholders:&nbsp;&nbsp;
* 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:* | Business Goal: To ease the use of tools by centralizing access \\
Actor: Information Specialist. \\
All the Knowledge/Model browser tools could be combined into a portal or a portal-type format. Information Specialist&nbsp;will interact with one portal&nbsp;during modeling. This could promote reuse by easing use of tools. \\
Portal&nbsp;&nbsp;users can have different privileges&nbsp;based on the groups they belong to. e.g. Only the curators could get access to tools/functionalities that can create/modify CDEs (like the curation tool)&nbsp;or&nbsp;load models&nbsp;(model Loader). |
| *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 Template (text) in Round 2 with other Metadata Repository UI related functional requirements submitted. \\
This is a non-functional requirement essentially asks for harmonizing/combining the wide variety of browsers/editors that will be developed. |
\\
{scrollbar:icons=false}