You are on page 1of 7

Identification Summary

TITLE: CREATE PAYMENTS SUMMARY: This use case describes the steps associated with creating payments. ACTORS: 1. User (U) the user who wants to create the payment

2. Sprite (S) the program


CREATION DATE: JULY 8, 2013 VERSION: V1.0 DATE OF UPDATE: JULY 8, 2013 PERSON-IN-CHARGE: Janine Chua

Flow of Events
PRECONDITIONS: 1. User has an amount to be paid. MAIN SUCCESS SCENARIO: 1. User adds a new payment. 2. User adds amount to be paid. 3. User adds description 4. User adds card number 5. User adds CVC 6. User selects expiry month 7. User selects expiry year 8. User fills additional details 9. User successfully creates payment Sprite updates user payment database 10. Use case ends ALTERNATIVE SEQUENCE: A8. User decides to not fill in additional details 1. Proceed to Step 9 ERROR SEQUENCE: E2. Amount exceeds $999,999.99 1. Stripe sends error message asking for an amount not exceeding $999,999.99 2. Repeat Step 2 E4. Invalid card number 1. Stripe sends error message that the card number is invalid

2. Repeat Step 4 E6. Invalid expiry month 1. Stripe sends error message 2. Repeat Step 6 E7. Invalid expiry year 1. Stripe sends error message 2. Repeat Step 7

POST-CONDITIONS: 1. Payment instance is made 2. User database is updated

Identification Summary
TITLE: CREATE PLANS SUMMARY: This use case describes the steps associated with creating plans. ACTORS: 1. User (U) the user who wants to create the plan

2. Sprite (S) the program


CREATION DATE: JULY 8, 2013 VERSION: V1.0 DATE OF UPDATE: JULY 8, 2013 PERSON-IN-CHARGE: Janine Chua

Flow of Events
PRECONDITIONS: 1. User has an amount set for the plan. 2. User has decided on the interval the plan should take MAIN SUCCESS SCENARIO: 1. User adds a new plan 2. User adds ID 3. User chooses name 4. User add amount 5. User chooses interval among the choices 6. User adds trial period 7. User successfully creates plan 8. Use case ends ALTERNATIVE SEQUENCE: A5. User decides a different interval period 1. Sprite displays more options 2. Repeat Step 5 A6. User decides to not offer trial period 1. Proceed to Step 7 ERROR SEQUENCE:

E2. User failed to provide a unique ID 1. Stripe sends error message to provide a unique ID 2. Repeat Step 2 E3. Name field not filled

1. Stripe sends error message to provide a name 2. Repeat Step 3 E4. Amount exceeds $999,999.99 1. Stripe sends error message asking for an amount not exceeding $999,999.99 2. Repeat Step 4 E5. Interval not chosen 1. Stripe sends error message to choose an interval 2. Repeat Step 5

POST-CONDITIONS: 1. Plan instance is made 2. User database is updated

Identification Summary
TITLE: CREATE COUPONS SUMMARY: This use case describes the steps associated with creating coupons. ACTORS: 1. User (U) the user who wants to create the coupon

2. Sprite (S) the program


CREATION DATE: JULY 8, 2013 VERSION: V1.0 DATE OF UPDATE: JULY 8, 2013 PERSON-IN-CHARGE: Janine Chua

Flow of Events
PRECONDITIONS: 1. User has an amount set for the coupon 2. User has decided on the duration the coupon would last with a user MAIN SUCCESS SCENARIO: 1. User adds a new coupon 2. User adds amount to be taken off 3. User chooses duration 4. User adds ID 5. User adds maximum redemptions allowed 6. User adds deadline for redeem 7. User successfully creates coupon 8. Use case ends ALTERNATIVE SEQUENCE: A2a. User decides a percentile basis 1. User adds percentage to be taken off 2. Proceed to Step 3 A2a. User decides an amount basis 1. User adds amount to be taken off 2. Proceed to Step 3 A5. User decides to not put a limit on number of redemptions 1. Proceed to Step 6 A6. User decides to not put a deadline 1. Proceed to Step 7 ERROR SEQUENCE:

E2. User inputs neither or both percentage and/or amount to be taken off 1. Stripe sends error message to provide one of the two 2. Repeat Step 2 E3. Duration not chosen 1. Stripe sends error message to provide duration 2. Repeat Step 3 E4. User failed to provide a unique ID 1. Stripe sends error message asking for a unique ID 2. Repeat Step 4

POST-CONDITIONS: 1. Coupon instance is made 2. User database is updated

You might also like