Page History
Scrollbar | ||
---|---|---|
|
...
Page info | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
|
...
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. |
...
Scrollbar | ||
---|---|---|
|