NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Scrollbar
iconsfalse

Page info
title
title

Instructions

...

Pre Interview:

Item

Information/Response

Date

01/07/2010

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

Init1SD6

Originator/Customer's Name:

Brian Davis/Forum post                                                                                   

Originator/Customer's Company:

3rd Millenium

Summary of requirement pre-interview, by Reviewer:

The Primary actor is a cancer researcher.
The business goal is to move a step closer to realization of semantic web.
The associations between various UML classes need to be as unambiguous as possible this would make traversing classes a more informed affair. The best way to achieve this would be to enable associations to be annotated with concept codes.

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

Post Interview - ongoing throughout development of use cases:

...

Item

...

Description

...

Information/Response

...

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


Scrollbar
iconsfalse

...

Requirement Type (required)

...

Analyst's assessement of the most appropriate category/type of requirement (no need to ask interviewee):

  • Functional: Fundamental or essential to the product - describes what the product has to do or what processing is needed
  • Nonfunctional: properties the functions must have such as performance, usability, training or documentation
    • Project constraint: schedule or budget constraints
    • Design constraint: impose restrictions on how the product must be designed, such as conformant to ISO 11179, utilizes 21090 or is able to work on a particular type of device
    • Project driver: business-related forces such as descriptions of stakeholders or purpose of the product/project
    • Project issue: conditions that will contribute to the success or failure of the project

...

                                                

...

ConOp Initiative(s)
Requirements Analyst/Business Analyst

...

...

 

...

High Level Use Case Summary)
Requirements Analyst/Business Analyst

...

Please write a short descriptive narrative use case. 

...

 

...

Use Case Linkage (required)
Business Analyst

...

Which use case(s) is this requirement linked to?  (should follow Use Case numbering scheme <SemCon Ops Initiative>.<analysts initials><requirement number>.<use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

...

Use case Number(s):

...

Conflicts / Dependencies(required)
Requirements Analyst/ Business Analyst

...

Are there any conflicts with other requirements / use cases? 

...

Yes OR No - If yes, what and why?

...

Next Step (required)
(Requirement Analyst / Business Analyst)

...

After reviewing the results of the interview, the forum, and all other materials related to this requirement, the analyst should recommend the next step, then attach the Tiny Link (on the Info tab) for this page to the Master List table.

...