NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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 that identifies the inputs and output.

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.

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

Discovery of analytical steps

Use Case Number

Init1dbw6.pm8.2

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.

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

Storage and access of intermediate data

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

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

Workflow sharing

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.

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

  • No labels