NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

  • Created by Unknown User (suzekb), last modified by Unknown User (wileyal) on Jan 23, 2012

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

Pre Interview:

Item

Information/Response

Date: 

12/09/2009

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

Init1bes5

Originator/Customer's Name:

Ashwin Mathur                                                                      

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


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 will interact with one portal during modeling. This could promote reuse by easing use of tools.
Portal  users can have different privileges 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) or load models (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.


  • No labels