Create a high level UML activity diagram that describes the behavior of the system for the Query Account, Transfer Funds, Add Cash, Startup and Shutdown use cases previously defined. Make sure to use partitions to differentiate between actions performed by the user and ones performed by the ATM machine. There is no need to specify objects flow $($transfer of objects between actions$).$ The specification of the control is enough. Since this is an initial model, keep the level of detail to a minimum. Note that you do not need to use a computer tool for this exercise, hand drawn diagrams will suffice. However, you can also use Microsoft Visio on your computer if you wish.

The Use Case for the following are listed below.

$*$Query Account Use case

Use case name: Query Account

Summary: Customer gets the information regarding account balance and transaction history of a valid bank account.

Actor: ATM customer

Dependency: Include Validate PIN use case

Precondition: ATM is idle, displaying a welcome message

Main sequence:

$1.$ Include Validate PIN.

$2.$ Customer selects Account Balance and selects the account number.

$3.$ System displays the current amount balance and transaction history.

$4.$ System prints a receipt showing the account balance and transaction history.

$5.$ System ejects card.

$6.$ System displays Welcome message.

Alternative sequences:

step $3$: If the system determines that the account number is invalid, then it displays an error message and ejects the card.

$*$Transfer Funds Use Case

Use case name: Transfer Funds

Summary: Customer transfers a specific amount of funds from a valid bank account.

Actor: ATM Customer

Dependency: Include Validate PIN use case.

Precondition: ATM is idle, displaying a Welcome message.

Main Sequence:

$1.$ Include Validate PIN use case.

$2.$ Customer selects Transfer Funds, enters the amount, and selects the account number.

$3.$ System Checks whether the customer has enough funds in the account and whether the daily limit is not exceeded.

$4.$ If all checks are successful, the system authorizes transferring of funds.

$5.$ System transfers the amount.

$6.$ System prints a receipt showing transaction number, transaction type, amount transferred, and account balance.

$7.$ System ejects card.

$8.$ System displays Welcome message

Alternative sequences:

step $3$: If the system determines that the account number is invalid, then it displays an error message and ejects the card.

step $3$: If the system determines that there are insufficient funds in the customer's account then it displays an apology and ejects the card.

step $3$: If the system determines that the maximum allowable daily transfer limit has been exceeded, it displays an apology and ejects the card.

$*$Add cash Use Case

Use case name: Add Cash

Summary: Adding cash to the ATM

Actor: ATM Operator

Precondition: ATM is out of money displaying Welcome message and Out Of Money message.

Main Sequence:

$1.$ ATM is shut down and the alarm is disabled

$2.$ The cassettes that hold money are removed and are loaded with notes.

$3.$ The system is fed with information about how much money has been loaded.

$4.$ The system checks the information.

$5.$ If all checks are successful ATM is started and the alarm is reset.

$*$Startup Use case

Use Case Name: Startup

Summary: Switches on the ATM

Actor: ATM operator

Precondition: ATM is switched off.

Main sequence:

$1.$ The system is started after the switch is turned $\text{'}$on$\text{'}.$

$2.$ The amount of money currently in the ATM is entered.

$3.$ A connection to the bank is established.

$4.$ The services for the customers come online.

Alternate sequence:

step $2$: If the ATM is out of cash then the cash is loaded

$*$Shutdown Use Case

Use Case Name: Shutdown

Summary: Shuts off the ATM

Actor: ATM Operator

Precondition: ATM is idle and no customer is in line.

Main Sequence:

$1.$ The system is shut off.

$2.$ The connection to the bank is terminated.

$3.$ The operator replenishes cash and paper if needed.