Get status of query process
Use Case Number |
INIT1SD2.pm7.1 |
Brief Description |
When a long-running query is submitted to a number of different federated services, it is desirable to be able to provide users with a status update on the progress of the query, including which services have completed, how much data has been returned, and (if possible) how much work is left. |
Actor(s) for this particular use case |
Cancer Researcher |
Pre-condition |
A number of services are available upon which a federated query can be performed. |
Post condition |
The user is updated with the status of the query. |
Steps to take |
|
Alternate Flow |
None. |
Priority |
Medium. |
Associated Links |
|
Fit criterion/Acceptance Criterion |
Minimally, the user should be informed on which services have completed execution of the query, which are still working on the query, and how much time has passed for each service. |
ry
Use Case Number |
INIT1SD2.pm7.2 |
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 |
|
Cancel portions of a query
Use Case Number |
INIT1SD2.pm7.3 |
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. |
Interrogate a service for additional data information
Use Case Number |
INIT1SD2.pm7.4 |
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 |
|
Customize complexity of supported queries
Use Case Number |
INIT1SD2.pm7.5 |
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 |
|