Page History
...
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. |
...
Use Case Number | INIT1SD2.pm7.2 |
---|---|
Brief Description | After receiving a status update that a federated query has completed on some services, the user may want to fetch and view the results from the completed sub-queries. |
Actor(s) for this particular use case | Cancer Researcher |
Pre-condition | A federated query has been submitted to multiple services and a subset of them have completed. |
Post condition | The user receives intermediate data from the completed sub-queries. |
Steps to take |
|
Alternate Flow | None. |
Priority | Medium. |
Associated Links | |
Fit criterion/Acceptance Criterion | The Cancer Researcher can view intermediate results in order to determine whether to continue the processing of the federated query. |
...
Use Case Number | INIT1SD2.pm7.5 |
---|---|
Brief Description | Some queries can be intractable or impractical to complete. When the level of complexity of these types of queries is well understood, it is important that the Software Engineer is able to configure the query processor to handle them appropriately. This includes the amount of data that can be returned, the length of time that can be spent processing a query, and the number of joins that are allowed. |
Actor(s) for this particular use case | Software Engineer |
Pre-condition | A service has been developed that supports queries. |
Post condition | The service is configured to handle complex queries appropriately. |
Steps to take |
|
Alternate Flow | The Software Engineer changes the configuration of a deployed service. |
Priority | Low |
Associated Links | |
Fit criterion/Acceptance Criterion | Minimally, the number of joins and amount of data returned should be supported. |
...