Use case: Transfer Money Precondition: This use case assumes that the customer has logged into the ATM. Actor: ATM Customer 1) TUCBW customer presses the Transfer button on the Transaction Selection screen. 3) Customer enters the bank account number, amount to transfer, and presses the Submit button. 5) TUCEW customer sees the confirmation message and presses the OK button on it. System: ATM 0) ATM displays the Transaction Selection screen. 2) ATM asks the customer to enter the bank account and the amount to be transferred. 4) ATM displays a confirmation that the amount has been transferred to the bank account. As per pre-condition, you need not worry about logging in process. Checking validity of an account number belonging to another bank is not instantaneous - so, usually, ATMs do not allow for inter-bank transfers. Hence, you can assume for this use case, the ATM Customer can transfer money into any account in the same bank. The use case assumes the ATM Customer is logged into their account; so the source account number is known. The destination account number is being entered by the ATM Customer in step #3. For the above user case: do the following: 1. Identify the input values, their type, value specification, valid/invalid/exceptional values (Similar to fig 20.13 pg 520 in the book) 2. How many test-cases or scenarios can be written? What would the corresponding output be? (use fig 20.14 pg 521 in the Kung book or slide #7 in test_case_register_for_events); narrow down the testcases (if need be). 3. Give concrete values for the narrowed down cases (use fig 20.15 in the Kung book or slide #8 in test_case_register_for_events) 4. Implement the concrete test cases use JUnit or similar tools for this - take a look at the file JUnit_how_to - Implementation language and it's environment is up to you. 5. Implement the ATM also without this we cannot run the testcases. It goes without saying; including it here to avoid confusion.