Use Case Statement

By Manuel Dennis III

Name

Request List Query Section

Description

How does the Query Section function

Dependencies

User must be authorized to query requests

Scope

Change the scope of a Request List Result Grid

Primary Actors

· Assigner, Approver, Worker

Secondary Actors

· Administrator, Requester

Pre Conditions

· All text fields and drop down lists on the Request List page should be cleared or set to a default value

Success End Conditions

· The Request List Result Grid should be populated with a list of Requests that meets the Query criteria

· If no results match, a message to that effect should be displayed to the user

Failure End Conditions

· The Request List displays incorrect results or no results

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

 

UseCase

#

Action / Stimulus

Reaction

1

User enters some keywords

The keywords are parsed using a simple split function to create a list to construct a where clause that can be used to interrogate the Subject and all comment fields for requests. The requests should be scoped to the users role prior to the Query criteria.

2

User selects a checkbox indicating what type of keyword search is to be performed.

If the subject checkbox is selected, then the search will include the subject lines of each request. If the comments checkbox is selected, then all of the requests comments will also be searched.

3

User selects from the list of drop down lists which items they would additionally like to place into a query

The system should construct targeted queries that check the ids for the specific tables that are related to the request. The drop down lists should include:
Requester, Department, Division, Category, Machine, Status, Location, Project, Action, Priority, and Client. A drop down for Worker may be relevant too.

4

User enters a date range by entering dates into two drop down lists that should check the request change dates

The system should construct a date range clause that can be used to narrow the returned requests based on the status change date.

5

User clicks Requester link

This will link the user to the PersonInfo.aspx page for information about the Requester.

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

A1

    

A2

    

A3

    

 

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

B1

    

B2

    

B3

    

 

Alternative / Additional Scenario: Cancel

#

Action / Stimulus

Reaction

C1

    
     
     

Notes:

 

 

 

 

Issues: