X hits on this document

118 views

0 shares

0 downloads

0 comments

20 / 43

Software Requirements Specification

1.

The visitor selects the help option.

2.

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

3.

End of use case.

Use Case 5: Validate Data

Use Case Description:  The validator wants to review selected metadata in the database. After review, the data may be accepted or rejected. If the data is accepted, then it is added to the database and will be available for others; otherwise, it will not be added and a notification will be sent to the provider. The Validator web site is distinct from the Visitor/Provider site. This is to simplify the user interfaces.

Actors:  Validator, Database.

Scenario 1: Review Data

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

Postconditions: Metadata has been reviewed.

1.

The validator selects the validate metadata option on the Validator Page.

2.

The system redirects the validator to the Metadata Validation Page.

3.

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

4.

The system displays the data from the dataset.

5.

The validator approves the data (ALT 2).

6.

The system marks the dataset as reviewed and makes the metadata available for visitor searches (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 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 1, step number 1.  

Scenario 2: Validate Software Metadata

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

Postconditions: Software has been reviewed.

1.

The validator selects the validate software option.

2.

The system redirects the validator to the Software Validation Page.

3.

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

4.

The system displays the software information from the list.

5.

The validator approves the data (ALT 2).

6.

The system marks the dataset as reviewed and makes the metadata available for visitor searches (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.

Software Engineering II

CS 4311 Fall 2004

Date

9/2/2004   4:15 PM

Page

20

Document info
Document views118
Page views118
Page last viewedMon Dec 05 12:29:57 UTC 2016
Pages43
Paragraphs1725
Words12810

Comments