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
The state of the system before the user interacts with it

A service exists that needs to be annotated.

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

The service is annotated sufficiently to be discovered and integrated into an analytical pipeline.

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. The Information Modeler defines the metadata (inputs, outputs, service functionality, etc.) for the service.
2. The service is deployed and accessible to its users
3. The metadata is published in a way that can be queried upon and consumed by users of the service

Alternate Flow
Things which would prevent the normal flow of the use case

None.

Priority
The priority of implementing the use case: High, Medium or Low

High.

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.

• Init1dbw6 - Support caB2B to integrate services on caGrid
• Support caB2B Services to integrate data on grid

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

Sufficient metadata needs to be defined so that the service can be discovered and linked into a workflow.

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

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.

• Init1dbw6 - Support caB2B to integrate services on caGrid
• Support caB2B Services to integrate data on grid

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...

Use Case Number

Init1dbw6.pm8.3

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

• Init1dbw6 - Support caB2B to integrate services on caGrid
• Support caB2B Services to integrate data on grid

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...

Use Case Number

Init1dbw6.pm8.4

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.

• Init1dbw6 - Support caB2B to integrate services on caGrid
• Support caB2B Services to integrate data on grid

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...