Page History

Date: 

12/17/2009

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

Init1pm5

Originator/Customer's Name:

Ashwin Mathur : forum posting

Originator/Customer's Company:

Unknown

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

• Clinical and scientific research data and metadata managers
• Software and Application engineers and developers
  

Summary of requirement pre-interview, by Reviewer:

There needs to should be a way developed to cleanly do a rollback of remove any model that has been loaded. This will help the users easily back out any loads even at a later stage. We need to develop   This is important for developers that would be managing their own metadata (e.g. model loads), as well as for curators to rollback model loads.  If using the current technology stack, there will need to be a robust algorithm for this since not all data might be able to be rolled back.
Note: this is linked to the use case related to providing a sandbox for developers themselves to create metadata.to Init1pm5 - Data rollback functionality

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 Model or Waiting Room