Selman ALPDÜNDAR

ATM Withdraw Cash – Use Case

Use Case Description: Allows any bank customer to obtain cash from their bank account. This use case begins when an ATM customer chooses a type of account from which the cash is to be withdrawn (e.g. checking) from a list of possible accounts, and to choose a dollar amount from a list of possible amounts. The system sends the transaction to the financial system for verification. If the financial system approves the transaction, the machine dispenses the appropriate amount of cash and issues a receipt. The dispensing of cash is also recorded in the ATM’s log.

Use Case Name:

  • Withdraw Cash

Actors:

  • Any Bank Customer (Has an existing account)
  • Banking System (Any bank’s ATM and its infrastructure)

Triggers:

  • The user wants to withdraw money from one of his/her account.

Preconditions:

  • The ATM is operational.
  • The bank customer has a card to insert into the ATM.

Post conditions:

  • The bank customer has received their cash (and optionally a receipt).
  • The bank has debited the customer’s bank account and recorded details of the transaction.

Normal Flow:

  1. The customer enters their card into the ATM.
  2. The ATM verifies that the card is a valid bankcard.
  3. The ATM requests a PIN code.
  4. The customer enters their PIN code.
  5. The ATM validates the bankcard against the PIN code.
  6. The ATM presents service options including “Withdraw”.
  7. The customer chooses “Withdraw”.
  8. The ATM verifies sufficient funds in the customer’s bank account.
  9. The ATM presents options for amounts.
  10. The customer selects an amount or enters an amount.

11. The ATM verifies that the customer is below withdrawing limits.

  1. The ATM verifies that it has enough cash in its hopper.
  2. The ATM debits the customer’s bank account.
  3. The ATM returns the customer’s bankcard.
  4. The customer takes their bankcard.
  5. The ATM issues the customer’s cash.
  6. The customer takes the cash.
  7. Use case ends.

Alternate Flows:

2A1: The user has an invalid card. This can be caused because of the condition of the card i.e. card is either broken, bent or magnetic stripe/computer chip is damaged or the encoded data is erased, blocked or not authorized account, inactivated card and/or wrongly inserted card i.e. card is upside down.

  1. The ATM will display error message.
  2. The ATM will eject the card.
  3. The user will take the card.
  4. The use case returns to step 1 and continues.

5A1: The user entered an invalid PIN.

  1.  The ATM will indicate that the wrong PIN has been entered.
  2.  The system will log and check number of tries.
  3.  The ATM will ask the customer to enter their PIN again.
  4.  The use case returns to step 4 and continues.

5.3A1: The user exceeded the number of PIN tries.

  1.  The ATM will retain the user’s card.
  2.  The ATM will capture a 10-second video image of the Customer.
  3.  The ATM will create an event log entry to record the fact that the customer failed to enter the correct PIN number in three attempts.
  4.  The ATM will send the event log entry to the bank system.
  5.  The use case ends.

8A1: The customer does not have sufficient funds in the bank account.

  1. The ATM will inform the customer that the bank has rejected the withdrawal.
  2. The ATM will advise the user to contact the bank for further details.
  3. The system will record a transaction log entry for the transaction including the reason given for the transactions rejection.
  4. The use case ends.

11A1: The user tries to withdrawal cash above daily withdraw limits.

  1.  The ATM will display error message that explains the daily withdrawal limit.
  2.  The ATM asks the customer to enter a smaller amount.
  3.  The use case returns to step 12 and continues.

12A1: The ATM hopper does not have sufficient cash.

  1.  The ATM will display error message.
  2.  The ATM will display the maximum available withdraw limit on cash.
  3.  The system will create an event log entry to record the fact that the ATM has run out of cash.
  4.  The system will send the event log entry to the bank.
  5.  The user will enter a smaller amount.
  6.  The use case returns to step 13 and continues.

12.5A1: The user selects to quit the session.

  1.  The user will cancel the process.
  2.  The ATM will eject the card.
  3.  The user will take the card.
  1.  The use case ends.

12A2: The ATM hopper has the wrong denomination of cash.

  1. The system will ask the customer for the required amount indicating that the amount entered must be a multiple of the smallest denomination note held.
  2.  The user will enter a different amount.
  3.  The use case returns to step 13 and continues.

12.2A1: The user selects to quit the session.

  1.  The user will cancel the process.
  2.  The ATM will eject the card.
  3.  The user will take the card.
  1.  The use case ends.

14A1: The card stuck in the ATM.

  1.  The ATM will beep to alert the customer.
  2.  The ATM will capture a 15 second video image of the customer.
  3.  The ATM will create an event log entry to record the fact that a card has been retained because it became stuck in the card reader.
  4.  The system will send the event log entry to the bank.
  5.  The ATM will explain the machine malfunction to the user.
  6.  The ATM will ask the customer to speak to bank staff.
  7.  The ATM will disable itself.
  8.  The use case ends.

15A1: The customer fails to take the card.

  1.  The ATM will prompt and beeps the customer to take their card.
  2.  The ATM will wait for a period of time.
  3.  The ATM will retain the card.
  4.  The ATM will create an event log entry to record the fact that the card was left behind in the ATM.
  5.  The system will send the event log entry to the bank.
  6.  The use case ends.

16A1: The cash stuck in the ATM.

  1.  The ATM will beep to alert the customer.
  2.  The ATM will capture a 15 second video image of the customer.
  3.  The ATM will create an event log entry to record the fact that there has been a dispensing error.
  4.  The system will send the event log entry to the bank.
  5.  The ATM will explain the machine malfunction to the user.
  6.  The ATM will ask the customer to speak to bank staff.
  7.  The ATM will disable the withdraw cash service option.
  8.  The use case ends.

17A1: The customer fails to take their cash.

  1.  The ATM will prompt the customer to take their cash.
  2.  The ATM will wait for a period of time.
  3.  The ATM will retrieve the cash checking the amount that has been left behind.
  4.  The ATM will create an event log entry to record the fact that cash has been left uncollected.
  5.  The ATM will record a transaction log entry for the transaction including both the amount that should have been taken and the amount that was actually taken.
  6.  The system will send the event log entry to the bank.
  7.  The use case ends.

 

withdrawcash-usecasespecification-example



1 comment

  1. hi,
    please send the State transition digaram for the “Leave management system”
    how to write uses cases steps for the booking a flight/bus/train.
    not use case diagram .please send fastly its urgent.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.