Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

**Collegiate Sports Paging System

Use Case Specification: Edit Profile**

Version 1.0

Revision History

DateVersionDescriptionAuthor
October 9, 19991.0Initial versionContext Integration
Table of Contents
  • [Edit Profile](#Edit Profile)
  • [Flow of Events](#Flow of Events)
  • [Special Requirements](#Special Requirements)
  • Preconditions
  • Postconditions
  • [Extension Points](#Extension Points)

Edit Profile

Brief Description

This use case occurs when a subscriber wishes to change their profile information or when a new subscriber wishes to enroll.

Flow of Events

Basic Flow

  1. User selects “Edit Profile”
  2. System displays categories of profile (personal, preferences, pager information, “page me when” selections).
  3. User selects category
  4. System displays detail
  5. User updates detail, presses “OK”
  6. System validates data as required, updates subscriber profile.

Alternate Flows

If this is a new subscriber, the use case “Pay Fee with Credit Card” is invoked following step 5 above.

Special Requirements

Special requirements will be determined during the next iteration.

This needs to be secured as credit card information may be in the profile.

Preconditions

Preconditions will be determined during the next iteration.

Postconditions

Postconditions will be determined during the next iteration.

Extension Points

Extension points of the use case will be identified during the Elaboration Phase.