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
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
Basic Flow
- Subscriber selects "pay fee with credit card"
- 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).
- 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.
- If user declines current card information on file, system prompts
subscriber for credit card number, expiration date, and (optionally) PIN
- System verifies that expiration date on credit card has not already
passed.
- System sends credit card info to external system for charge validation and
application
- 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:
- Subscriber selects "pay fee with credit card"
- System displays current credit card information
- User either accepts information as is or updates appropriately
- System sends credit card info to external system for charge validation
and application
- 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). If the credit card has expired, an error message will be
displayed and the subscriber record will not be updated.
Special Requirements
None.
Preconditions
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
None.
Extension Points
None.
Copyright
1987 - 2003 Rational Software Corporation
| |
|