alessandropro/cps406-group6-atm

CPS 406 - Section 4 - Group 6

cps406-group6-atm's Issues

3.2.2. ValidateAccountNumber

UC #2 ValidateAccountNumber.pdf

3.2.2. ValidateAccountNumber
Priority: 1
Brief Description: System validates the customer account number by checking the database for existing matching account.
Actors: System, Database
Triggers: Customer has inputted an account number to be validated and presses ‘OK’
Flow of Events:
Basic Flow – Validate Account Number:

1. The Use Case starts when the system has received a 16 digit account number to be validated.
2. System searches for appropriate account corresponding to 16 digit account number in the database.
   3. If account number exists
   3.1 Exit Use Case and return to Login menu indicating a successful validation.
   4. Else account number does not exist
   4.1 Exit Use Case and return to Login menu indicating a failed
   validation.
   Alternative Flow: None
   Special Requirements: None
   Preconditions: Application must be running, account number must be entered
   Postconditions:
   Success Postconditions:
   1. Account is verified and open to ATM specific actions.
      Failure Postconditions:
   2. Account is not verified, therefore system goes back to log in.
      Extension Points: none

Use Case List

A Brainstorm of Use Cases for our discussion

3.2.14 Deposit

UC #14 Deposit.pdf

3.2.14 Deposit
Priority: 4
Brief Description: The user gives the System an amount to deposit into their account (either cash or cheque through the deposit slot)
Actors: Account Holder, System, Database
Triggers: When the Account Holder selects ‘Deposit’ from the main menu
Flow of Events:
Basic Flow – Deposit:
The use case starts when the user selects ‘Deposit’ from the main menu
The system prompts the user to enter the amount they wish to deposit
The user enters the amount to deposit
While the System is waiting for the deposit to be put into the deposit slot
4.1 The System prompts the Account Holder to put in their cash or cheque via envelope
The System updates the active Account’s balance on database
Alternative Flow:
User presses ‘Exit’ button (UC 3.2.4 Exit)
User presses ’Return’ button (UC 3.2.5 Return)
Special Requirements: None
Preconditions: Application must be running, account must be logged in, the user selects the ‘Deposit’ button on the main menu
Postconditions:
Success Postconditions:
1. The Account receives the deposit successfully
Failure Postconditions:
1. The deposit is not completed
Extension Points: none

3.2.12 PrintReceipt

UC #12 PrintReceipt.pdf

3.2.12 PrintReceipt
Priority: 3
Brief Description: Will print receipt with all transaction done on it.
Actors: System, Database
Triggers: When the Account Holder decides to have a receipt printed
Flow of Events:
Basic Flow – Print Receipt:

1. The Use Case starts when the user has decided to have a printed receipt.
2. System checks for sufficient paper to print receipt.
3. If there is enough paper to print receipt.
   3.1. Print receipt and the return to UC 3.2.4 Exit.
4. Else show prompt saying “Sorry but there is not enough paper to print a receipt at this time. Please excuse this inconvenience.”
5. Return to UC 3.2.4 Exit.
   Alternative Flow: None
   Special Requirements: None
   Preconditions: Application must be running, account must be logged in, transactions must have been made
   Postconditions:
   Success Postconditions:
   1. Receipt will have been printed with all transactions done this session
      Failure Postconditions:
   2. Display error
      Extension Points: none

3.2.10 DispenseMoney

UC #10 DispenseMoney.pdf

3.2.10 DispenseMoney (included in UC 3.2.8 Withdraw)
Priority: 2
Brief Description: The System dispenses the money through the money dispenser
Actors: Account Holder, System, Bank Database
Triggers: Verified withdrawal amount passed
Flow of Events:
Basic Flow – Dispense Money:
1. The use case starts when the System receives the amount to be dispensed from (UC 3.2.8 Step #6)
2. If the System does not have sufficient cash money
2.1 Display error message “Sorry, this machine is out of money.”
2.2 Return to UC 3.1.7
3. The System gets the required amount of money
4. The System dispenses the money through the money dispenser
5. While the money has not been removed from the dispenser
5.1. The System displays a remove money message
Alternative Flow:
1. User presses ‘exit’ button (UC 3.2.4 Exit)
Special Requirements: None
Preconditions: Application must be running, account must be logged in, withdrawal amount must be confirmed and passed
Postconditions:
Success Postconditions:
1. The selected amount of money is dispensed
Failure Postconditions:
1. The selected amount of money cannot be dispensed
Extension Points: none

3.2.5. Return

UC #5 Return.pdf

3.2.5. Return
Priority: 2
Brief Description: Goes back to the previous page
Actors: System
Triggers: When the user presses the ‘Return’ key on screen.
Flow of Events:
Basic Flow – Return:

1. Go to previous page
   Alternative Flow: None
   Special Requirements: None
   Preconditions: Application must be running
   Postconditions:
   Success Postconditions:
   1. Have returned to previous page.
      Failure Postconditions:
   2. Fails to return to previous page.
      Extension Points: none
      

3.2.7. ViewBalance

UC #7 ViewBalance.pdf

3.2.7. ViewBalance
Priority: 2
Brief Description: Fetches balance from database and displays it on screen
Actors: System, Database
Triggers: Account Holder request account balance
Flow of Events:
Basic Flow - View Balance:
1. Request Account balance from database
2. Display Account balance.
Alternative Flow:
1. User presses ‘exit’ button (UC 3.2.4 Exit)
Special Requirements: none
Preconditions: Application must be running, account must be logged in
Postconditions:
Success Postconditions:
1. Account balance is displayed
Failure Postconditions:
1. Account balance is not displayed
Extension Points: none

3.2.8. Withdraw

UC #8 Withdraw.pdf

3.2.8. Withdraw (include UC 3.2.9 CheckAvailableFunds and UC 3.2.10 DispenseMoney)
Priority: 1
Brief Description: The Account Holder withdraws a specific amount from their account
Actors: Account Holder, System, Database
Triggers: Selecting ‘Withdraw’ from the main menu
Flow of Events:
Basic Flow – Withdraw:
1. The use case starts when Account Holder selects the ‘withdraw’ button on the main menu
2. The System displays a window with predetermined amounts to withdraw and an option to input a custom amount (must be a multiple of 20)
3. If a custom amount is entered and ‘enter’ is pushed
3.1. While the amount is not divisible by 20
3.1.1. Display an invalid input message
3.1.2. Clear the amount in the textbox
3.2 Continue with custom amount.
4. Else if the account holder selects a predetermined amount to withdraw
4.1 Continue with the predetermined value
5. Include (UC 3.1.9 CheckAvailableFunds)
6. Access database and withdraw the funds.
7. Include (UC 3.1.10 DispenseMoney)
8. The balance is decreased by amount selected/inputted through database
Alternative Flow:
1. User presses ‘exit’ button (UC 3.1.4 Exit)
2. User presses ‘return’ button (UC 3.1.5 Return)

Special Requirements: None
Preconditions: Application must be running, account must be logged in
Postconditions:
Success Postconditions:
1. The selected amount of money is withdrawn and the balance is updated
Failure Postconditions:
1. The selected amount of money cannot be withdrawn

Extension Points: none

3.2.6. ViewMainMenu

UC #6 ViewMainMenu.pdf

3.2.6. ViewMainMenu
Priority: 1
Brief Description: Displays the main menu of options for the Account Holder
Actors: Account Holder, System
Triggers: Successful login, Account Holder selects to do another transaction
Flow of Events:
Basic Flow – View MainMenu:
1. The use case starts when one of the triggers occur
2. The system displays the main menu of option buttons
3. The system waits until the Account Holder selects one of the buttons (Withdraw, Deposit, View Balance, Exit)
4. The system calls the selected button’s function
Alternative Flow:
1. User presses ‘exit’ button (UC 3.2.4 Exit)
Special Requirements: None
Preconditions: Application must be running, Account must be logged in
Postconditions:
Success Postconditions:
1. Main menu is displayed and usable
Failure Postconditions:
1. Main menu is not displayed
Extension Points: none

3.2.11 CheckReceipt

UC #11 CheckReceipt.pdf

3.2.11 CheckReceipt
Priority: 3
Brief Description: Asks the Account Holder if they would like a receipt of their previous transactions
Actors: Account Holder, System, Database
Triggers: When the Account Holder decided to Exit or stop using the ATM
Flow of Events:
Basic Flow – Check for a Receipt:
The use case starts when the user has decided to exit the system and ATM
The System asks the Account Holder if they would like a printed receipt.
If Account holder says yes
3.1. Extension Point (UC 3.2.12 PrintReceipt)
4. Exit use case and return to (UC 3.2.4 Exit)
Alternative Flow: None
Special Requirements: None
Preconditions: Application must be running, account must be logged in
Postconditions:
Success Postconditions:
1. Receipt will be printed.
Failure Postconditions:
1. DIsplay error
Extension Points: none


3.2.9. CheckAvailableFunds

UC #9 CheckAvailableFunds.pdf

3.2.9. CheckAvailableFunds (included in UC 3.2.8 Withdraw)
Priority: 2
Brief Description: The System checks if the selected amount to be withdrawn is within the account’s balance
Actors: System, Database
Triggers: Withdraw amount selected
Flow of Events:
Basic Flow – Check Available Funds:
1. The use case starts when the System receives the amount to be withdrawn from (UC 3.2.8 Step #5)
2. The System gets the active account’s balance
3. If the withdraw amount is greater than the account’s balance
3.1 Display error message “withdraw amount exceeds balance”
3.2 Return to (UC 3.2.8 Step #2)
4. Return to (UC 3.2.8 Step #6)
Alternative Flow: None
Special Requirements: None
Preconditions: Application must be running, account must be logged in, withdrawal amount must be selected and passed
Postconditions:
Success Postconditions:
1. The selected amount of money is confirmed available to be withdrawn
Failure Postconditions:
1. The selected amount of money cannot be withdrawn
Extension Points: none

3.2.1 Login

UC #1 Login.pdf

3.2.1 Login (include UC 3.2.2 ValidateAccountNumber and UC 3.2.3 ValidatePin)
Priority: 1
Brief Description: The user inputs login information and the system checks validity
Actors: Account Holder, System
Triggers: Inserting Card, NFC Card, Entering Account Number
Flow of Events:
Basic Flow – Login:

1. The use case starts when the user provides an account number
2. Include (UC 3.2.2 ValidateAccountNumber)
3. While System does not validate account number.
   3.1. Prompt to user that the account does not exist.
   3.2. User must input a new number to be checked.
   3.3. Include (UC 3.2.2 ValidateAccountNumber)
4. Else Switch to PIN entering window
5. Include (UC 3.2.3 ValidatePIN)
6. While System does not validate account PIN and tries are less than 3.
   6.1. Prompt to user that the account PIN is invalid.
   6.2. User must input a new PIN to be checked.
   6.3. Include (UC 3.2.3 ValidatePin)
   Alternative Flow:
7. User presses ‘exit’ button (UC 3.2.4 Exit)
   Special Requirements: The card number has to be 16 digits; PIN must be 4 digits long
   Preconditions: Application must be running
   Postconditions:
   Success Postconditions:
8. Account is verified and open to ATM specific actions.
   Failure Postconditions:
9. Account is not verified, therefore system goes back to log in.
   Extension Points: none

3.2.13 CheckMoreTransactions

UC #13 CheckMoreTransactions.pdf

3.2.13 CheckMoreTransactions
Priority: 3
Brief Description: The System checks if the Account Holder wants to do another transaction after completing a transaction
Actors: Account Holder, System, Database
Triggers: After a transaction completes
Flow of Events:
Basic Flow – Check for a Receipt:

1. The Use Case starts when a transaction completes
2. The system asks the Account Holder whether or not they want to do another transaction
3. If the Account Holder selects ‘Yes’
   3.1. Return to (UC 3.2.6 ViewMainMenu)
4. Else
   4.1. Go to (UC 3.2.4 Exit)
   Alternative Flow: None
   Special Requirements: None
   Preconditions: A transaction has been completed successfully
   Postconditions:
   Success Postconditions:
   1. System returns to main menu or exits
      Failure Postconditions:
   2. Display error
      Extension Points: none

3.2.3. ValidatePin

UC #3 ValidatePIN.pdf

3.2.3. ValidatePin
Priority: 1
Brief Description: System validates the inputted PIN by checking the database for correct a corresponding PIN number.
Actors: System, Database
Triggers: Customer has inputted a PIN number to be validated and attempts to log in.
Flow of Events:
Basic Flow – Validate Pin:

1. The Use Case starts when the system has received a 4 digit PIN number to be validated.
2. System compares inputted 4 digit PIN number corresponding to PIN stored within the 16 digit account number.
   3. If inputted PIN is equal to account’s stored pin
   3.1 Exit Use Case and return to Login menu indicating a successful validation.
   4. Else inputted PIN is not equal to account’s stored PIN
   4.1 Exit Use Case and return to Login menu indicating a failed validation.
   Alternative Flow: None
   Special Requirements: None
   Preconditions: Application must be running and account number must be validated.
   Postconditions:
   Success Postconditions:
   1. Account is verified and open to ATM specific actions.
      Failure Postconditions:
   2. Account is not verified, therefore system goes back to log in.
      Extension Points: none

3.2.4. Exit

UC #4 Exit.pdf

3.2.4. Exit
Priority: 1
Brief Description: Exits the application
Actors: System
Triggers: Pressing the ‘exit’ button
Flow of Events:
Basic Flow – View MainMenu:
The use case starts when account holder presses the ‘exit’ button
Prompt asking, “ Would you like to exit ATM now?”
If user selects “No”
3.1 return to previous screen
System checks if transactions have been made
4.1 if a transaction have been made, Extension point (UC 3.1.11 CheckReceipt)
System switches to a new window
The new window prints “Thank you for banking with RBI”
The application exits
Alternative Flow: None
Special Requirements: None
Preconditions: Application must be running
Postconditions:
Success Postconditions:
1. Application exits
Failure Postconditions:
1. Application does not exit

Extension Points: none