A Brain Tumor in silico use case consists of determining genetic, gene expression and outcome correlates of high resolution nuclear morphometry in the diffuse gliomas and their relation to MR features using Rembardt and TCGA datasets. This involves integrative analysis involving Pathology, Radiology and molecular data. The following semantic infrastructure use cases fall out of these requirements:
Init6pm23.1 - Agile Metadata Management
Use Case Number |
Init6pm23.1 |
Brief Description |
Specific scientific data elements will be shared amongst collaborators, requiring the need for a way to semantically describe the data. However, through the course of the study, new data elements will be added and some data element may change. Therefore, there is a need for an agile modeling approach that does not require significant effort to modify the information model and register the semantic metadata. |
Actor(s) for this particular use case |
Information Modeler |
Pre-condition |
An information model is represented in UML, registered in the metadata repository, and in active use. |
Post condition |
The information model is updated and able to be used in production. |
Steps to take |
|
Alternate Flow |
None. |
Priority |
High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
The modeling must be able to be performed and updated in a light-weight, Agile environment. Minimally, updates may be made monthly on an iterative basis. They should take no longer than days to define and propagate to the metadata repository. |
Init6pm23.2 - Modeling and Sharing Analytical Algorithms
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 |
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 |
|
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 |
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 |
|