UML Diagram for Bank Management System – Part II

Continued from UML Diagram for Bank Management System – Part I

4. Logout- Use case specifications

4.1 Brief Description

The person who ever logged in to the system or bank database has to logout after all the work is over. The vendor provided for communication is now closed from database.

Flow of Events

4.2 Basic flow

1. User clicks the logout

2. All the transactions he performed are reflected in the bank database.

4.3 Alternate Flow

If in the basic flow, if the internet connection is lost user must refresh the page again.

4.4 Pre Conditions

The user should have been logged in already.

4.5 Post Conditions

None.

5. Invalid Login- Use case specifications

5.1 Brief Description

If a person with a invalid user id or password details want login to the system, the system has to prompt the person about failure and should not open the vendor of communication until he furnishes valid user id & password.

Flow of Events

5.2 Basic flow

1. User enters username and password.

2. Bank Database validates that the login is invalid.

3. Further he may not be allowed to proceed until enters a valid login.

5.3 Alternate Flow

1. If the user enters a valid login he must be allowed to proceed further.

5.4 Pre Conditions

None.

5.5 Post Conditions

None.

6. Card transaction – Use case specifications

6.1 Brief Description

Card transaction includes a credit/debit card. This service is provided by a retail institution to a card holding customer. The customer may want to buy any thing form merchant, customer provides the card and the merchant stripes the card into the card reader then it is checked for validity and if the card is valid the transaction begins. A credit card will have a credit amount you can deduct amount more than that. A debit card will be having some level of funds if the funds are over the transaction will not continue.

Flow of Events

6.2 Basic flow

1. The retailer places the card in card reader.

2. Card reader checks the card validity after that retailer asks the customer

to enter pin number.

3. After entering the pin number retailer enters amount to be paid by customer.

4. Card reader proceeds transaction after that it updates bank Database

and finally gives a receipt to customer.

6.3 Alternate Flow

If in the basic flow, if the card or pin is invalid or the account don’t have sufficient balance the card reader ejects the card out by giving a receipt.

6.4 Pre Conditions

The User must possess a debit/credit card.

6.5 Post Conditions

The user has to sign in the receipt and put a copy of receipt with him for security reasons.

7. ATM transaction- Use case specifications

7.1 Brief Description

If a customer approaches an ATM, the person is requested to insert card. After inserting the card it is checked for validity if the card is valid transaction continues. And then pin validation is done; if the pin is invalid the transaction is doesn’t allowed. The customer may have transactions like checking balance, draw amount and donation. If there are less funds the transaction is sustained.

Flow of Events

7.2 Basic flow

1. User inserts card in ATM.

2. Bank Database validates the card.

3. On success employee must enter pin and select from his list of services

appeared on the screen.

7.3 Alternate Flow

If in the basic flow, the card or pin is invalid a receipt ejects out from ATM in response to the error.

7.4 Pre Conditions

The User must possess an ATM card

7.5 Post Conditions

The user must take the receipt.

8. Insert card – Use case specifications

8.1 Brief Description

The customer is requested to insert (swipe) card and the card is taken in and kept inside for the whole transaction time. Once the transaction is over card is spelled out.

Continue to UML Diagram for Bank Management System – Part III