Running head: ATM OPERATIONS

ATM Operations Mark Kjellander Strayer University Systems Analysis and Development CIS 210 Dr. Yohannes Abate November 03, 2012

ATM OPERATIONS ATM Operations Recently I was hired as an intern at a major bank in the Dallas / Fort Worth metropolitan area. Yesterday my supervisor came to me and asked me to develop use cases for ATM usage. Case This case use study will describe how a customer of our bank uses our Automated Teller Machines (ATM) to withdraw funds from an account. The main participants in this scenario are the bank patron and the bank itself. For the ATM to function certain things must already exist.

The ATM itself must be in direct contact with the bank, this is usually accomplished via a secure network connection to the bank via a Virtual Private Network (VPN) over the internet or in rare cases a dial up connection. The ATM must have cash that it is able to dispense to the user. If no cash is available the ATM will only be able to give balances. In this scenario the basic flow of events will be as follows. First the banking customer inserts a recognized card, this could be a bank card, ATM card or a qualified credit card. The user then validates his or her identity by use if a pin code that is entered into the ATM machine and transmitted back to the home bank. The user is validated and then the user is asked for an account to be used if the customer has multiple accounts. Then the user is presented with a menu of options. This menu usually consists of deposit, withdraw, and balance inquiry. For purposes of this scenario the customer will select withdraw cash. This is when the ATM will ask the user for an amount to be withdrawn, this is usually done via a menu of likely amounts and an other button. After the amount is entered it is transmitted back to the home bank. The amount requested is compared to the amount on deposit. If funds are available the funds are dispensed to

ATM OPERATIONS the customer and the card is returned and receipt is printed. This illustrates a successful withdrawal of funds from the ATM location. Some of the alternative flows that can happen are a bad user the user has entered an incorrect pin and the bank has rejected the transaction request. This will result in a failure and a termination of the transaction request. Another alternative is that a customer can request an improper cash amount. Such as a customer wants twenty five dollars but the ATM only has ten dollar bills loaded. This will cause an error condition and the customer will be told to choose another amount based on ten dollar increments. Or on the same vein a customer requests an amount that exceeds the limits set by the bank or the ATM. This will result in a termination of

the transaction with the message Transaction exceeds Limit. Also in the same arena a customer asks for more money than is in the account. This will cause an error and the message insufficient funds. Please reenter amount Will be given to the customer. Visio diagram is attatched The deposit flow is very similar, in this scenario the basic flow of events will be as follows. First the banking customer inserts a recognized card, this could be a bank card, ATM card or a qualified credit card. The user then validates his or her identity by use if a pin code that is entered into the ATM machine and transmitted back to the home bank. The identity is verified and the customer is presented with a menu of options. These options usually are deposit, withdrawal, transfer, and balance inquiry. For this scenario the customer will select deposit. If the customer has multiple accounts he or she will select the account to deposit into. The customer will enter the amount of the deposit . The ATM will then ask the customer to insert the envelope into the deposit slot. Once the envelope is in the ATM the envelope is stamped with a date time stamp as is required under Federal Regulation E("Federal Reserve Regulations," 2012).

ATM OPERATIONS Some of the alternative flows that can happen are a bad user the user has entered an incorrect pin and the bank has rejected the transaction request. This will result in a failure and a

termination of the transaction request. If the customer fails to get the enveloper in to the ATM in the allotted time the operation is aborted and the customer is asked if they need more time . If no response is received the entire operation is aborted and the card is returned. Visio Attatched Transfer flow is very similar, in this scenario the basic flow of events will be as follows. First the banking customer inserts a recognized card, this could be a bank card, ATM card or a qualified credit card. The user then validates his or her identity by use if a pin code that is entered into the ATM machine and transmitted back to the home bank. The identity is verified and the customer is presented with a menu of options. These options usually are deposit, withdrawal, transfer, and balance inquiry. For this scenario the customer will select transfer. The customer will be presented with a list of accounts to transfer from. The customer will select the account that is to be the from account. Then the customer will be presented with a list of accounts to be the destination for the funds. After the account is selected the customer is then asked the amount to move to the new account. After the funds are moved the receipt is printed and the transaction is completed. Some of the alternative flows that can happen are a bad user the user has entered an incorrect pin and the bank has rejected the transaction request. Also if the funds are not available to be transferred to the destination account. Ethical Issues

ATM OPERATIONS Machines often fail. This could create an ethical issue as the customer cannot have acces

to the money they have on deposit with the owning bank. Also there is no secondary verification of ID. If a card is stolen a thief could theoretically withdraw money from the customers account.

ATM OPERATIONS References Federal Reserve Regulations. (2012). Retrieved from http://www.federalreserve.gov/bankinforeg/reglisting.htm Shelly, G. B., & Rosenblatt, H. J. (2012). Systems Analysis and Design (9th ed.). Mason, Ohio: Cengage. Wells Fargo. (n.d.). www.wellsfargo.com