NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Scrollbar
iconsfalse

...

Page info
title
title

Anchor
ContentsofthisPage
ContentsofthisPage
Panel
titleContents of this Page
Table of Contents
minLevel2

...

Use Case Number

Init6pm23.4

Brief Description

The ultimate result of the scientific use case is to design a classifier that predicts outcome.  It will be necessary to describe the classifier, as well as have that description link back to the data that is used to generate it.  In other words, the provenance of the data must be captured.

Actor(s) for this particular use case

Information Modeler

Pre-condition
The state of the system before the user interacts with it

Information models exist and are registered for analytical input data, output data, analytical algorithm, and research methodology.

Post condition
The state of the system after the user interacts with it

The inputs, analytical service, and outputs are linked through standard provenance data.

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

  1. The Information Modeler imports the standard provenance semantic metadata model into his UML model.
  2. The Information Modeler extends the provenance semantic metadata as needed
  3. The Information Modeler associates all data that needs tracking to the provenance metadata
  4. The Information Modeler registers his model, including input parameters and associated extended provenance semantic metadata
  5. The Software Engineer implements the system, which links the analytical data via provenance data.

Alternate Flow
Things which would prevent the normal flow of the use case

A Researcher uses provenance to backtrack an analytical flow.

Priority
The priority of implementing the use case: High, Medium or Low

High

Associated Links
The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.

Init6pm23

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

A common standard model is highly desirable, though it is necessary for different Information Modelers to extend it.

...


Scrollbar
iconsfalse