Banking services

Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Terminologies
2. Overall description
2.1 Product perspective
2.2 Hardware interface
2.3 User interfaces
2.4 User Characteristics
2.4 Operating environment
2.5 Hard ware specification
3. Specific requirements
3.1 The gist of the software is as follows:
3.2 Functional Requirement:
3.3 Non-Functional Requirement
4. References
5. Designs
5.1 Use case diagram
5.2 Class Diagram
5.3 Object Diagram
5.4 Interaction Diagram
4.4.1 Sequence Diagram
4.5.2 Collaboration Diagram
5.6 State Diagram
5.7 Activity Diagram
5.8 Implementation Diagram
4.8.1 Component Diagram
4.8.2 Deployment Diagram

INTRODUCTION:
Banking has no doubt reached even the most remote corners of the
country. The move from manual system to a computerized one
resulted in a major overhaul of the overall infrastructure of a bank.
No longer did the customer have to wait in long queues for his work
to be finished. With the computerization of banks it became easy to
manage people’s accounts and their overall finances. Never before
has withdrawing money or transferring money from one account to
another or even applying for a loan been so easy. Creating a new
account is now so easy that gone are the days when people had to
wait in those queues which seemed never ending .By going the
digital way “THE VIT BANK”, guarantees your banking experience
will forever be revolutionized.

1.1 Purpose

The purpose of this project is to ease the process of transaction as

well as to reduce the manual work.

1.2 Scope

The software supports a computerized banking called VitBank. The

software enables banker to complete simple bank account services
via user id and password provided by the bank.
The Bank Application identifies a customer by account number. It
collects information about a simple account transaction (e.g.,
deposit, withdrawal, transfer, Transfer money), communicates the
transaction information to the customer’s bank, and dispenses cash
to the customer. The banks provide their own software for their own
computers. The VitBank software requires appropriate record
keeping and security provisions. The software must handle
concurrent accesses to the same account correctly.
1.3 Definitions, abbreviations

Definition:
Account:
 A single account at a bank against which transactions can be
applied. Accounts may be of various types with at least
checking and savings. A customer can hold more than one
account and a account can be held by more than on customer.

Terminologies:
 Debit/Debtor: Account in which money comes in/The
person who receives the benefits
 Credit/Creditor: Account from which money goes out/The
person who gives the benefits
 Passbook: Record of Various transactions that have taken
place in the account
 Draft: Can be called as temporary cash.
 maxDailyWD: The maximum amount of cash that a
customer can withdraw from an account in a day (from
00:00 AM to 23:59 PM) via check.
2. Overall description
2.1 Product Perspective
VIT BANK is aimed toward making a computerized banking solution for
the staff of bank. VIT BANK should be user-friendly, ‘quick to learn’ and
reliable software for the above purpose.
2.2 Hardware interface
The software will run on a personal computer connected via LAN in
bank.
2.3 User interfaces
The customer user interface should be intuitive, such that 99.9% of
all new banker are able to complete customer banking transactions
without any assistance.
2.4 User Characteristics
There are two users:
1. Customers are simply members of the general public with no
special training.
2. Banker need have no special education or experience.
The staff in following departments manages the software.
o Accounts Department
o Loans Department
o Customer Service Department
o Collection Department
2.4 Operating environment
Asp.net, office, windows 2003 or XP
2.5 Hard ware specification:
80 GB HDD, 1 GB RAM, 2.1 GHz processor, LAN.
3. Specific requirements
3.1 The gist of the software is as follows:
 A person can either be an existing customer and if not he can
simply open a new account.
 Once the person becomes a customer of “THE VIT BANK” he
is given an account number and pin code.
 The account balance can be checked
 If the person wants to deposit money, it can be done either by
cheque or cash.
 Five recent transaction statement or all transaction statement
can be shown.
3.2 Functional Requirement:
A Banker should be able to
 Create a new Account
 Login for doing transaction
 Change account details
 Check customer balance
 To see and print customer account statement.
  Withdraw money
 Deposit Money
 Stop Check Payment
3.3 Non-Functional Requirement
• The lag between user request and software output should be
less than 5 seconds for minor operations(eg check balance
etc) and Not more than 10 seconds for major operations like
withdraw deposit etc
• The Software shall be available 100% of the time during
working hours, with no period of downtime or inconsistency.
• VIT bank should be fault tolerant. Data should not become
corrupted in case of system crash or power failure.
• The files in which the information regarding securities and
portfolios should be secured against malicious deformations.
5. References

• Booch, Jacobson, Rumbagh, “The UML user Guide”, Pearson

Education.
• Object oriented analysis and design with applications by Gready
Booch
 U s e C a s e D ia g r a m fo r V IT B A N K

< < e x te n d > > < < e x te n d > > G e n e ra t e U n iq u e Id

R e g is t ra t io n o f c u s to m e r

< < e x te n d > >

L o g in
< < e x te n d > >

W it h d ra w M o n e y In s u ffic ie n t A m o u n t

B ank er
< < e x te n d > >
< < e x te n d > >
D e p o s it m o n e y

< < e x te n d > >

Tra n s fe r

c lo s in g a c c o u n t
 C la s s D ia g r a m f o r V IT B A N K

A ccount 1 ..*
T ra n s L o g
0 ..*
A cc no Cnam e
B a la n c e A ccno
C u s to m e 0r1. . * T ra n s T y p e
nam e e n q u iry () D ate
A d re s s A va ila b le ()
t e ln o E n t e r A c c o u n t N o ()
1 1
p u td a t a () B ank
g e td a t a () nam e
G ive m o n e y () B ra n c h

g e t d a t a ()
p u t d a t a ()

1
CB anker
S a vin g s C u r re n t
nam e
ID In t e re s t O ve d ra f a m o u n t
P asswd
D e p o s it () D e p o s it ()
g e t d a t a () W it h d ra w () W it h d ra w ()
p u t d a t a () T ra n s fe r() T ra n s fe r()
L o g in ()
 O b je c t D ia g r a m fo r V IT B A N K

C 1 :C u s t o m e r
C 1 .n a m e = " X Y Z " A 1 :A c c o u n t
C 1 .a d r e s s = " w a d a l a " A 1 .A c c n o = 1 2 3
C 1 .te l n o = 9 9 2 3 3 4 2 A 1 .B a l a n c e = 5 0 0 0

B 1 :B a n k
B 1 .n a m e = " V IT B a n k "
B 1 .B r a n c h = " W a d a la "

T 1 :T ra n s L o g
B K 1 :B a n k e r
T 1 .C n a m e = " X Y Z "
B K 1 .n a m e = " A B C " T 1 .A c c n o = 1 2 3
B K 1 . ID = B 1 2 1 T 1 .T r a n s T y p e = D e p o s i t
T 1 .D a te = 2 3 / 1 0 /1 0
 S e qu e n ce D iagram for W ith draw

Cus tom er : B ank er : A c c ount : Databas e : DB TLog :

C us tom er B ank er1 A c c ount T1:TransLog
Reques t for withdraw

E nter A c count N o( )
Chec k balanc e( )
A vailable( )

Deduc t m oney ( )

Create Log( )

G ive Cas h
 C o lla boratio n D iagram fo r W ith draw

Cus tom er :
Cus tom er

7: Give Cash TLog :

T1:Trans Log

Databas e : 1: Request for withdraw

DB

B ank er :
B ank er1

3: Chec k balanc e( )
5: Deduc t m oney( )

2: E nter A c c ount No( )

6: Create Log( )
4: A vailable( )

A c c ount :
A c c ount
 S ta te C h a rt D ia g r a m fo r W ith d ra w

F ill R e g form
C los e R e q u e s t to c lo s e Id le O pen

R e q u e s t Tra n s a c tion
F in is h tra n s a c tio n

A c t ive
 Ba nk e r A c c ou nt

A ctiv ity D ia gram for W ith draw

L ogin

Se lect Withdra w
Option

NO s ucces s

YES

Enter Am ount

checkMinim un B Che ckSufficie nt

alance Balance

No s ucces ful verified

NO

YES
YES

U pdate
Databa s e
 C o m p o n e n t D ia g r a m f o r V IT B A N K

A c c .vb
F rm D e p o
s it .vb

B a n k in g D ataB as e
GUI S e rvic e s . e x e

F rm Tra n s
F rm W ith d
a c t. vb
ra w .vb
D e p lo y m e n t D i a g r a m f o r V I T B A N K

< < D a ta B a s e > >

< < S e rve r> >

B a n k .m d b

B a n k in g S o lu ti o n .s ln

c ls D a ta .c l a s s

h e lp .d o c

< < c lie n t1 > > < < c lie n t2 > > C l ie n t3 > >

GUI
GUI GU I