INSTITUTE FOR ADVANCED COMPUTING

AND
SOFTWARE DEVELOPMENT
AKURDI, PUNE

Documentation On

“ONLINE BANKING SYSTEM”

PG-DAC Feb-2019

Submitted By :
Group No: 91
Amol Kedar (1119)
Hanmant Chavan(1142)

Prashant Karhale Mr. Kashinath Patil

Centre Coordinator Project Guide

1
 Table of
Contents
1) Introduction -------------------------------------------------------------------3
1.1)Purpose----------------------------------------------------------------------------------------3
1.2)Scope------------------------------------------------------------------------------------------3
1.3)Definitions, Acronyms and Abbreviations-------------------------------------------4
1.4)References------------------------------------------------------------------------------------5
1.5)Technologies to be used----------------------------------------------------------------6
1.6) Overview …………………………………………………………………………… 6
2) Overall Description: ................................................................................................ 6
2.1) Product Perspective: .................................................................................................... 7
2.2) Software Interface: ...................................................................................................... 8
2.3) Hardware Interface: ..................................................................................................... 8
2.4) Communication Interface: ........................................................................................... 8
2.5) Product Features: ........................................................................................................ 8
2.6) User Characteristics: ................................................................................................... 9
2.7) Design and Implementation Constraints: .................................................................... 9
2.8) Use-Case Model Survey: ............................................................................................. 9
2.9) Architecture diagram: ................................................................................................ 14
2.10) ER-Diagram:…. ........................................................................................................ 15
2.11) Assumptions and Dependencies: ................................................................................ 15
3) Specific Requirements: ......................................................................................... 16
3.1) Use-Case Reports: ..................................................................................................... 16
3.1.1) Activity Diagram for Login------------------------------------------------------------------------- 19
3.1.2)Activity Diagram for balance enquiry--------------------------------------------------------------- 21
3.1.3)Activity Diagram for funds transfer----------------------------------------------------------------- 24
3.1.4)Activity diagram for cheque book request---------------------------------------------------------- 25
3.1.5)Activity Diagram for Mini Statements-------------------------------------------------------------- 27
3.1.6)Activity Diagram for update profile --------------------------------------------------------------- 28
3.2) Supplementary Requirements: ...................................................................................... 29
3.3)Non Functional Requirement------------------------------------------------------------------- -31
4) Supporting Information: ………………………….…………………………….32
4.1) System in context: …………………………………………………………………………….32
4.2) DFD diagram ----------------------------------------------------------------------------------------------33
4.3) Class Diagram: ………………………………………………………………………………..34
5) Appendices: ……….……………………………….………...…………………… 35
5.1) Appendix B: References ………………………………………………………………………35

2
 5.1.1)Login Process sequence diagram,----------------------------------------------------------------------35
5.1.2)Balance Enquiry ------------------------------------------------------------------------------------------35
5.1.3)Fund Transfer----------------------------------------------------------------------------------------------36
5.1.4)Update Profile---------------------------------------------------------------------------------------------37
5.1.5)Check Book Request-------------------------------------------------------------------------------------38
5.1.6)Mini Statement--------------------------------------------------------------------------------------------38

6)Data Dictionary---------------------------------------------------------------------------------39
6.1)Table name User_Account -------------------------------------------------------------------------------------------39
6.2)Table name Customer------------------------------------------------------------------------------------------------- 39
6.3)Table name Primary_Account----------------------------------------------------------------------------------------39
6.4)Table name Fund_Transfer------------------------------------------------------------------------------------------- 39
7)Software Life Cycle Model -------------------------------------------------------------------40
8) Screen Shots-------------------------------------------------------------------------------------42
8.1)Login Page--------------------------------------------------------------------------------------------------------------42
8.2)Registration-------------------------------------------------------------------------------------------------------------43
8.3)Welcome page----------------------------------------------------------------------------------------------------------44
8.4)Deposit-------------------------------------------------------------------------------------------------------------------45
8.5)Withdraw----------------------------------------------------------------------------------------------------------------45
8.6)Money Transfer---------------------------------------------------------------------------------------------------------46
8.7)Check Balance-----------------------------------------------------------------------------------------------------------47
8.8)Mini Statement----------------------------------------------------------------------------------------------------------48

9)References-----------------------------------------------------------------------------------------49
10)Conclusion---------------------------------------------------------------------------------------50

3
1) Introduction
Online banking system provides is specifically developed for online banking for Balance Enquiry,
Funds Transfer to another account in the same bank, Request for cheque book/change of address/stop
payment of cheques, Mini statements (Viewing Monthly and annual statements).

1.1 Purpose
The Traditional way of maintaining details of a user in a bank was to enter the details and
record them. Every time the user need to perform some transactions he has to go to bank and perform
the necessary actions, which may not be so feasible all the time. It may be a hard-hitting task for the
users and the bankers too. The project gives real life understanding of Online banking and activities
performed by various roles in the supply chain. Here, we provide an automation for banking system
through Internet. Online banking system project captures activities performed by different roles in
real life banking which provides enhanced techniques for maintaining the required information up-
to-date, which results in efficiency. The project gives real life understanding of Online banking and
activities performed by various roles in the supply chain.

1.2 Scope
This Project investigates the entry threshold for providing a new transaction service channel
via the real options approach, where the entry threshold is established by using an Online banking
system designed for the use of normal users(individuals), Industrialists, Entrepreneurs, Educational
Institutions(Financial sections), Organizations and Academicians under transaction rate uncertainty.

Customer must have a valid User Id and password to login to the system
If a wrong password is given thrice in succession, that account will be locked and the
customer will not be able to use it. When an invalid password is entered a warning is given
to the user that his account is going to get locked.
After the valid user logs in he is shown the list of accounts he has with the bank.
On selecting the desired account he is taken to a page which shows the present balance in
that particular account number.

4
 User can request for the details of the last ‘n’ number of transactions that he has performed.
A report can also be taken of this.
User can make a funds transfer to another account in the same bank. User is provided with a
transaction password which is different from the login password.
User can transfer funds from his account to any other account with this bank. If the
transaction is successful a notification should appear to the customer, in case it is
unsuccessful, a proper message should be given to the customer as to why it failed. User
can request for cheque book/change of address/stop payment of cheque’s
User can view his monthly as well as annual statements. He can also take print out of the
same.
Generate reports at every section
Administrator can take a back up of the database for every instance that is happening,
periodically.
All users are authenticated to avail the services
FAQ section is also included for end users benefit.

1.3 Definitions, Acronyms and Abbreviations

Administrator: He is the super user who can add new customers into banking system, and
assigns corresponding username, password, account type and other details. When any customer
withdraws his account from the bank, he can delete their account and stop the transactions immediately.
He can generate different reports. He also takes the system backup.

Team Members (Customers): After logging in he can request for balance enquiry in his
account, Funds Transfer to another account in the same bank, Request for cheque book/change of
address/stop payment of cheques, Mini statements (Viewing Monthly and annual statements).

Industrialists, Entrepreneur, Organizations and academicians: These are

another type of customers. They will have extra information to be entered while logging in such
as organization Id and so on. They can also perform all the actions what the normal customers are
going to perform.

5
 HTML: Hypertext Markup Language is a markup language used to design static web
pages.

EJB: Enterprise Java Beans.

J2EE: Java 2 Enterprise Edition is a programming platform part of the Java Platform for
developing and running distributed multitier architecture Java applications, based largely on modular
software components running on an application server.

MYSQL: Mysql Database is the database management system that delivers a flexible and cost
effective database platform to build robust on demand business applications.

APACHE TOMCAT: Apache tomcat application server is an application server that runs
business applications and supports the J2EE and web services standards.

SPRING: Spring application developer is a toolkit which is designed for the creation of more
complex projects, providing fully dynamic web application utilizing EJB’s. This consist of EJB tools ,
CMP ,data mapping tools & a universal test client that is designed to aid testing of EJB’ s.

HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web
browser & a Web Server.

HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer)

TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols

used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and
IP.

1.4 References
SRS (IEEE SRS Format and Format provided by TGMC)

Project specification requirement (provided by TGMC)

Problem Definition (provided by TGMC)

6
 1.5 Technologies to be used
J2EE – Application architecture
JAVA – Application architecture
SPRING STS – Development tool
APACHE TOMCAT - Application Server
MYSQL – Database
JSP – Design pages

1.6 Overview
SRS includes two sections overall description and specific requirements

Overall description will describe major role of the system components and interconnections.
Specific requirements will describe roles & functions of the actors.

2) Overall Description
The following sections describe the general factors that affect the product and its requirements.
Customer must have a valid User Id and password to login to the system. After the valid user logs
inhe is shown the list of accounts he has with the bank. On selecting the desired account he is taken to
a page which shows the present balance in that particular account number, user can request details of
the last ‘n’ number of transactions he has performed. User can make a funds transfer to another
account in the same bank. User is provided with a transaction password which is different from the
login password.User can transfer funds from his account to any other account with this bank. If the
transaction is successful a notification should appear to the customer, in case it is unsuccessful, a
proper message should be given to the customer as to why it failed. User can request for cheque
book/change of address/stop payment of cheque’s.User can view his monthly as well as annual
statements. He can also take print out of the same.Appropriate help to be provided as and when
requested by the user.

7
2.1 Product Perspective
The client will have client interface in which he can interact with the banking system. It is a web
based interface which will be the web page of the banking application. Starting a page is displayed asking
the type of customer he is whether ordinary or a corporate customer. Then the page is redirected to login
page where the user can enter the login details. If the login particulars are valid then the user is taken to a
home page where he has the entire transaction list that he can perform with the bank. All the above activities
come under the client interface.
The administrator will have an administrative interface which is a GUI so that he can view the entire
system. He will also have a login page where he can enter the login particulars so that he can perform all his
actions. This administrative interface provides different environment such that he can maintain database &
provide backups for the information in the database. He can register the users by providing them with
username, password & by creating account in the database. He can view the cheque book request &
perform action to issue the cheque books to the clients.

8
2.2 Software Interface

User on Internet : Web Browser, Operating System (any)

Application Server : APACHE TOMCAT
Data Base Server : MYSQL
Network : INTERNET
Development Tools : SPRING STS (J2EE, Java, JSP), MYSQL, OS (Windows),
Application Server.

2.3 Hardware Interface

Client Side ( IE Along with Printer )

Processor Ram Disc Space
Internet Explorer Pentium II at
6.0 500 MHz 64 MB 1 GB
Server Side
Apache Tomcat Pentium III at
application server 1 GHz 512 MB 2 GB

Pentium III at 1GB

Mysql 1 GHz 512 MB (Excluding data size)

2.4 Communication Interface

Client on Internet will be using HTTP/HTTPS protocol.

Client on Intranet will be using TCP/IP protocol.
A Web Browser such as IE 6.0 or equivalent.
2.5 Product Features :
The Internet banking system consists of following modules :
1) Login Process: This module allows valid customers to access the functionalities provided by
the bank.
2) Balance Enquiry: This module maintains the balance details of a particular account.

9
 3) Update Profile: This module allows the customer to update profile of their account.
4) Funds Transfer: This module allows the customers to transfer funds from one account to
another within the same bank.
5) Change of Password: This module allows customers to change their password.
6) Mini Statements: This module allows customers to view their transaction details.

2.6 User Characteristics :

Customers : The normal users will have an account of fixed or savings and should have a minimum
balance of 500 Rs. He can transfer funds to another account of the same bank & may view his monthly or
annual statements.

2.7 Design and Implementation Constraints

Login and password is used for identification of customer’s account and there is no facility
for non users to login.
This system works only on a single server.
GUI is only in English
Limited to HTTP/HTTPS protocols

2.8 Use-Case Model Survey:

Description and the priority of this system

When we consider the online internet banking in this we provide the details of how to access the
bank account without going to the bank through internet.
When we consider the priority of this project it is mainly of medium cost, efficient to user access
data, provides the required data, safe and secure one .we can know the details of our account whether
it may be a transaction or deposit or balance enquiry etc.
Overall view of the banking system:
The Online Internet Banking provides us the banking facility through internet.
The overall view of the banking System is as shown below:

10
Use-Case Model Survey:

Login

account list
initialises

customer
balance enquiry
start sessions

funds transfer
Data Backup
performs

administrator
update profile
Crash recovery

request cheque book

End sessions
corporate
ministatements

shutdowns

help

log out

11
Activity Diagram for overall system:

start

Enter userid &

passwd

valid user no

yes

balance enquiry Funds transfer update profile request cheque Ministatements

book

your account to:

balance is ::.... ammount: .

Log out

stop

Users of the system:

In this online internet banking system, the users are
 Administrators

 Customers



12
1. Administrator: He is the super user responsible for managing system users, taking system backup,
generating reports, maintaining organization details, Starting Sessions and ending Sessions and also
manages various requests from different Types of users.
Providing UserName, Password and other information required for the users to start an account.
Starting Sessions: The Administrator creates the system users and will be assigned with the
different roles. He is also responsible to start the session when a particular user wants to use the
system every time(It is automatically managed setup).
Managing Data Backup: The Administrator is responsible for managing entire details by taking
the backup periodically. He also takes the Backup of the database in order to prevent loss of data
on system crashes or inorder to prevent malfunctioning. He can take a backup of entire database
or a particular section.
Crash Recovery: The Administrator manages the crash recovery at the time of system crash or
failure occurs.
Ending session: The administrator is responsible for ending the session when the particular user
logged out of the system(It is automatically managed setup).

2. Customer(Normal/others): Ordinary customers have a user name & password with which they can login into
their account. They can perform all the transactions such as funds transfer, balance enquiry, cheque book
request, etc by sitting at their home on internet.
Login: User can login to the system by providing appropriate username and password provided
by the administrator.
Selecting the Account: After logging in the user is provided with a screen showing the details
of accounts and he selects one of the account inorder to perform the transaction.
Balance Enquiry: He can view the balance left in his account, if once he has entered into his
account.
Funds Transfer: Upon the request the user can transfer funds from his account to other
accounts.
Request for cheque book : He can request for cheque book.
Mini statements: He also can take a mini statement print out upon his requirement.

13
3. Corporate: The corporate users include Industrialists, Entrepreneur, Organizations and Academicians etc.
They have a corporate id along with username & password. The organization will have an administrator to
maintain all the details of their employees. He deposits salaries of the employees into the accounts of the
corresponding employees. These employees can perform all the transactions that ordinary customer does.

Login: corporate can login to the system by providing appropriate username, password and along
with Corporate-ID provided by the administrator.
Selecting the Account: After logging in the user is provided with a screen showing the details of
accounts and he selects one of the account inorder to perform the transaction.
Balance Enquiry: He can view the balance left in his account, if once he has entered into his
account.
Funds Transfer: Upon the request the user can transfer funds from his account to other
accounts.
Request for cheque book : He can request for cheque book.
Mini statements: He also can take a mini statement print out upon his requirement.
Internal administrator: Every corporation will be having its own internal administrator who is
responsible for maintaining details of their employees, deposits salaries of the employees into their
accounts.

14
2.9 Architecture Diagram :

15
2.10 ER- Diagram :

2.11 Assumptions and Dependencies

The details of customers such as username, password, account type and their corresponding authority details
should be manually entered by the administrator before using this system.

16
 Every user should be comfortable of working with computer and net browsing.
He should be aware of the banking system.
He must have basic knowledge of English too.

3) Specific Requirements

3.1 Use-Case Reports

i) Administrator: He is the super user responsible for managing clients of the system, taking
system backup, generating reports, maintaining organization details.

Manage Clients: The Administrator assigns new users when a new client joins the
online bank. Also he can delete an account when any of the clients leave the bank
organization.
Maintain Organization Details: The Administrator maintains entire details of the
organization that includes details of the clients, entrepreneur details etc.
Take System Backup: The Administrator Backup the database in order to prevent loss
of data on system crashes. He can backup entire database or a particular section.. Generate
Reports: : Responsible for checking the logs of different system users for auditing and
maintaining the integrity of the system

Manage Clients

 Name Of Use-Case: Manage clients.


Description:

The Administrator assigns new users when a new client joins the online
bank. Also he can delete an account when any of the clients leave the bank organization.
Preconditions:
Administrator is already logged in.

17
 delete_account

manage clients

create_account

 Name Of Use-Case: Maintain organizational details


Description: The Administrator should maintain all the organizational details.
Preconditions:
Administrator is already logged in.

enterprenuar_details

details

client _details

Activity diagram for maintain organizational details:

18
 Enter customer
details

Store details in
database

 Name Of Use-Case: Take System backup.


Description: The Administrator Backup the database in order to prevent loss of data on
system crashes. He can backup entire database or a particular section.
Preconditions:
Administrator is already logged in.

 Name Of Use-Case: Generate Reports.


Description: The Administrator is responsible for checking the logs of different clients
for auditing and maintaining the integrity of the system.
Preconditions:
Administrator is already logged in.

ii) Customer :

19
.
.
. Ordinary customers have a user name & password with which they can login into their account. They
can perform all the transactions such as funds transfer, balance enquiry, cheque book request, etc by sitting at their
home on internet.

Login: User can login to the system by providing appropriate username and password provided
by the administrator.
Selecting the Account: After logging in the user is provided with a screen showing the details
of accounts and he selects one of the account inorder to perform the transaction.
Balance Enquiry: He can view the balance left in his account, if once he has entered into his
account.
Funds Transfer: Upon the request the user can transfer funds from his account to other
accounts.
Request for cheque book: He can request for cheque book.
Mini statements: He also can take a mini statement print out upon his requirement.

 Name Of Use-Case: Login.


Description: Customer must provide a valid User Id and password to login to the system


Preconditions:

Customer must have a valid User Id and password to login to the system.

+access

<<success>>
access account

+relogin <<failure>>

Login
+warning

warning message

20
3.1.1 Activity Diagram for Login:

When the user opens the web page, he is shown with a page which asks him whether he is normal
or a corporate customer. Then he is redirected to login page. Here the customer is asked to enter user name &
password (corporate id if he selects corporate). When the user enters the details & submits it goes to a validation
engine where it checks valid/not. If valid he is shown with list of accounts he has with the bank.

customer System

prompt for user

id & passwd
Enter user id &
password

validate user &

passwd

invalid

valid

shows accounts
list

 Name Of Use-Case: Accounts accessing.


Description: Here the page will display all the accounts that the user has with the bank.
.Preconditions:
Client has already logged in.

21
 Savings

Current
accounts list

fixed

Accessing view:

User after logging into his/her account a page is displayed with the basic requirements:
1) Balance Enquiry.
2) Funds Transfer (same bank).
3) Request Cheque Book.
4) Mini statements.
5) Update profile.
User can perform various actions on his/her account.

Name Of Use-Case: Balance enquiry.

Description: Client can view the balance left in his account, if once he has entered into
his account.
.Preconditions:
The client has already been logged in.

selects account requests balance displays

enquiry balance

3.1.2 Activity Diagram for balance enquiry:

When the customer needs to check the balance, he selects balance enquiry option from the home page.
Then the system checks the balance in his/her account & displays it on the balance enquiry screen.

22
 Customer System

display the
transactions

select balance
enquiry option

display the
balance

 Name Of Use-Case: Funds Transfer.


Description: The client can transfer the amount from his account in the bank to the
other account in the same bank.
.Preconditions:
The client has already been logged in.

+wrong passwd
Payee exists enter amount transfer notify customer
in our list
+try again not valid

Enter payee
Transaction paswd
+passwd correct

valid Payee not enter payee

in list submit wait for
details trans passwd

23
3.1.3 Activity Diagram for funds transfer:
When the customer selects the funds transfer option in the home page. Then the system prompts for
transaction password. When the user enters the transaction password, system checks whether the password is
correct or not. If valid it prompts for payee & amount. User enters the payee details & amount, system checks
whether the balance is available. If available it transfers & updates both the accounts. Customer is notified
whether transaction is success or not.

24
  Name Of Use-Case: Request cheque book.

Description: The client can request for cheque book by giving the details required.
.Preconditions:
The client has already been logged in.

request cheque book Enter address submit

chequeBook issue

3.1.4 Activity diagram for cheque book request:

When the customer requests for a cheque book in the home page, the system prompts for address details
of the customer. After entering the particulars it goes to validation engine & checks the particulars are valid or not.
If valid it accepts the request & proper message is displayed to the customer.

Customer System

display the
transactions

select cheque book

request option

prompt for
address details

Enter address
details

validation

no
yes

accept request

show success/failure
notice

25
  Name Of Use-Case: Stop payments of cheques.

Description: Client can request to stop the payment of the cheque giving its details.
Preconditions:
The client has already been logged in.

stop payment Enter Submit

of cheques cheque details

3.1.5 Activity Diagram for stop payments of cheques:

When the customer selects stop payments of cheques option in the home page, the system
prompts for cheque details which is to be stopped. Customer enters the details such as cheque number,
payee, date, etc. The system accepts the request & provides the customer success/failure notice.

Customer System

display the
transactions

select stop payment of

cheques option

prompt for
cheque details

Enter cheque
details
accept request

show success/failure
notice

26
  Name Of Use-Case: Mini Statements.
Description: The client can request the mini statements i.e monthly, annual or ‘n’
number of transactions.
.Preconditions:
The client has already been logged in.

Monthly stmts

Ministatements print outs

Annual stmts

3.1.6 Activity Diagram for Mini Statements:

When the user requests for mini statements in the home page, system asks the type of statement needed by
the customer. When the customer selects the type of statement (monthly/annual/’n’ number of transactions). The
system displays the list of transactions on the screen. If the customer wants to take print outs he can take the print
outs of the same.

27
 Customer System

display the
transactions
select ministatements
option

prompt for type

of stmt

select type of
statement

accept request &

provide transaction list

view/take print
out of list

 Name Of Use-Case: Update Profile.


Description: The client can update his profile, i.e he can change his password, address,
mobile number, e-mail id, etc.
Preconditions:
The client has already been logged in.

request for enter new values submit fields updated

updating in the fields

3.1.7 Activity Diagram for update profile:

When the customer requests for update profile in the home page, the system shows present details to the
customer. The customer changes the required fields he wishes to change & submits. The system updates the
information & a proper message is displayed to the customer about the updated information.

28
 Customer System

display the
transactions
select update
profile

Shows present details with

edit option

select edit option for the

field to be changed
prompt for new
value

Enter new value

for the field
update the
change

send the updated

information

iii) Corporate users :

The corporate users will have the same functionalities as that of a customer. The
extra functionality of corporate user is to have an internal administrator.
 Name Of Use-Case: Internal administrator duties.

Description: The internal administrator has to maintain company accounts & transfer
salaries to the employees accounts.
Preconditions:
The internal administrator should have valid corporate_id, username &
password.
The internal administrator has already been logged in.

29
 manage company
accounts

internal
administrator

transfers money
to employee's account

3.2 Supplementary requirements:

1) Performance Requirements

System can withstand even though many no. of customers request the desired service.
Access is given to only valid users of bank who requires the services such as balance enquiry,
update profile, funds transfer, mini statements, and request for stop payments and for cheque book

2) Safety Requirements

By incorporating a robust and proven mysqlDB into the system, reliable performance and integrity of
data is ensured. There must be a power backup for server system. Since the product is of 24x7 availability
there should be power backup for server which provides the information .Every day the data should be backup
even when the operation of an user is not successful i.e., while performing the operation power failure occurs
then data should be backup.

3) Security Requirements

Sensitive data is protected from unwanted access by user’s appropriate technology and
implementing strict user-access criteria of unique user number and Password in such a way
that unauthorized user cannot log in. Operational rights for each user/ terminal can be
defined.

30
 Online Banking uses the SSL (Secure Socket Layer) protocol for transferring data.

SSL is encryption that creates a secure environment for the information being transferred between
customer browser and Bank. Online Banking uses 128-bit digital certificate from VeriSign for
encryption of the Secure Sockets Layer (SSL) session. SSL is the industry standard for encrypted
communication and ensures that customer's interaction with the Bank over the Internet is secure.

Secure Socket Layer (SSL) protects data in three key ways:

 Authentication ensures that you are communicating with the correct server. This
prevents another computer from impersonating Bank.

 Encryption scrambles transferred data.

 Data integrity verifies that the information sent by customer to Bank wasn't altered during the
transfer. The system detects if data was added or deleted after customer sent the message. If
any tampering has occurred, the connection is dropped.

3.3 Non Functional Requirements :


Those requirements which are not the functionalities of a system but are the characteristics of a system
are called the non-functionalities.

1.Secure access of confidential data. SSL can be used.

2.24X7 availability
3.Better component design to get better performance at peak time
4.Flexible service based architecture will be highly desirable for future extensions.



31
 4) Supporting Information:

4.1) System in context:

The “Online Banking System” is an independent system. In Version 1.0, the system is a Web based
application which performs various activities of banking.

 Takes data from the customer.


 Interact with the database for the data storing.

 Includes business logic that supports inventory and payroll.

32
4.2) DFD diagram:

33
4.3) Class diagram:

Customer
userId : String Funds Transfer
password : String
userId : String Balance Enquiry
firstName : String
accountType : String userId : String
lastName : String
TransId : String accountType : String
address : String
payee : String balance : Currency
mobile : String
amount : Currency
showBalance()
login()
transfer()
performTransaction()
logOut()

Mini Statements
userId : String
Update Profile transList : String
userId : String
Cheque Book password : String showTransList()
userId : String firstName : String
chequeBookDetails : String lastName : String
address : String
requestChequeBook() mobile : String
stopPayCheques()
updateProfile()

34
5) Appendices:
5.1) Appendix A: Sequence Diagrams

5.1.1)Login process:

login page system services

: customer

enter userid & passwd

verification of valid user

allow access to services

login failed

relogin(+3)/block account

5.1.2)Balance Enquiry:

main page balance enquiry DataBase

: customer

Requests BalanceEnq.
redirect

check

shows balance

view

35
5.1.3)Funds Transfer:

main page funds transfer database

: customer
page

request fund transfer

redirect

ask for trans passwd

enter passwd
check passwd
request ok

request for payee & amount

enter payee & amount

check balance
display message

notify

success/failure

notify customer

36
5.1.4)Update Profile:

main page update page database

: customer

request update

redirect

get the details

details

display all fields

edit the feilds to be updated

update

updated

notify

display updated details

5.1.5)Cheque Book Request:

main cheque book banker database

: customer
page
Request for chequeBook
redirect

request details

provides details

accepts details

request processing

notify customer check available

check numbers

available numbers

send to customer

37
5.1.6)Stop payment of cheques:

main page stop database

: customer
payamen...

request stop payments

redirect

asks for cheque details

provide cheque details

validate

stop cheque

display message

notify customer

5.1.7)Mini Statements:

main page ministmts page database

: customer

request ministatements

redirect

type of statement?

select type of statement

access data requested

provides stmt details

displays transactions list

request printouts

provides printout format

38
6) Data Dictionary

6.1)Table Name: USER_ACCOUNT

Description: This table is used to store user account details.

Key Field Name Data Type Length Nullable
CUSTOMER ID INT 10 NO
PASSWORD VARCHAR NO
EMAIL VARCHAR NO

6.2)Table Name: CUSTOMER

Description: This table is used to store customer details.

Key Field Name Data Type Length Nullable

PK ID INT 10 NO
ACC NUMBER INT 12 NO
ACC TYPE VARCHAR 20 NO
AGE VARCHAR 10 NO
FIRST NAME VARCHAR 40 NO
LAST NAME VARCHAR 40 NO
ADDRESS VARCHAR 200 NO

6.3)Table Name: PRIMARY_ACCOUNT

Description: This table is used to store account details.

Key Field Name Data Type Length Nullable

ACC ID VARCHAR 12 YES
ACC NUMBER VARCHAR
ACC BALANCE DOUBLE YES

6.4)Table Name: FUND_TRANSFER

Description: This table is used to store the fund transfer details.

Key Field Name Data Type Length Nullable

Id INT NO
DEBIT ACC VARCHAR 50 YES
CREDIT ACC VARCHAR 50 YES
DATE TIMESTAMP NO
BALANCE DOUBLE YES
DEBT_AMMOUNT DOUBLE YES
TRANSACTION VARCHAR YES

39
7) Software Life Cycle Model:

In order to make this Project we are going to use Classic LIFE CYCLE MODEL .Classic life cycle
model is also known as WATER FALL MODEL. The life cycle model demands a Systematic sequential
approach to software development that begins at the system level and progress through analysis design coding,
testing and maintenance.

The Classic Life Cycle Model

The waterfall model is sequential software development process, in which progress is seen as
flowing steadily downwards (like a waterfall) through the phases of conception initiation, Analysis,
Design (validation), construction. Testing and maintained.

1) System Engineering and Analysis:-

Because software is always a part of larger system work. Begins by establishing requirement for all
system elements and Then allocating some subset of these requirement to the software system Engineering
and analysis encompasses the requirement gathering at the system level with a small amount of top level
design and analysis.

2) Software requirement Analysis:

The requirement gathering process is intensified and focused specifically on the software
.Requirement for the both system and software are discussed and reviewed with the customer. The
customer specifies the entire requirement or the software and the function to be performed by the
software.

3) Design:

40
 Software design is actually a multi-step process that focuses on distinct attributes of the program
data structure, software architecture, procedural detail and interface of the software that can be assessed or
quality before coding begins .Like requirement the design is documented and becomes part of the
software.

4) Coding:
The design must be translated into a machine readable form. The coding step performs this task. If
design is programmed in a detailed manner, coding can be accomplished mechanically.

5) Testing:
Once code has been generated programmed testing begins. The testing process focuses on the
internals of the software ensuring that all statement have been tested and on the functional externals hat is
conducting tests to uncover the errors and ensure that defined input will produce the results that agree
with the required results.

Unit testing:-
In computer programming, Unit testing is software Verification and validation method where the
programmer gains confidence that individual units of source code are fit to use A unit is the smallest
testable part of an application. In procedural programming a unit may be an individual programmed,
function, procedure, etc. while in object-oriented programming, the smallest Unit is a class, which may
belong to a base/super class abstract class or derived/child class.

Benefits:
The goal of unit testing is to isolate each part of the program and show that the individual parts are
correct. A unit test provides a strict written contract that the piece of code must satisfy.
Documentation:-
Unit testing provides a sort of living documentation of the system. Developers looking to learn
what functionality is provided by a unit and how to use it can look at the tests to gain a basic
understanding of the unit API.

Limitation of unit testing:

Testing cannot be expected to catch error in the program –It is impossible to evaluate all execution
paths for all but the most trivial programs. The same is true for unit testing. Additionally, by unit testing
only types the functionality if the units themselves.
6) Maintenance:
Software will undoubtedly undergo change after it is Delivered to the customer .Change will occur
because errors have been encountered because the software must be able adopted to accommodate
changes in its external environment because the customer requires functional or performance enhancement
enhancements. The classic life cycle is the oldest and most widely used paradigm or software
engineering

41
 8) Screen Shots

8.1)Login Page

42
8.2)Registeration

43
8.3)Welcome

44
8.4)Deposit

8.5)Withdraw

45
8.6)Money Transfer

46
8.7)Check balance

47
8.8)Mini-statement

48
9) Bibilography /References

1. (n.d.). Retrieved 2012, from http://www.programmingportal.in/2010/05/onilne-banking-system-

sequence-diagram.html

2. (n.d.). Retrieved 2012, from www.php.net

3. (n.d.). Retrieved 2012, from SSL: http://info.ssl.com/article.aspx?id=10241

(2012). Retrieved november 2012, from AppPerfect: www.appperfect.com

4. nternet-banking-for-many-benefits. (n.d.). Retrieved 2012, from

http://smartbisplan.com/internet-banking-for-many-benefits/

5. Synopsis-Internet-Banking. (n.d.). Retrieved 2012, from

http://www.scribd.com/pgailani/d/36880246-Synopsis-Internet-Banking

49
10)Conclusion

The Online Banking suite provides a global accounting foundation that provides the all private
banks with Online banking facilities. It allows client of private banks to carry out their day to day
banking transactions.

The application illustrated or demonstrates the way to develop an online banking system by using
interactive web client by using JSP, spring mvc with safer way to access &encapsulate database by
EJB component. This suggests the application server simply deployable and accessible. This we
conclude that Online banking system is Quick, simple, authenticated access to accounts via the
desktop.

50