Use Case Statement

By Manuel Dennis III

Name

Default Login

Description

An overview of the Default Login page

Dependencies

A menu control

The business logic layer must exist to retrieve user and person objects and associated data

Scope

To manage user access to the Work Request application

Primary Actors

· Assigner, Worker, Requester, Approver, Administrator

Secondary Actors

· Future user

Pre Conditions

· All fields must be cleared and the user should login and be authenticated

Success End Conditions

· The user can modify his login information to gain access to the Work Request application

Failure End Conditions

· Login information fails to verify or unauthorized user is allowed into the system

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

Use Case

#

Action / Stimulus

Reaction

1

User enters username and password

System notes changes.

2

User presses Login button

System verifies user and activates menu items

System stores the userid and personid in the session variables

3

    

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

A1

User Logout

System removes user session

A2

    

A3

    

 

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

B1

User presses Appeal Access link

User’s email application is launched and populated with info regarding her desire to use the Work Request application.

B2

    

B3

    

 

Alternative / Additional Scenario: Cancel

#

Action / Stimulus

Reaction

C1

    
     
     

Notes:

 

 

 

 

Issues: