Page History
...
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 | 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 | A common standard model is highly desirable, though it is necessary for different Information Modelers to extend it. |
Use Case - Descriptive Name
...
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
...
Brief Description
...
...
Actor(s) for this particular use case
...
...
Pre-condition
The state of the system before the user interacts with it
...
...
Post condition
The state of the system after the user interacts with it
...
...
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.
...
Alternate Flow
Things which would prevent the normal flow of the use case
...
...
Priority
The priority of implementing the use case: High, Medium or Low
...
...
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.
...
...
Fit criterion/Acceptance Criterion
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?
...