• Uncategorized

ATM Transaction Use Case

ATMTransaction Use Case

InstitutionAffiliation

ATMTransaction Use Case

Withdrawals,deposits, transfers or inquiries require specific features in atransaction. However, the flow of events in all the transactions isalmost similar with the exception of very little dissimilarity. A usebegins in a session when a customer chooses a transaction type from alist in an ATM (Al-Shamailh, 2015). After the insertion of a card,the customer is required to provide specific information such asaccount pin and the amount to withdraw or deposit or the inquiry heor she would want to make. Thus, an ATM system Use case can beillustrated as shown below:

Figure1: ATM System Use Case

WithdrawalTransaction Use Case

Awithdrawal transaction requires a customer to pick an account fromwhich to withdraw the money. For example, a client can decide to usea savings or a checking account from a wide list of possible accountsowned or registered in the system. After picking an account, thecustomer then selects a specific amount of money before going aheadto accept the completion of the transaction. However, if the amountrequested exceeds the one in the account, an insufficient alertmessage is sent to the customer and he or she will make necessarychanges. On the other hand, if the transaction is approved, the ATMwill be able to dispense the requested amount and issue a receipt toformalize the transaction (Al-Shamailh, 2015). The ATM will then keepa log of all details of the transactions that occurred within aparticular period of time. At the same time, the customer has theability to cancel an operation by pressing a cancel key located onthe ATM, and this is only before selecting the amount required sinceit is impossible to rollback the process after the selection has beenmade. The Use Case diagram illustrates as figure 2 below gives anoverview of a withdrawal process.

Preconditions

  • Customer must have a valid ATM card and a working Pin

  • ATM must be connected to an active network and linked to the bank system

  • ATM must have enough money to support the transaction

  • The ATM system must have a withdrawal option

Post-conditions

Thecustomer should be able to get the exact amount requested immediatelyand a receipt that shows the completion of the transaction. Further,the system must be able to appropriately update the customer’saccount immediately the transaction is complete.

Figure2: ATM Withdrawal

Specifications

Theprimary actor in this case is the customer and other stakeholdersinvolved include the bank, and the administrator. The customer wantsa quick and accurate transaction and be able to get his or her money.The bank must provide high quality and reliable services to thecustomer, and charge the customer the appropriate amount for thetransaction. The administrator must ensure that the ATM has therequired amount to meet daily demands. The whole process should befast and accurate (V.Jog &amp R. Pardeshi, 2014).

NormalFlow of Events

Customerinserts ATM card into Machine and keys in a PIN, the system validatesthe details provided, customer chooses the withdraw option, customerthen chooses the amount to withdraw, customer submits the amount,system carries out a validation process, customer then presses the OKbutton, and the ATM ejects the card, cash and receipts is printed,and finally customer account is updated (V.Jog &amp R. Pardeshi,2014).

AlternateFlow of Events

  • If a customer enters a wrong pin, the system will reject the transaction and prompt the customer to enter a valid pin to ensure that the transaction progresses.

  • The customer inserts an incompatible card the machine rejects the card and displays an error message.

  • Customer key’s in a higher amount that exceeds the limit, the system denies the execution of the withdrawal process.

DepositTransaction Use Case

Justlike other transactions, in a deposit scenario, a customer will alsochoose the accounts to engage in the whole process. The customer caneither choose a savings, ordinary or a checking account. The systemasks a customer to key in a specific amount to deposit. The initialstep is for the machine to check if the customer is eligible to makea deposit. If he or she is eligible the ATM allows the customer tocarry out the transaction and issues a receipt. An acknowledgmentmessage is then sent on the reception of the money. The amount iscredited in the banking system to the customer’s account and theverification process is conducted later. The ATM keeps all thedetails of the transaction. Customers have the ability to canceldeposit transactions, and this is possible by pressing the Cancel Keyon the ATM before inserting the amount to deposit (Outair, Lyhyaoui,&amp Tanana, 2014). Once the inserted envelope is accepted, theoperation cannot be rolled back. Further, if there is a delay ininserting the envelope, then the operation is cancelledautomatically.

Figure3: Deposit Use Case

Pre-conditions

  • Customer must have a registered account, ATM card and working PIN

  • There must be an active network connecting the ATM to the banking system

  • The machine must have the capability to accept money and a deposit option

Post-condition

Thecustomer is able to get acknowledgement on the deposited money orcheque as well as a receipt to authenticate the transaction. At thesame time, the customer’s system must be updated after thetransaction.

Specifications

Primaryactor in this case is the customer and other involved stakeholdersinclude the bank and the ATM administrator. The customer deposits anamount and the bank provides high quality services to the customer toenable the completion of the transaction. The ATM administratorensures that the machine can accept deposits and print receipts.

TransferTransaction Use Case

Atransfer transaction compels a customer to select a specific accountfrom which to make the transaction. This can be a saving or checkingaccount. The operation further requires a customer to make a choiceof an account to be used in the process and at the same time input acorrect amount to facilitate a transfer. The bank system is requiredto confirm and authenticate the accounts and ensure that the accountfrom which to transfer money as the required amount to enable thecompletion of the transaction. However, if no enough amounts arepresent to support the transaction, an alert message prompting thecustomer on insufficient amount is displayed on the machine (Outair,Lyhyaoui, &amp Tanana, 2014).

Onthe other hand, if the process gets approved, the system transfersthe required amount before issuance a receipt. The entire process isrecorded and stored in the transaction log for reference purposes. Incase the transaction was erroneous, the customer will have a smallwindow to cancel the process, and this is only possible beforeselecting the amount to transfer otherwise it will not be possibleto cancel the process after inserting the required amount andconfirming the same. In case a wrong pin is keyed in an error messageis sent. A wrong PIN prompt mainly originates when a customer entersan authentication key that is not approved by the system. In suchcases the system will reject the transaction and prompt the customerto try once more. However, if the customer enters wrong PINs thriceconsecutively the card will be retained and the customer asked tocontact the bank immediately.

Preconditions

  • A person must be registered account holder, have a valid ATM card and a PIN.

  • The ATM must be connected to the main bank system and have a strong and active network.

  • The machine must be able to carry out transfer transactions.

Post-conditions

Acustomer must be able to acknowledge the transfer of money andreceive a receipt to authenticate the whole process.

Specifications

Theprimary actor is the customer who asks to transfer money. Otheractors include the bank and the ATM administrator. The bank mustensure that money is available to complete the transaction andauthenticate account ownership. The ATM administrator should ensurethat the ATM functions as required (Turan, 2015).

Figure4: ATM Transfer Use Case

EthicalIssue

Thecustomer authentication process is one of the major ethical issuesconnected with the use of ATMs. The authentication process can bedepicted as a partial process that does not necessarily authenticateif it is really the account holder using the ATM card or not.Authentication through passwords does not suffice as a strongerapproach of protecting the confidentiality and privacy of thecustomers. The issue explains why it is common for parents to sendchildren to make withdrawals. At the same time, it explains theenormous risks of misplacing the ATM cards and if the cards fall inwrong hands. In case a stranger stumbles into an account holder’sPIN it means that they can withdraw money from their accounts. Thus,it is imperative to institute a two step authentication processes inATM in a bid to protect account holders (Nair, 2014).

Anotherethical issue is the use and access of data. Every time a customertransacts using an ATM, there is a trail of digital data left behind.A higher proportion of the data is about the customer that connotesall the activities conducted within a period of time. The bank whichhouses massive data warehouses keeps and stores the data for futureuse. However, on most occasions, the customer is not given themandate to dictate the use of the data and this may impact his or herprivacy and confidentiality. Thus, there should be a system in placethat allows customers to be the sole managers of their data.Alternatively, there should be a strict policy or regulation thatgoverns who should access the data. The EU privacy act stipulatesthat customers ought to have the final say in the use of their dataotherwise the whole process will be illegal. Ethical issues arisewhen a question of security pops-up. Most often there are no clearlines on who is responsible for the security of the ATM cards. If thecustomer losses the card and his or her account compromised, banksreject claim of a loss depicting that it was beyond their control.

References

Al-Shamailh,A. (2015). An Experimental Comparison of ER and UML ClassDiagrams.&nbspIJHIT,&nbsp8(2),279-288. http://dx.doi.org/10.14257/ijhit.2015.8.2.26

Nair,M. (2014). Fractional Reserve Banking, Client Collaboration, andFraud.&nbspJBus Ethics,&nbsp130(1),85-92. http://dx.doi.org/10.1007/s10551-014-2176-x

Outair,A., Lyhyaoui, A., &amp Tanana, M. (2014). Towards an AutomaticEvaluation of UML Class Diagrams by GraphTransformation.&nbspInternationalJournal of Computer Applications,&nbsp95(21),36-41. http://dx.doi.org/10.5120/16721-7063

Turin,M. (2015). Integrating Software Metrics with UML ClassDiagrams.&nbspLNSE,&nbsp3(3),220-224. http://dx.doi.org/10.7763/lnse.2015.v3.194

V.Jog,V. &amp R. Pardeshi, N. (2014). Advanced Security Model forDetecting Frauds in ATM Transaction.&nbspInternationalJournal of Computer Applications,&nbsp95(15),47-50. http://dx.doi.org/10.5120/16674-6679