Collegiate Sports Paging System

Use Case Specification: Pay fee with credit card

Version 2.0

Revision History

Date

Version

Description

Author

October 9, 1999 1.0 Initial version Context Integration
December 1, 1999 2.0 Update after Elaboration 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 checks to see if user is a current subscriber.  If the user is a new subscriber, a new subscriber ID is generated by the system (using any algorithm that will generate a unique number - this may, for instance, be a continually incrementing number within the system).
  3. System checks to see if current subscriber credit card information is on file.  If it is, user is presented with indicator of credit card on file (using the last four digits of the card number), and asked if this card should be used.
  4. If user declines current card information on file, system prompts subscriber for credit card number, expiration date, and (optionally) PIN
  5. System verifies that expiration date on credit card has not already passed.
  6. System sends credit card info to external system for charge validation and application
  7. Upon receipt of validation, system updates subscriber record to indicate new expiration date

Alternate Flows

  1. Subscriber renews subscription
  2. 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
  3. Invalid credit card information
  4. 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).  If the credit card has expired, an error message will be displayed and the subscriber record will not be updated.

Special Requirements Top of page

None.

Preconditions Top of page

User is identified as a subscriber and has a subscriber ID associated with them.   For first-time subscribers, a preliminary subscriber entry is made.

Postconditions Top of page

None.

Extension Points Top of page

None.

Copyright  © 1987 - 2001 Rational Software Corporation

Display Rational Unified Process using frames

Rational Unified Process