Intern Software Developer &Bull; Describe a Use

¶ … Intern Software Developer • Describe a use case, complete with typical and alternate courses, that documents the event of a bank customer withdrawing money from an ATM It is argued by Constantine & Lockwood that the use cases user interface design and software usability are of paramount importance. Use case can be used as a very effective in making better usability if the intentions are kept in mind and by avoiding elaboration and making the process simpler.

(Harmelen, 2001) Therefore many extraneous possibilities are avoided and assumed that in such cases the customer will contact the customer care centre of the bank (for example: cash getting stuck, card getting stuck etc.). Thus in this use case the simple process is alone illustrated. In use cases of this type, there are more than one possibility depending on the technology available and the banking networks. The type of ATM is also in question. Description: Intention is that the customer withdraws money from the ATM.

There are the actors in the scenario namely 1) The customer with the credit or debit card, 2) The Functioning ATM with cash, 3) The banking network, the core banking system, and 4) customer care centre. These are involved in the use of the ATM by the customer or any transaction. Where the customer withdraws money, the customer's bank account and the balance, and place of the ATM are involved. The Use Case is as follows: 1. ATM is on and the welcome screen prompts customer to enter card in slot. 2.

The customer's card is read and the verification module is executed. If the card cannot be processed a message is displayed 'this card cannot be used in this ATM' The ATM returns card. Goes to step 1 mode above. 3. The customer is prompted to enter PIN 4. Customer enters PIN 5. It is verified with the system and then the ATM moves to the next screen. If the PIN is wrong a message is displayed 'Please press cancel button and enter PIN again' Once the cancel button is pressed ATM goes to step 3 6.

The customer is prompted to enter the amount 7. The amount is verified and the account checked 8. If the amount is available cash is dispensed. 9. Slip is printed. Entry made in ledger at core system. If cash not available the ATM closes the transaction with a message displayed 'Insufficient Balance' 10 ATM returns card in all cases and goes to step 1 11. On any problem the Customer contacts the care centre. End of use. • Illustrate the use case using Visio or a similar product.

The Use Case illustrations follow the simple and step format that has the domain and the sequence of actors and actions given in ovals as was the first practice. (Grady, 2006) • Describe a use case dependency for making an account deposit. Illustrate this use case with Visio or a similar product Description: Intention is that the customer makes a deposit at the counter.

There are the actors in the scenario namely 1) The customer with filed form and cash, 2) The teller and the computer system, 3) The banking network, the core banking system, and 4) the printing system. These are involved in the use case. Where the customer pays money at the counter, the Chelan is checked and the teller enters the transaction in the computer, prints the customer's bank account book and updates it, returns to customer. This is an interaction model with two or more human interface actors- and the system.

In the interaction model the objects must collaborate to achieve the end result. There can be different levels of abstraction for the interaction. (Blaha; Rumbaugh, 2007) The basic and simple acts are being used here. The Use Case is as follows: 1. Customer approaches teller counter with cash and Chelan filled 2. The teller invokes the software by entering customer account number 3. Teller then enters the cash transaction to software. 4. The system updates amount and sends a printable document 5. The teller enters the customer passbook to the printer 6. Updated print is done. 7.

Customer receives the printed book. 8. Teller sends software to normal mode. End of use. • Describe a use case dependency for making an account transfer. Illustrate this use case with Visio or a similar product. Description: Intention is that the customer wishes to send money from his account to another. In this case the capability of the system is in question. It is to be seen if the capabilities of the system will help meet the actor's actions.

The actors and the system must collaborate with the systems response being critical. (Bittner; Spence, 2003) In this case the transfer involves the whole networking of banks. There are the actors in the scenario namely 1) The customer and account, 2) The second bank at some place with an account number, 3) The banking network, the core banking system, and 4) Two Banks. The Use Case is as follows: 1. The customer logs on to the terminal prompts customer to enter his ID 2. The customer's ID verification module is executed.

If the customer is not entering proper password message is displayed Please enter password. The screen returns to step 1 screen. 3. The customer is prompted to select bank branch and account of receiver. 4. Customer enters details 5. It is verified with the system and then the verification done with customer. If the receiver is not found it prompts for recheck. On that goes to step 5 6. The customer is prompted to acknowledge transaction -- with yes/no query 7.

On yes the amount is sent from the system to the banking system of the receiver 8. The receiving bank makes transaction entry and returns details. 9. Customer gets a printable.