X hits on this document

167 views

0 shares

0 downloads

0 comments

16 / 43

Software Requirements Specification

Use Case 2: Register

Use Case Description: A prospective provider must register before s/he can make data available (Refer to Use Case 4). Registration is a one-time process after which the provider will be able to login.

Actors:  Provider, Database.

Scenario 1: First Time Provider

Preconditions: The provider is not registered. The provider is viewing the Provider Registration Page.

Postconditions: The provider has successfully registered and an email with information has been sent to the provider.

1.

The system displays the Provider Registration Page. This page contains a form for the user to fill out with the attributes listed below. The attributes marked with * are required.

a.

The provider’s first name. *

b.

The provider’s middle initial.

c.

The provider’s last name. *

d.

The provider’s email address. *

e.

The provider’s organization.

f.

The provider’s address.

g.

The provider’s category, i.e. commercial, government, educational or other.

h.

The provider’s login name. *

i.

The provider’s password. *

j.

The provider’s password verification. *

2.

The provider fills out the form with the requested information and selects the option to submit (ALT 1).

3.

The system verifies that the required attributes are present, that the email address has a valid form, that the login name does not exist in the database, and that the password and password verification are identical. (ALT 2, ALT 3).

4.

The system displays a thank you page which contains instructions.

5.

The provider presses continue with login link option.

6.

The system displays the Login page (Refer to Use Case 3).

7.

End of use case.

ALT 1: The user selects the option to clear the form.

A1-1: The system sets the webpage to its default state, without submitting any information.

A1-2: System returns to Scenario 1, step number 1.

ALT 2: The system detects invalid registration information. Required fields are empty, email address does not have a valid format, the login name is already in use, or the passwords do not match.

A2-1: The system displays the registration webpage.

A2-2: The system informs that one or more of the required fields are incorrect (such as invalid login name, or login name already exists), marks them in red, and includes description of appropriate corrective actions.

A2-3: The user corrects the marked fields and resubmits the information pressing the submit button (ALT 1).

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

Scenario 3: Help

Preconditions: The provider is viewing the Provider Registration Page.

Postconditions: The visitor is viewing the Provider Registration Page.

1.

The visitor selects the help option.

2.

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

3.

End of use case.

Use Case 3: Login

Software Engineering II

CS 4311 Fall 2004

Date

9/2/2004   4:15 PM

Page

16

Document info
Document views167
Page views167
Page last viewedFri Jan 20 23:08:18 UTC 2017
Pages43
Paragraphs1725
Words12810

Comments