Use Case Name: Login_Use_Case

Iteration: Filled

Summary:

All users who request entry into the system must prove they are who they say they are. This aplies to users inside the company and outside the company. Who the user is determines what the user has access to.

Basic Course of Events:

1. The use case begins when the user accesses the system.

2. The system responds by requesting user identification and password.

3. The user enters the identification and password.

4. The system responds by verifying the combination of ID and password against a list of valid users.

5. The system responds by notifying the user that the ID and password are valid and allows the user

access to the application.

Alternative Paths:

None

Exception Paths:

1. In step 4, if the user identification and password combination is not valid, the

system responds by notifying the users that log in failed and asks the user

to try again. The system returns to step 2.

2. If the user tries unsuccessfully three times, the system responds by informing

the user to contact the pharmacist and the system returns to the

ready/wait state.

3. In step 4, if authentication fails because the user’s account is suspended, the

system responds by informing the user to contact the pharmacist and the

system returns to the ready/wait state.

Extension Points: Administrator, Customer

1. If the user is identified as a customer, the system presents the user with the

customer use case.

2. If the user is identified as an administrative, the system presents the user with

the administrator use case.

Trigger:

The user repsonds to the login prompt at the ready/wait state.

Assumptions:

The system is operational

Preconditions:

The system is operational and the system is in the ready/wait state

Postconditions:

The validated user is presented with the appropriate use case

Related Business Rules:

1. The user must be in good standing.

Author: HGG

Date: Fall 2002