Types of Transactions in an ATM Machine - Assignment Example

20 May Uses Cases This paper focuses on the and design of use case diagrams to the implementation of three key types transactions in an ATM machine (Shelly and Rosenblatt 201). Firstly, it is about the withdrawal transaction. This emphasizes on the event of a bank customer withdrawing money from an ATM machine. In doing this, there is a significant number of functionalities or procedures that have to be put into close consideration and executed in the successful implementation of a withdrawal transaction by a bank customer. It is important to note that, there are two preconditions that have to satisfied for the for the withdrawal transaction to be executed. The first one is the availability of cash in the dispenser while the second one is an active computer network connection between the ATM and the Bank. As indicated in the use case below, there are two main actors in the ATM withdrawal transaction. There actors are: Bank Customer Bank The withdrawal transaction begins by a customer inserting his or her Bank Card into the card slot of the ATM. Then a user validation process is performed on the basis of the card ID and the customer’s PIN. After validation, the a display screen is provided containing the available set of operations. In this scenario, the customer has directly selects “Withdraw Cash”. The ATM screen displays prompts for an account type. The selects the desired account type from the available Menu. This is immediately followed by screen for the user to input the required amount of money. All this information falls under the withdrawal use case. That is, the Bankcard ID, PIN (Personal Identification Number), account type and amount, which is then sent to the Bank as a requested transaction. The Bank then replies with a go-ahead or not reply. Upon successful approval the customer’s money is made available by the dispenser. The ATM then ejects the card and Prints a receipt. It is essential to indicate that this use case is based on the assumption that a user makes a direct and successful withdrawal. However, there are some alternative flows caused by conditions such as Wrong PIN, Invalid or Expired Card, Invalid Account type and Excess withdrawal Amount. The second diagram is a use case dependency for making an account deposit. As indicated in the use case diagram below, this is another highly technical procedure in the design of an ATM service machine. The preconditions are same as for withdrawal, which is a customer and Bank. The following is involved in the execution of an account deposit transaction. The transaction initiates by a Bank Customer inserting his or her card. This is then followed a provision of display screen by the ATM prompting a user PIN, which is integrated as the validation use case. It uses the card ID and PIN to authenticate its use. The machine displays a screen containing the menu items available for user interaction. In this case, the Bank customer selects “Deposit”. Consequently, a menu for the possible accounts is displayed for the user to choose the account type. The customer then chooses a specific menu value of the amount to deposit from the next display screen. All this information, the card ID, PIN, account type and amount is sent to the Bank for approval. If approved, the ATM machine displays a screen prompting the user to enter his or her envelope (containing money) in the security box, which prints the transaction ID on it. A receipt is then printed for the customer to pick and then the ATM ejects the customer’s Bankcard This transaction remains pending in the bank account of the customer. The next time or day, a bank representative opens the security box. He or she then counts the money and commits the transaction (Lehpamer 108). It is crucial to make it clear that there is a considerable number of alternative flows that can change the execution of this transaction. These changes can be caused by issues such as, wrong PIN, Invalid Account, No envelope inserted, more than one envelopes inserted, No money in the inserted Envelope, Too much money in the envelope, less money in the envelope and Missing Envelope. Thirdly but certainly not the least it is about a use case dependency for making an account transfer. This use case entails much less complex set of steps. As indicated in the use case diagram below, it entails the following steps. It initiated by a Bank customer inserting their card. Card validation is then done using the Bank Card ID and PIN. The ATM machine displays a set of possible options in the Menu. In this scenario, the customer chooses or selects “Transfer”. A menu list for possible accounts is then displayed for the user to choose a different account type to transfer to. The customer is prompted to enter the amount to transfer. The ATM system sends Bank Card ID, PIN, the chosen account and amount to the Bank, which replies with a go on/not reply for the requested transaction. If approved, the ATM machine prints a receipt. The ATM ejects the customer’s Bank Card and transaction ends successful. It is again important to clarify that the execution of this transaction can also be faced some alternative flows. Issues such as, a Wrong PIN, Invalid Account and Invalid Amount are the cause of the alternative flows. In conclusion, it is vital to note that there is a significant number of ethical issues that a use case exposes in connection with the development or use of the ATM system. One of the ethical issues is that the use case leads a customer to providing data, which the Bank collects, saves and can use it in the way they want. That is, the user is not given the right to tell the bank how his or her data should be used by the bank, which means it can be used for making an advertisement without the knowledge or approval by the customer. The use case hereby exposes a highly unethical practice. Secondly, information such as the amount one deposits to his or her account is something that has to remain private. However, in the ATM deposit use case, a bank representative is free to know the exact money deposited by an individual even without his approval (Bittner and Spence 52). Works cited Bittner, Kurt and Spence, Ian. Use Case Modeling. Boston, Mass. [u.a.: Addison-Wesley, 2006. Print. Lehpamer, Harvey. Transmission Systems Design Handbook for Wireless Networks. Norwood: Artech House, 2002. Internet resource. Shelly, Gary and Rosenblatt, Harry. Systems Analysis and Design. Boston: Course Technology Cengage Learning, 2012. Print. Read More