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, Software Engineer |
Pre-condition | An algorithm exists, it is coded, and its features are known. Outputs from the analytical routine are modeled and registered. |
Post condition | A semantically sound description of the algorithm is defined, able to be shared with others, and able to be associated with data that the algorithm created. |
Steps to take |
|
Alternate Flow | None. |
Priority | Medium |
Associated Links | |
Fit criterion/Acceptance Criterion | None. |
...
A common standard model is highly desirable, though it is necessary for different Information Modelers to extend it. |
Init6pm23.3 - Modeling Lab and Research Methodology
Use Case Number | n.n | 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. | Brief Description | |
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 | |||
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 |
|
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 |
|