UML Diagram for Bank Management System – Part I

UML Diagrams for Bank Management System

[Migrated from my old blog Kaybots]

(Mini-project)

By G.SHAKIR

Use Case Modeling

Use Case diagram for Banking System:

1. Online Transaction – use case specifications

1.1 Brief Description

Account transaction begins when customer is successfully logged in to the site. Several menus where displayed related to profile of customer and the recent transactions and the current account balance.

The main purpose of using online account transactions is to transfer cash from one account to another for this purpose the customer is provided fields to specify the accounts to which he is transferring amount. After every transaction a confirmation is displayed to customer.

The customer is also provided the possibility to change the account login password, but not the user id, every transaction is added to the bank database.

Flow of Events

1.2 Basic flow

1. User enters username and password.

2. Bank Database validates the user.

3. On success user can transfer money, change his password and view his profile.

1.3 Alternate Flow

If in the basic flow, the details specified by user are invalid then he is informed that his login is failed .Then the user may quit the system or he may create a new account.

1.4 Pre Conditions

The user should have a valid account in the bank.

1.5 Post Conditions

The account database is modified after transaction.

2. Client Desktop transaction- Use case specifications

2.1 Brief Description

Client desktop is given to each of bank employees and they are provided with account logins with a user id and a password. Every employee switches on his desktop and login to his account through which he can communicate with bank database.

An employee can have operations like withdrawal of money, giving loans, furnishing the DD/cheque and customers may want to deposit money.

Bank employee is allowed to modify the database accordingly. And the intended services are provided to the customers.

Flow of Events

2.2 Basic flow

1. Employee enters his username and password.

2. Bank Database validates the employee.

3. On success employee can withdraw or deposit money, issue loans and

DD/cheque to the customers.

2.3 Alternate Flow

If in the basic flow, the details specified by employee are invalid the he is informed that his login is failed .Then the person is not employee of the bank and he is not having authority to perform those actions.

2.4 Pre Conditions

The employee must possess a account login and password.

2.5 Post Conditions

The account database is modified after transaction. Employee issues dd/cheque to user.

3. Login- Use case specifications

3.1 Brief Description

The online customer or a bank employee has to login to access their accounts from bank database. A vendor is provided for communication with bank’s database and this vendor provides safety and atomicity. A user may be an invalid user so the system has to prompt the person appropriately.

Flow of Events

3.2 Basic flow

1. User enters username and password.

2. Bank Database validates the user.

3. On success user can precede the transaction.

3.3 Alternate Flow

If in the basic flow, the details specified by user are invalid the he is informed that his login is failed.

3.4 Pre Conditions

The user must possess a login id and password.

3.5 Post Conditions

None.

Continue to UML Diagram for Bank Management System – Part II