Page History
...
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 | 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 | Research methodology metadata is modeled and associated to input parameter metadata. |
Steps to take |
|
Alternate Flow | Researcher enters the research methodology data when the input parameter data is entered into the system. |
Priority | Medium |
Associated Links | |
Fit criterion/Acceptance Criterion | A common standard model is highly desirable, though it is necessary for different Information Modelers to extend it. |
...
Init6pm23.4 - Analytical Provenance Tracking
Use Case Number | 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 | Information models exist and are registered for analytical input data, output data, analytical algorithm, and research methodology. | ||
Post condition | The inputs, analytical service, and outputs are linked through standard provenance data. | ||
Steps to take |
| ||
Alternate Flow | A Researcher uses provenance to backtrack an analytical flow. | ||
Priority | High | ||
Associated Links | |||
Fit criterion/Acceptance Criterion | 1. |
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|