Use case:

Create a new account for a new user

Primary Actor(s):

Client
WebServer

Secondary Actor(s):

AccountsServer, Accounts Database

Brief Description:

The Client requests for a new account to be created for a new user. The Webserver provides the client a new account provided all the required information is available.

Preconditions:

The Client, WebServer, and AccountsServer are active and the server is connected to the database.

Flow of Events:

1. The Client makes a request to the WebServer to create a new account.
2. The WebServer asks the client for the necessary information.
3. The WebServer validates the information with the AccountsServer.
4. The WebServer provides the client with a new account.

Postconditions:

The Client gets a new account.

Priority:

High.

Alternative flows and exceptions:

If there already exists a user with the specified name and ID, the WebServer informs the client that an account has already been created.

Use case:

Create an additional account for an existing user

Primary Actor(s):

Client
WebServer

Secondary Actor(s):

AccountsServer, Accounts Database

Brief Description:

The Client requests for an additional account to be created for an existing user. The Webserver provides the client a new account provided all the required information is available.

Preconditions:

The Client, WebServer, and AccountsServer are active and the server is connected to the database.

Flow of Events:

1. The Client makes a request to the WebServer to create an additional account.
2. The WebServer asks the client for the necessary information.
3. The WebServer validates the information with the AccountsServer.
4. The WebServer provides the client with an additional account.

Postconditions:

The Client gets an additional account.

Priority:

High.

Alternative flows and exceptions:

Use case:

Authenticate Client

Primary Actor(s):

Client
WebServer

Secondary Actor(s):

AccountsServer, Accounts Database

Brief Description:

The Client attempts to login to the account with a user ID and password. If authenticated the client is provided access to his/her account information.

Preconditions:

The Client, WebServer, and AccountsServer are active and the two servers are connected to the database.

Flow of Events:

1. The Client makes a request to the WebServer to login, and provides his/her user ID and password.
2. The WebServer asks the client for the necessary information.
3. The WebServer validates the information with the AccountsServer.
4. The WebServer provides the client with a new account.

Postconditions:

The Client gets access to his/her information.

Priority:

High.

Alternative flows and exceptions:

If the account is not validated the client is provided with a incorrect login page.