Expose service workflow metadata
Use Case Number |
Init1dbw6.pm8.1 |
Brief Description |
It is commonplace in bioinformatics to string together a number of data and analytical operations in order to produce the desired output. In order for Cancer Researchers to discover which services can be piped together, it is necessary that the designers of the services expose the appropriate metadata. |
Actor(s) for this particular use case |
Information Modeler |
Pre-condition |
A service exists that needs to be annotated. |
Post condition |
The service is annotated sufficiently to be discovered and integrated into an analytical pipeline. |
Steps to take |
|
Alternate Flow |
None. |
Priority |
High. |
Associated Links |
|
Fit criterion/Acceptance Criterion |
Sufficient metadata needs to be defined so that the service can be discovered and linked into a workflow. |
Discovery of analytical steps
Use Case Number |
Init1dbw6.pm8.2 |
Brief Description |
Once metadata about a service is defined and exposed, it must be queriable by users of the service. They must, through consuming of the metadata alone, be able to determine which services can act as consumers of the data the service produces, as well as produces of the data the service consumes. Furthermore, the user must be able to determine that the service is appropriately placed within the workflow. |
Actor(s) for this particular use case |
Cancer Researcher |
Pre-condition |
Service-level metadata is exposed for a number of services that can be linked via a workflow. |
Post condition |
The Cancer Researcher knows which services can act as inputs to which other services. |
Steps to take |
|
Alternate Flow |
The query could begin with a dataset or data service, and the Cancer Researcher would be identifying all downstream data and analytical services. |
Priority |
High. |
Associated Links |
|
Fit criterion/Acceptance Criterion |
The user must be able to identify services based on input/output types, as well as find the appropriate translation services if needed. |
Storage and access of intermediate data
Use Case Number |
Init1dbw6.pm8.3 |
Brief Description |
When services are chained together into bioinformatic pipelines, it is often desirable to be able to store and then later access intermediate results of queries and analytics. These can be used to modify the pipeline as needed, or to share intermediate results with other investigators. |
Actor(s) for this particular use case |
Cancer Researcher |
Pre-condition |
A service that produces data has been identified and is accessible, as well as the mechanism by which intermediate data will be stored. |
Post condition |
The results of the service are available via the intermediate data service. |
Steps to take |
|
Alternate Flow |
None. |
Priority |
Low. |
Associated Links |
|
Fit criterion/Acceptance Criterion |
Access to the intermediate data must be as seamless as access to any other service, and the data should be secured based on rules that the Cancer Researcher identifies. |
Workflow sharing
Use Case Number |
Init1dbw6.pm8.4 |
Brief Description |
Once a user identifies a service workflow of interest, he should be able to share that workflow in a way that makes it easy to encode, share with colleagues, reuse/rerun, modify, and extend. |
Actor(s) for this particular use case |
Cancer Researcher |
Pre-condition |
A set of services of interest has been identified. |
Post condition |
The service workflow is stored and shared. |
Steps to take |
|
Alternate Flow |
The steps listed above can be performed in any order any number of times with the exception that the workflow must be encoded and saved first. |
Priority |
Low. |
Associated Links |
|
Fit criterion/Acceptance Criterion |
The workflow must be accessible in much the same way as any other service. |