Scribd Logo
Upload

Welcome to Scribd!

  • Use Case Fsoftw2

    Uploaded by

    Minh Nguyễn
    23 views5 pages
    The document describes three use cases for an ATM: withdraw, deposit, and transfer. Each use case involves validating the customer's card and PIN, selecting an option, entering required details like amounts, and processing the transaction. If any validation fails, the system notifies the customer and ends or repeats steps as needed. Typical scenarios are provided along with alternate scenarios to handle validation errors.

    Original Description:

    ds

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document describes three use cases for an ATM: withdraw, deposit, and transfer. Each use case involves validating the customer's card and PIN, selecting an option, entering required details like amounts, and processing the transaction. If any validation fails, the system notifies the customer and ends or repeats steps as needed. Typical scenarios are provided along with alternate scenarios to handle validation errors.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    23 views5 pages

    Use Case Fsoftw2

    Uploaded by

    Minh Nguyễn
    The document describes three use cases for an ATM: withdraw, deposit, and transfer. Each use case involves validating the customer's card and PIN, selecting an option, entering required details like amounts, and processing the transaction. If any validation fails, the system notifies the customer and ends or repeats steps as needed. Typical scenarios are provided along with alternate scenarios to handle validation errors.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 5

    Use-Case Modeling ATM

    Use-Case Modeling ATM


    Use Case: Withdraw
    Actors: Customer
    Typical Course Scenario
    1. Customer inserts card
    2. System validates card
    3. Customer enters PIN
    4. System validates PIN
    5. Customer selects Withdraw option
    6. System requests Withdraw amount
    7. Customer enters Withdraw amount
    8. System validates amount can be withdrawn
    9. System ejects amount
    10. System ejects card
    11. Customer takes amount and card

    Alternate Course Scenario


    2a. Invalid card:
    2a1. System notifies user, ejects card, end of use case
    4a. Invalid PIN:

    4a1. System notifies user, requests PIN again


    4a2. Customer reenters PIN
    4b. Invalid PIN entered 3 times:
    4b1. System retains card, end of use case
    8a. Amount exceeds balance:
    8a1. System notifies user, requests amount again
    8a2. Customer reenters amount
    Use Case: Account Deposit
    Actors: Customer
    Typical Course Scenario
    1. Customer inserts card
    2. System validates card
    3. Customer enters PIN
    4. System validates PIN
    5. Costumer selects Account Deposit
    6. System requests account number
    7. Customer enters account number
    8. System verifies account number
    9. System requests deposit amount
    10. User enters deposit amount
    11. System updates account balance
    12. System generates and prints receipt and ejects card

    Alternate Course Scenario

    2a. Invalid card:


    2a1. System notifies user, ejects card, end of use case
    4a. Invalid PIN:
    4a1. System notifies user, requests PIN again
    4a2. Customer reenters PIN
    4b. Invalid PIN entered 3 times:
    4b1. System retains card, end of use case
    9a. Amount exceeds balance:
    9a1. System notifies user, requests amount again
    9a2. Customer reenters amount
    Use Case: Account Transfer
    Actors: Customer
    Typical Course Scenario
    1. Customer inserts card
    2. System validates card
    3. Customer enters PIN
    4. System validates PIN
    5. Costumer selects Account Transfer
    6. System requests source account number
    7. Customer enters source account number
    8. System verifies account number
    9. System requests destination account number
    10. User enters destination account number
    11. System verifies destination account

    12. System requests amount to transfer


    13. User enters amount
    14. System verifies available balance in source account
    15. System updates account balances
    16. System generates and prints receipt and ejects card

    Alternate Course Scenario


    2a. Invalid card:
    2a1. System notifies user, ejects card, end of use case
    4a. Invalid PIN:
    4a1. System notifies user, requests PIN again
    4a2. Customer reenters PIN
    4b. Invalid PIN entered 3 times:
    4b1. System retains card, end of use case
    8a. Source account is invalid.
    8a1. System presents error message.

    8a2. Resume step 9.

    11a. Destination account is invalid.


    11a1. System presents error message.

    11a2. Resume step 12

    14a. Source accounts balance is not sufficient to transfer.

    14a1. System presents error message.

    14a2. Resume step 15.


    14b. Amount exceeds the transferred limit.
    14b1. System presents error message.
    14b2. Resume step 15.

    You might also like