Collegiate Sports Paging System

Use Case Specification: Pay Fee with Credit Card

Version 1.0

Revision History

Date

Version

Description

Author

October 9, 1999 1.0 Initial version Context Integration
Table of Contents

Pay Fee With Credit Card Top of page

Brief Description

This use case occurs when a new subscriber wants to pay their annual subscription fee by specifying a credit card number and PIN. This may also occur when an existing subscriber wants to renew (see alternate flow 1)

Flow of Events Top of page

Basic Flow

  1. Subscriber selects "pay fee with credit card"
  2. System prompts subscriber for credit card number, expiration date, and (optionally) PIN
  3. System sends credit card info to external system for charge validation and application
  4. Upon receipt of validation, system updates subscriber record to indicate new expiration date

Alternate Flows

Subscriber renews subscription

When this occurs, the flow runs as follows:

  1. Subscriber selects "pay fee with credit card"
  2. System displays current credit card information
  3. User either accepts information as is or updates appropriately
  4. System sends credit card info to external system for charge validation and application
  5. Upon receipt of validation, system updates subscriber record to indicate new expiration date
Invalid credit card information

If the information provided by the subscriber is not validated by the external system, an error message will be displayed and the subscriber record will NOT be updated (so that the last steps in the above flows will not be executed).

Special Requirements Top of page

Special requirements will be determined during the next iteration.

Issue - interface specifications for external credit card system need to be verified.

Preconditions Top of page

Preconditions will be determined during the next iteration.

Postconditions Top of page

Postconditions will be determined during the next iteration.

Extension Points Top of page

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

Copyright  1987 - 2003 Rational Software Corporation