NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 38

changes.mady.by.user Unknown User (wileyal)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (wileyal)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Scrollbar
iconsfalse

...

Page info
title
title

Anchor
ContentsofthisPage
ContentsofthisPage
Panel
titleContents of this Page
Table of Contents
minLevel2

...

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

A service has been developed that supports queries.

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

The service is configured to handle complex queries appropriately.

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 Software Engineer configures the handling of different aspects of query complexity, including 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
  2. The Software Engineer deploys the service

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

The Software Engineer changes the configuration of a deployed service.

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

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?

Minimally, the number of joins and amount of data returned should be supported.

...


Scrollbar
iconsfalse