Task $1-$ Domain Modeling

$1.$ Identify the principal domain entities

$2.$ Create a domain model using UML class diagrams to represent the relationships between the

main entities in the domain. 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.

Task $2-$ Functional Requirements

Given the problem definition and the UML use case diagram shown in Figure $1,$ define the use cases for

the Query Account, Transfer Funds, Add Cash, Startup and Shutdown. Note that the two cases Withdraw

Funds and Validate PIN $($seen in class$)$ are already given.

Figure $1$: Banking System use case model

Validate PIN Use Case

Use case name: Validate PIN

Summary: System validates customer PIN

Actor: ATM Customer

Precondition: ATM is idle, displaying a Welcome message.

Main sequence:

$1.$ Customer inserts the ATM card into the card reader.

$2.$ If system recognizes the card, it reads the card number.

$3.$ System prompts customer for PIN.

$4.$ Customer enters PIN.

$5.$ System checks the card's expiration date and whether the card has been reported as lost or

stolen.

$6.$ If card is valid, system then checks whether the user$-$entered PIN matches the card PIN

maintained by the system.

$7.$ If PIN numbers match, system checks what accounts are accessible with the ATM card.

$8.$ System displays customer accounts and prompts customer for transaction type: withdrawal,

query, or transfer.

Alternative sequences:

Step $2$: If the system does not recognize the card, the system ejects the card.

Step $5$: If the system determines that the card date has expired, the system confiscates the card.

Step $5$: If the system determines that the card has been reported lost or stolen, the system

confiscates the card.

Step $7$: If the customer$-$entered PIN does not match the PIN number for this card, the system reprompts for the PIN.

Step $7$: If the customer enters the incorrect PIN three times, the system confiscates the card.

Steps $4-8$: If the customer enters Cancel, the system cancels the transaction and ejects the card.

Postcondition: Customer PIN has been validated.

Withdraw Funds Concrete Use Case

Use case name: Withdraw Funds

Summary: Customer withdraws 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 Withdrawal, enters the amount, and selects the account number.

$3.$ System checks whether customer has enough funds in the account and whether the daily

limit will not be exceeded.

$4.$ If all checks are successful, system authorizes dispensing of cash.

$5.$ System dispenses the cash amount.

$6.$ System prints a receipt showing transaction number, transaction type, amount withdrawn,

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 withdrawal amount has

been exceeded, it displays an apology and ejects the card.

Step $5$: If the ATM is out of funds, the system displays an apology, ejects the card, and shuts

down the ATM.

Postcondition: Customer funds have been withdrawn.

Task $3-$ UML Activity Diagram

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.