X hits on this document

147 views

0 shares

0 downloads

0 comments

17 / 43

Software Requirements Specification

Use Case Description: A provider or validator must login with a valid login name and password in order to access restricted functions. These include providing data (Refer to Use Case 4) and validating data (Refer to Use Case 5).  

Actors:  Provider, Validator, Database.

Scenario 1: Login

Preconditions: The Actor must be registered (Refer to Use Case 2).  The Actor is viewing the Login Page.

Postconditions: The Actor has successfully logged into the system.

1.

The system displays the Login Page.

2.

The Actor enters a login name, a password and selects the submit option (ALT 1).

3.

The system submits an SQL search query to the database using the login name.

4.

The database returns the encrypted password.

5.

The system encrypts the password entered and compares to the password returned by the database. The passwords match (ALT 2).  NOTE: The password is encrypted on the client side and compared on the server side. The server does not send an encrypted password to a client, and an unencrypted password is never transferred over the network.

6.

The system redirects the Actor to the Actor Page.

7.

End of use case.

ALT 1:The Actor selects the cancel option.

A1-1: The system returns to the Home Search Page.

A1-2: End of use case.

ALT 2: The system detects invalid login name or password.

A2-1: The system displays an error page.

A2-2: The system waits 5 seconds.

A2-3: System returns to Scenario 1, step number 1.

Scenario 2: Password Recovery

Preconditions: The Actor must be registered.  The Actor is viewing the Login Page.

Postconditions: The Actor has successfully received an email with his password.

1.

The system displays the Login Page.

2.

The Actor selects forgot password option.

3.

The system displays the Password Recovery Page.

4.

The Actor enters his log in name.

5.

The system submits an SQL search query to the database using the login name (ALT 1).

6.

The database returns the Actor’s email address.

7.

The system creates a new temporary password and emails it to the Actor.

8.

The system submits the new password to the database.

9.

The system sends the new password to the Actor’s email address.

10.

The system displays the Password Recovery Instructions Page with instructions.

11.

End of use case.

ALT 1: The Actor login name is not found.

A1-1: The system displays a webpage indicating that the provider login name was not found.

A1-2: The Actor hits the ok button.

A1-3: The system redirects the Actor to the Provider Registration Page (Refer to Use Case 2).

A1-2:End of use case.

Scenario 3: Help

Preconditions: The visitor is viewing the Login Page.

Postconditions: The visitor is viewing the Login Help Page.

1.

The visitor selects the help option.

2.

The system redirects the visitor to the Login Help Page and to the section associated with the page from which the visitor came from.

Software Engineering II

CS 4311 Fall 2004

Date

9/2/2004   4:15 PM

Page

17

Document info
Document views147
Page views147
Page last viewedTue Jan 17 12:18:06 UTC 2017
Pages43
Paragraphs1725
Words12810

Comments