X hits on this document

125 views

0 shares

0 downloads

0 comments

21 / 43

Software Requirements Specification

ALT 1: The validator selects the cancel option.

A1-1: The system redirects the user to the Provider Page.

A1-2: End of use case.

ALT 2: The validator selects the disapprove option.

A2-1: The system marks the data as disapproved.

A2-2:The system prompts the validator for an explanation.

A2-3:The validator enters an explanation.

A2-4:The validator selects the submit option.

A2-5:The system sends an email to the provider indicating that the data has been rejected, including the validator’s explanation.

A2-6:The system redirects the validator to the Validator Page.

A2-7: Return to Scenario 2, step number 1.  

Scenario 3: Submit Glossary Entry

Preconditions: The validator must be logged in to the system (Refer to Use Case 3).   The provider is viewing the Validator Page.

Postconditions: Glossary has been reviewed.

1.

The validator selects the validate glossary entry option.

2.

The system redirects the validator to the Glossary Term Validation Page.

3.

The validator selects the review glossary term option associated with that term from the table (ALT 1).

4.

The system displays the glossary term definition from the list.

5.

The validator approves the data (ALT 2).

6.

The system marks the glossary term as reviewed and makes the term available for visitor viewing the glossary (Refer to Use Case 1).

7.

The system sends an email to the provider indicating that the data set has been accepted.

8.

The system redirects the validator to the Validator Page

9.

End of use case.

ALT 1: The validator selects the cancel option.

A1-1: The system redirects the user to the Provider Page.

A1-2: End of use case.

ALT 2: The validator clicks disapprove option.

A2-1: The system marks the data as disapproved.

A2-2:The system prompts the validator for an explanation.

A2-3:The validator enters an explanation.

A2-4:The validator selects the submit option.

A2-5:The system sends an email to the provider indicating that the data has been rejected, including the validator’s explanation.

A2-6:The system redirects the validator to the Validator Page.

A2-7: Return to Scenario 2, step number 1.  

Scenario 4: Change Account Information

Preconditions: The validator must be logged in to the system (Refer to Use Case 3).   The validator is viewing the Validator Page.

Postconditions: The validator has changed his information.

1.

The validator selects the change account option on the Validator Page.

2.

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

3.

The database returns all the account information associated with that validator.

4.

The system redirects the validator to the Change Validator Information Page.

5.

The system displays a form with all the attributes associated with the user.

6.

The validator changes a field.

7.

The validator selects submit changes (ALT1).

Software Engineering II

CS 4311 Fall 2004

Date

9/2/2004   4:15 PM

Page

21

Document info
Document views125
Page views125
Page last viewedWed Dec 07 14:42:07 UTC 2016
Pages43
Paragraphs1725
Words12810

Comments