Use Case Number

Init6pm23.3

Brief Description

Metadata describing analytical results should link to the methodology used to generate the input data, such as the way that the biological specimens are analyzed and treated.  In some cases, there can be clear overlap between the research methodology and the study design, which should be linked if possible.

Actor(s) for this particular use case

Information Modeler, Software Engineer

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

Input data to analytical services has been generated using a particular set of steps, which is termed the methodology.  A UML model exists for modeling the input parameter data.

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

Research methodology metadata is modeled and associated to input parameter metadata.

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 research methodology semantic metadata model into his UML model.
2. The Information Modeler extends the research methodology semantic metadata as needed
3. The Information Modeler associates input parameter data elements to the research methodology semantic metadata
4. The Information Modeler associates study design data elements to the research methodology semantic metadata
5. The Information Modeler registers his model, including input parameters and associated extended research methodology semantic metadata
6. The Software Engineer generates a grid service using the registered metadata
7. The Software Engineer implements the system, which links the analytical inputs to the research methodology data.

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

Researcher enters the research methodology data when the input parameter data is entered into the system.

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

Medium

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.

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

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.

Brief Description

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

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?

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