Scribd
Upload
1K views2 pages

Sample User Story For Use in Agile Models

This user story describes the need for a customer to create a credit card record to make payments. It involves 29 acceptance criteria for the customer to select a card type, enter card details like name, number and expiration date. The system must validate the fields and display errors if validation fails, then confirm if the payment method is added successfully.

Uploaded by

Niranjan Srinivas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1K views2 pages

Sample User Story For Use in Agile Models

This user story describes the need for a customer to create a credit card record to make payments. It involves 29 acceptance criteria for the customer to select a card type, enter card details like name, number and expiration date. The system must validate the fields and display errors if validation fails, then confirm if the payment method is added successfully.

Uploaded by

Niranjan Srinivas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SAMPLE USER STORY FOR USE IN AGILE MODELS

Story ID US0012
Story Type User Story
Story Short Name Create A Credit Card Record
Actor (I am a … ) Customer
Activity (I need to … ) Create a record that stores my credit card information
Outcome (So that I can … ) Select the record to make a payment using the stored card information
Acceptance Criteria 1) Customer must have an active Consumer account with GTC
2) Customer must have administrative permissions to the account
3) Customer must be registered with the site
4) Customer must be logged onto the site
5) Customer must have an active card or bank account with a positive balance
6) Customer must select to CREATE A PAYMENT METHOD
7) Customer must select USE A CREDIT CARD
8) Customer must select one card type from the list of accepted card types:
a. Visa
b. American Express
c. MasterCard
d. Discover Card
e. Diner’s Club
9) Customer must enter the cardholder name exactly as on selected credit card
10) The Cardholder Name field must accommodate 75 alpha characters
11) Customer must enter the card number
12) The number of digits in the card number must be the expected number for
the type of card selected:
a. American Express = 15 digits
b. Visa = 16 digits
c. MasterCard = 16 digits
d. Discover Card = 16 digits
e. Diner’s Club = 15 or 16 digits
13) The System is not required to check the MII of the credit card number
14) The System is not required to check the digit sequence against card type
15) The System is not required to validate the credit card number with the Luhn
method
16) Customer must enter the security code from the credit card
17) The number of digits in the security code must be:
a. 3 Digits for Visa, MasterCard, Discover, Diner’s Club
b. 4 Digits for American Express
18) Customer must enter (or select from list) the month (mm) in which the card
will expire
19) Customer must enter (or select from list) the year (yyyy) in which the card
will expire
20) Customer must enter the 5-digit ZIP Code for the Billing Address associated
with the selected card
21) System must display a summary of the credit card information submitted
22) System must display the terms and conditions associated with the
transaction
23) System must validate each required form field is not Null or blank
24) Customer must submit the payment method
25) Customer must agree to the Terms and Conditions
26) Customer must confirm the payment method
27) System must synchronously validate card number with card provider
28) System must display an outcome (Success/Failure) on processing the
transaction
29) System must display error messages for any field that does not successfully
validate
30) System must visually highlight each form field that does not successfully
validate
Review Status Accepted
Team Status Scheduled
Priority High
Frequency Moderate
Notes 1) Administrative permissions available by right to Primary Account Holder
2) Administrative permissions may be bestowed upon a SubAccount
3) See General Acceptance Criteria
Last Edited On 06/12/2011
Last Edited By JIK

You might also like