Bank Management Project Report

7/29/2019 Bank Management Project Report

1/28

BANK MANAGEMENT

Use Case ModelingUse Case diagram for Banking System:


2/28

System

u s e r

a t m t r a n s a c t io np i n v a l id a t i o n

i n v a l id p i n

i n s e r t c a r d

B a n k D a t a b

o n l in e t r a n s a c t i o n

lo g in l o g o u t

i n v a l id l o g i n

a n k e m p lo y e e

c l ie n t d e s k t o p t r a n s a c t i o n

t r a n s a c t i o n

r e t a i l i n s t i t u

i n v a l id c a r d

w e b m e r c ha n t

1. Online Transaction - use case specifications

1.1 Brief Description


3/28

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

The main purpose of using online account transactions is to transfer cashfrom one account to another for this purpose the customer is provided fieldsto specify the accounts to which he is transferring amount. After everytransaction 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 informedthat his login is failed .Then the user may quit the system or he may create a newaccount.

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



4/28

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

An employee can have operations like withdrawal of money, givingloans, furnishing the DD/cheque and customers may want to deposit money.Bank employee is allowed to modify the database accordingly. And theintended 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 isinformed that his login is failed .Then the person is not employee of the bank and heis 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



5/28

The online customer or a bank employee has to login to access their accounts from bank database. A vendor is provided for communication with

banks 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 informedthat his login is failed.

3.4 Pre Conditions

The user must possess a login id and password.

3.5 Post Conditions

None.

4. Logout- Use case specifications



6/28

The person who ever logged in to the system or bank database has to logoutafter all the work is over. The vendor provided for communication is nowclosed from database.

Flow of Events 4.2 Basic flow

1. User clicks the logout2. All the transactions he performed are reflected in the bank database.

4.3 Alternate FlowIf 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



7/28

If a person with a invalid user id or password details want login to thesystem, the system has to prompt the person about failure and should notopen 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



8/28

Card transaction includes a credit/debit card. This service is provided by aretail institution to a card holding customer. The customer may want to buyany thing form merchant, customer provides the card and the merchantstripes the card into the card reader then it is checked for validity and if thecard is valid the transaction begins. A credit card will have a credit amountyou can deduct amount more than that. A debit card will be having somelevel 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 dont havesufficient 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


9/28


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 validtransaction continues. And then pin validation is done; if the pin is invalidthe transaction is doesnt allowed. The customer may have transactions likechecking balance, draw amount and donation. If there are less funds thetransaction 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 inresponse 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



10/28

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

Flow of Events

8.2 Basic flow

1. Customer inserts card in ATM or Card reader 2. ATM or Card reader validates the card.3. On success user can precede the transaction

8.3 Alternate Flow

If the card is invalid, ATM ejects the card or then it may be taken back fromCard reader and gives a receipt indicating the error number.

8.4 Pre Conditions

The User must possess an ATM card or else a debit/credit card.

8.5 Post Conditions

None.

9. Invalid card - Use case specifications



11/28

The card inserted will be checked for validation. The card may not beinserted properly or it may be out of date or it can be an invalid for specific

bank. In those situations it is requested for re-insert.

Flow of Events

9.2 Basic flow

1. Customer inserts card in ATM or swipes in Card reader.2. ATM (Card reader) validates the card is invalid.3. Customer must re-insert (swipe) the card again.

9.3 Alternate Flow

Even after reinserting the card, if the card is invalid ATM (Card reader) gives areceipt indicating that the card is invalid. 9.4 Pre Conditions

The User must possess an ATM card or a credit/debit card.

9.5 Post Conditions

None.

10. Pin validation - Use case specifications



12/28

After inserting the card and if it is checked for validation, the user isrequested for pin. The pin is itself present on magnetic strip on back of card andit is checked with the entered one. Flow of Events

10.2 Basic flow

1. Customer inserts card in ATM and enter his pin number.2. ATM validates the pin.3. On success user can precede the transaction

10.3 Alternate Flow

If the pin is invalid, ATM ejects the card and gives a receipt indicatingthe error number.

10.4 Pre Conditions

The User must possess an ATM card.

10.5 Post Conditions

None.

11. Invalid Pin - Use case specifications



13/28

The pin entered may be wrong in that case transaction is cancelled. Thecustomer is requested for re-inserting of card and re-entry of pin. Thenumber of wrong trials may be limited according to banks specifications.

Flow of Events

11.2 Basic flow

1. Customer inserts card in ATM and enter his pin number.2. ATM founds that pin is invalid.3. The customer requested to reinsert card or reenter the pin.4. In case the number of trials exceeded, ATM blocks the card temporarily.

11.3 Alternate Flow

If customer enters a correct pin transaction proceeds further.

11.4 Pre Conditions

The User must possess an ATM card.

11.5 Post Conditions

The user should not enter the pin number more than the number of trials.

Class Diagram for Banking System:


14/28

credit

+amount

+feasibility()

debit

+amount

+feasibility()

card va l idat ion

+accno

+validity()

pin va l idat ion

+pin

+validity()

check bal

+balance

donat ion

+amount

+feasibility()

draw amount

+amount

+feasibility()

funds

+balance

A TM

+choice

+processrequest()

card reader

+cardholder+cnctwithDB

+turnon()+turnoff()

bank web page

+bankdetails+loginform

+processrequest()

login

+id+pswrd

+validity()

logout

+logout()

t ransfer o f amount

+amount+toaccno

+feasibility()

cl ien t desk t op

+frontend+cnctwithDB

+turnon()+shutdwn()

withdrawl

+accno+amount

+feasible()+drawamnt()

loan

+amount

+feasibility()

DD/cheque

+amount

+dispensecash()

deposi t

+amount+accno

+transfercash()

custome r conso le

+card+pin

+request()

b an k d a t ab ase

+profile+log+balance

+procesesrequest()

re ta i l ins t i tu it ion

+amountadded

+process()

employe e conso le

+id&pswrd

n e t wo rk t o b an k

+profile+balance+log

+request()

1

0..*

1

0..*1

0..*1

0..*

1 1

1

1

1

11

11

0..*

1

0..* 1

0..*

1

0..*

11

1 1

10..*

1

0..*

1..* 1

11

11

1

0..*

1

0..*.*

Sequence Diagramsand


15/28

Collaboration Diagrams

Online Transaction Sequence Diagram:

customer console network to bank

transaction

1 : loginRequest()2 : validity()

3 : profileRequest()

4 : display()

5 : transferRequest()

6 : transfer()

7 : succed()

8 : acknowledgement()

9 : transferRequest()

online transactionsequence diagram

Online Transaction Collaboration Diagram:


16/28

customer console network to bank

transaction

1 : login request()

2 : validity()3 : profile request()

4 : display()

5 : transfer request()

6 : transfer()

7 : succeed()

8 : acknowledgement()

9 : transfer request()

Client desktop Transaction Sequence Diagram:

transaction

network to bank databaseemployee console

1 : login request()2 : validity()

3 : menuChoice()

4 : p roceedTransaction()

5 : accountInfo()

6 : succed()

7 : menuChoice()

8 : proceedTransaction( )

client desktop transactionsequence diagram

Client desktop Transaction Collaboration Diagram:


17/28

employee console netwrk to bank db

transaction

1 : login request()

2 : validity()

3 : choice menu()

4 : proceed transaction()5 : account info()

6 : succeed()

7 : choice menu()

8 : transaction proceed()

Login & Logout Sequence Diagram:

desktop front end network to bank

1 : enterId&Pswrd()

2 : verify()

3 : validity()

4 : logout() 5 : reqLogout()

6 : succeded()7 : loggedout()

login & logoutsequence diagram


18/28

Login & Logout Collaboration Diagram:

desktop front end network to bank 1 : enter id pwd()2 : verify()

3 : validity()

4 : logout() 5 : request logout()

6 : succeeded()7 : logged out()

ATM Transaction Sequence Diagram:

customer console

transactionntwrk to bank

1 : insert card()

2 : validation()

3 : verified()

4 : ChoiceMenu()

5 : selectservice()

6 : accountInfo()7 : feasibility()

8 : give receipt()

9 : another transaction()

ATM transactionsequence diagram

ATM Transaction Collaboration Diagram:


19/28

customer console ntwrk to bank

transaction

1 : insert card()

2 : validation()

3 : verified()

4 : choice menu()

5 : select serv ice()

6 : account info()

7 : feasibility()

8 : give receipt()9 : another trans()

Card Validation Sequence Diagram:

customer panel atm network to bank

1 : insert card()2 : validation()

3 : card valid()

4 : eject card()

card validationsequence diagram


20/28

Card Validation Collaboration Diagram:

customer panel atm bank network

1 : insert card() 2 : validation()

3 : card valid()4 : eject card()

Pin Validation Sequence Diagram:

atm network to bank customer panel

1 : enterpin()

2 : pin validation()

3 : validity()4 : choiceMenu()

pin validationsequence diagram

Pin Validation Collaboration Diagram:


21/28

customer panel atm bank network 1 : enter pin() 2 : pin validation()

3 : validity()4 : choice menu()

Web merchant Transaction Sequence Diagram:

retailer card reader network to bank customer

1 : gives card()

2 : insert card()

3 : validation()

4 : verified()

Web merchant t ransactionsequence digram

5 : enter amount()

6 : update bank db()

7 : give receipt()

Web merchant Transaction Collaboration Diagram:


22/28

customer retailer card reader

bank network

1 : give card() 2 : insert card()

3 : validation()

4 : v erified()

5 : enter amount()

6 : update bank DB()

7 : give receipt()

Activity Diagrams


23/28

Online Transaction Activity Diagram:

open web page

create account enter id and pwd

furnish details

submit

choice menu

amount transfer view details change pwd

finished

valid details

valid login

yes

yes

no

no

Client Desktop Transaction Activity Diagram:


24/28


25/28

customer approaches officer

employee login

choice menu

deposit withdraw issue dd/cheque

passbook entry

proceed transaction

no

yes

valid login

Web Merchant Transaction Activity Diagram:


26/28

insert card

enter amount

proceed transaction

take receipt

finish

sufficient bal

yes

no

card valid

yes

no

Component Diagram for Banking System:


27/28

c u s t o m e r c o n s o le AT M m a c h in e

C a r d r e a d e r

C li e n t d e s k t o pWe b p a g e

B a n k D a t a b a s e

Em p l o y e e c o n s o l e

o n l in e t r a n s a c t i o n c l ie n t d e s k t o p t r a n s a c t i o n

AT M t r a n s a c t io n

w e b m e r c h a n t t r a n s a c t r io n

A c c o u n t i n fo

Deployment Diagram for Banking System:


28/28

Customer Conso le

Bank Databa seCard Reader

Emp loye e Consoleeb Page

Clien t Desk to p

ATM Machine

ATM Machineproviding services of

ATM transaction

Web Pageproviding services of online transaction

Client Desktopproviding services of banking at desks

Bank Databasekeeping the details of each and every account

Card readerproviding services of credit/debit tranmsaction

Customer may be ATM card holder,credit/debit card holder oran online user of a Bank

Each employee atBank given a desktopand provided with ownid & password for login tothe Bank's Database

Documents

Bank Management Project Report