Use Case Statement

By Manuel Dennis III

Name

Request List Page

Description

An attempt to define the Request List page

Dependencies

Request Query Section
Request List Result Section
Request List Quick Approval Section

Scope

Overview of the Request List Page features

Primary Actors

· Assigner, Approver, Worker, Administrator

Secondary Actors

· Requester

Pre Conditions

· The database must contain information for all drop down lists

· The requester must login with a valid user name and password

· The requester information must be in the database

Success End Conditions

· The Requester is presented with a list or requests that meet the Query criteria

Failure End Conditions

· The Requester is shown a list of requests that doesn’t meet requester privilege

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

 

UseCase

#

Action / Stimulus

Reaction

1

Requester visits the RequestList.aspx page.

The system should verify the user information and create a request.

2

The Requester enters a text phrase to search for

The system should note this phrase

3

The Requester checks which checkboxes to aid the search mechanism in narrowing the field of search

The system should determine if the user would like the search to include all comments and subject lines, or just subject lines

4

The Requester can select from the list of drop down lists which values they may be interested in

The system should note these selections before constructing a search path

5

The user should hit Search

The system should construct a search path based on the checkboxes, the text phrase box, and the drop down lists. It should then pass the Person object a constructed query to narrow the results. The results should be displayed in the Request List datagrid. The datagrid is documented in another Use Case. The Person object should also know who the Requester is via a PersonID, and additionally scope the Requester results based on visibility of location and department.
     

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

A1

A User visits the RequestList.aspx page via a direct URL link

The system should prompt the requester for valid authorization and authentication.

A2

The user could hit Reset Query

The system should clear all textbox values and reset drop down lists to empty states, and hide the request list grid on the page

A3

    

 

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

B1

    

B2

    

B3

    

 

Alternative / Additional Scenario: Cancel

#

Action / Stimulus

Reaction

C1

    
     
     

Notes:

 

 

 

 

Issues: