Page History

Use Case Number

Init6pm23.2

Brief Description

Data elements are generated using specific algorithms.  There needs to be a way to model the features of the algorithm itself and tie it back to the original data.  One of the features of the algorithm could be the code of the algorithm itself.  It would be ideal if this type of model could be generalized for use in the caBIG analytical community.

Actor(s) for this particular use case

Information Modeler

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

An algorithm exists, it is coded, and its features are known.  Outputs from the analytical routine are modeled and registered.

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

A semantically sound description of the algorithm is defined and , able to be shared with others, and able to be associated with data that the algorithm created.

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 analytical routine semantic metadata model into his UML model.
2. The Information Modeler associates

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? 

1.
2...