1.

Introduction
The purpose of this project is to develop an on-line banking system that provides customers with
the facility to check their accounts and do transactions online. The system will provide all the
banks facilities to its customers when their authentications [user id and password] match,
including viewing account information, performing transfers, giving the customer an option of
changing address, paying bills on-line, password retrieval, performing transactions, viewing
transactions and the locations the bank and its branches. The system should also support an
online enrollment facility for credit card customers and should allow customers to view their
personnel accounts and to pay bills online from their account. The system should assign a unique
transaction number to every transaction that a user makes. It should also generate credit card
numbers automatically when administrator,

Administrator will administer both normal bank account and credit card bank accounts. The
administrator should have the ability to perform various operations like creating a normal bank
account for the customer and performing functions like transfers, withdrawals and deposits
when the customers want teller transactions.
The administrator account on the request
of the bank customer. The customer should be able to access his/her account from anywhere
just by inputting the correct user-id and password.
1.1. Existing System:
The existing system involves the following activities:
Activities like Demand Draft issues, Pay Order issues are done manually and
corresponding registers updated manually.
Above all in manual system, only the man responsible for DD/Pay issue is aware of the various
records to be updated on each transaction.
Readability of the records, which are maintained manually, is also constrained in the present
system.
Since record are kept on a paper registers, again is also a problem.
Further retrieving information from such records for a period is tedious, as the storage place
restricts, old records will be kept off the disk.

Page | 1
 Also report generation of the various areas is done manually using great amount of manpower
and time.
The great limitation to the existing system is that the service to the customers is limited to the
bank hours only. The online banking facility provides 24 hours service to the customer.
1.2. Problems with conventional system:
1. Lack of immediate retrievals: -The information is very difficult to retrieve and to find
particular information like- E.g. - To find out about the customer details, the user has to go through
various registers. This results in inconvenience and wastage of time.
2. Lack of immediate information storage: - The information generated by various
transactions takes time and efforts to be stored at right place.
3. Lack of prompt updating: - Various changes to information like customer details or
immunization details of customer are difficult to make as paper work is involved.
4. Error prone manual calculation: - Manual calculations are error prone and take a lot of time
this may result in incorrect information.
5. Preparation of accurate and prompt reports: - This becomes a difficult task as information
is difficult to collect from various registers.
1.3. Goals of proposed system:
1. Planned approach towards working: - The working in the organization will be well
planned
and organized. The data will be stored properly in data stores, which will help in retrieval of
information as well as its storage.

2. Accuracy: - The level of accuracy in the proposed system will be higher. All operation
would be done correctly and it ensures that whatever information is coming from the center is
accurate.
3. Reliability: - The reliability of the proposed system will be high due to the above stated
reasons. The reason for the increased reliability of the system is that now there would be proper
storage of information.
4. No Redundancy: - In the proposed system utmost care would be that no information is
repeated anywhere, in storage or otherwise. This would as sure economic use of storage space
and consistency in the data stored.

Page | 2
5. Immediate retrieval of information: - The main objective of proposed system is to
provide for a quick and efficient retrieval of information. Any type of information would be
available whenever the user requires.
6. Immediate storage of information: - In manual system there are many problems to store
the largest amount of information.
7. Easy to Operate: - The system should be easy to operate and should be such that it can
be developed within a short period of time and fit in the limited budget of the user
1.4. Alternative Solutions:

1. Improved Manual System: One of the alternative solutions is the improvement of the
manual system. Anything, which can be done by using automated methods, can be done
manually. But the question arises how to perform thing manually in a sound manner. Following
are some suggestions, which can be useful in the manual system. A more sophisticate register
maintenance for various Customer
Information. Adequate staff may be maintained so that updating are made at the very moment
at the same time. Proper person for proper work should be made responsible so that a better
efficiency could be achieved. This needs a lot of work force.
2. Batch System: Another alternative solution can be used of computer-based batch system
for maintaining the information regarding customer details and employees. A batch system
refers to a system in which data is processed in a periodical basis. The batch system is able to
achieve most of the goals and sub goals. But a batch system data is processed in sequential basis.
Therefore batch system is not suggested.
3. Online System: This system (HMS) provides online storage/ updating and retrieval
facility. This system promises very less or no paper work and also provides help to Manager
and staff. In this system everything is stored electronically so very less amount of paper work
is required and information can be retrieved very easily without searching here and there into
registers. This system is been discussed here.
1.5. Scope:
The aim is to automate the system, pre-checking the inclusion of all required material
and automatically process the transactions used in a banking. The criterions which include over
here is to creation of an accountant it’s all respective perspectives. The data used by the system

Page | 3
is stored in a database that will be the centre of all information held about the customer and the
base for the remainder of the process after initial signing up been made.
This enables things to be simplified and considerably quickened, making the jobs of the involved
and considerably quickened, making the jobs of the involved people easier. It supports the
current process but centralizes it and makes it possible for decisions to be made earlier and
easier way.

Page | 4
2. Overall Description
2.1. Introduction:

the Internet for businesses. People are rushing towards the e-commerce applications for their
day-today needs, which in turn are making the Internet very popular. Online Banking has given
both an opportunity and a challenge to traditional banking. In the fast-growing world, banking
is a necessity, which in turn takes a lot of time from our busy schedule. Going to a branch or
ATM or paying bills by paper check and mailing them out, and balancing checkbooks are all
time-consuming tasks. Banking online automates many of these processes, saving time and
money. For all banks, online banking is a powerful tool to gain new customers while it helps to
eliminates costly paper handling and manual teller interactions in an increasingly competitive
banking environment. Banks have spent generations gaining trust of their customers, and the
goal for this project is to develop a user friendly, secure Online Banking Application. The
application will be built using Java Server Pages (JSP), tomcat as the application server, and
Microsoft Access / SQL Server as a database.
2.2. Architecture of Online Banking:
The Online Banking Application is based on 3-tiered model. The Enterprise architecture for Online
Banking Application is shown below.

Page | 5
The 3-tiered architecture shown above has the following major components:
1. Client: There will be two clients for the application. One will be a web-based user-friendly
client called bank customers. The other will be for administration purposes.
2. Application Server: It takes care of the server script, takes care of JDBCODBC driver, and
checks for the ODBC connectivity for mapping to the database in

3. Database:
Simply stated, the application works based on a request/response protocol. A client initiates a
request to the server. The server responds by executing the business logic hosted inside the JSP
program and if required, communicates with the Database Server to fulfills a client request

Page | 6
The Online banking Application project will be divided into 4 modules namely:
1. Bank Account
2. Bank Account Administrator
3. Credit Card Customer
4. Credit Card Account Administrator
Each module is discussed in more detail under design phase.
Module 1
In this module the customer is allowed to logon to the website and can access his/her account
by getting user name and password which will be verified with the server and the database.
Once he/she gets verified then they are allowed to view their personal account and perform
operations such as change of address, paying bills online, viewing transactions and transferring
money into other accounts. The data will be highly secured using Secure Socket Layer (SSL)
technology. Once the customer finishes the task the update information instantly gets stored into
the database. The customer is then allowed to sign out from his/her account.
Module 2
In this module the administrator is allowed to log on to the website and can access his/her
administrative account by using the user name and password which will then be verified with
the database. Once he/she gets verified the administrative interface will be displayed, where the
administrator can perform operations for both new customers and existing customers.
Administrator will help a new customer in opening their account by taking complete information
from them. Administrator provides services like withdrawal, deposit, transfer and deleting
customer during the time of closing the account. In this module administrator provides great
customer service to the customers who want to do phone banking or teller banking. The data
will be highly secured using Secure Socket Layer (SSL) technology. The interface for
administrator will be both very user friendly and efficient. The data gets stored in the database
instantly when the administrator hits the submit button.
Module 3
In this module, the customer is allowed to apply for the credit cards (Student, Premium and
Basic) or for the loan (home, auto and education). Depending upon their selection the

Page | 7
corresponding page will be shown when they will be asked to fill out the form. Depending on
the credit rating the customer will be either accepted or rejected. Usually the credit rating will
be checked with national credit bureau, which will be internally connected to INS and Social
Security office database. Once the customer gets approved for the credit card or loan, their credit
card will be sent to them by postal service. Once they decided to register themselves to an online
credit card banking, they enroll by using the enroll form, where they will be asked to enter their
credit card number, their Social Security Number and user defined password (Numbers only).
To access the account, customers should visit the credit card website and get verified with the
database by entering the user name and the password they have created. If the verification is
successful then they will be allowed to view their credit card account which will display
information about their credit limit and balance. They are also allowed to make online bill
payments using their credit card account. As this module contains all important data like credit
card numbers, account user name and password and online bill payments, it needs to be secure,
therefore Secure Socket Layer (SSL) will be used. It encrypts the data before it is sent and gets
decrypted at the server and vise-versa. This will prevent the hackers to view the data, which is
being transferred through any media.
Module 4
In this module the administrator is allowed to log on to the website and will be allowed to access
his/her administrative account by using its user name and password which will then gets verified
with the database. Depending upon their authentication, the administrative page will be
displayed, where administrator is allowed to assign credit limits for the customer depending
upon what kind of request the customer has made. The administrator will be allowed to put a
hold on the credit card account for security reasons, like lost/stolen credit card and this facility
will protect customer information from getting misused by others. Once the administrator
selects the type of card or loan requested and the social security number from the database on a
single click the credit limit will be assigned. There will be a special field in the database, which
will allow the administrator to keep track of the customers who have already been issued their
cards.
The application will be having other functionalities such as:

Page | 8
The application will be using a backend as MS- Access database, all the front-end will be written
in Java Server Pages (JSP) and Jakarta Tomcat application server will be used as a middle ware
which will take care of the connection between front-end and backend.
2.3 Project Requirements:

2.4 User Characteristics:

Every user should be:

2.5 Constraints:

guest.

Page | 9
3. Feasibility Study
Feasibility study is made to see if the project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study lets
the developer foresee the future of the project and the usefulness. A feasibility study of a system
proposal is according to its workability, which is the impact on the organization, ability to meet
their user needs and effective use of resources. Thus, when a new application is proposed it
normally goes through a feasibility study before it is approved for development. The document
provides the feasibility of the project that is being designed and lists various areas that were
considered very carefully during the feasibility study of this project such as Economic,
Technical and Operational feasibilities.
Three key considerations are involved in the feasibility are:-

Economic Feasibility
Technical Feasibility
Operational Feasibility
3.1.Economic Feasibility:

Economic analysis is most frequently used method for evaluating the effectiveness of the
proposed system. This is an ongoing effort that improves in accuracy at each phase of the
system life cycle.

As the necessary software and hardware is available in the organization, the initial investment
for the proposed system is nil. The proposed system minimizes the time and effort right from
data collection to answering queries, which result in significant saving in operating costs. Thus,
the proposed system is economically feasible.

3.2. Technical Feasibility:

It centers around the existing computer system (h/w, s/w, etc) and to what extent it can support
the proposed system. The Necessary hardware and software tools are available in the
organization and the software recommended supports the system objectives. Thus it is
technically feasible to design and develop the proposed system.

Page | 10
3.3. Operational Feasibility:

People are inherently resistant to change, and computers have been known to facilitate change.
An estimate should be made of how strong a reaction the user staff is likely to have towards the
development of a new system.
As the proposed system is a user-friendly package with all the visual aid, the effort that goes into
education and training the user staff is almost negligible.

Therefore, resistance to the proposed system is nil. Based on the above analysis, the recommended
system is feasible.

Page | 11
4. Data Flow Diagrams
4.1. Use Case Diagram:

Use case diagram is a diagram that shows a set of use cases and actors and their relationships.
These diagrams are central to modeling the behavior of a system, a subsystem or a class. We
use them to model the use-case view of a system. Use-case diagram make systems, subsystems
and classes approachable and understandable by presenting an outside view of how those
elements may be used in the context.
In the present project of Online Banking System, the use case is described as below. The Actors
here are: CUSTOMER, ADMINISTRATOR.
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.1 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.2. 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.

Page | 12
1.3. Pre-Conditions

The user should have a valid account in the bank.

1.4. Post Conditions

The account database is modified after transaction.

The below given diagram represents for Online Banking system.

Page | 13
4.2 Class Diagram:

Class diagram show a set of classes, interface and collaborations and their relationships. For the
most part this involves modeling the vocabulary of a system, modeling collaborations or
modeling schemas. A class diagram is a collection of vertices and arcs.
These diagrams are the foundations for deployment and component diagrams. A class is a
description set of a set of objects that share same attributes, operations, relationships and
semantics. Classes are important building blocks of and object-oriented system. A class
implements one or more interfaces. Classes may include abstractions that are part of a problem
domain as well as classes that make up and implementations. We use classes to represent
software things, hardware things and even things that are purely conceptual. A class is
represented as a rectangle with compartments. An attribute is a named property of a class that
describes a range of values that instances of the property may hold. An operation is
implementations of a service that can be requested for any object of the class to effect behavior.
A responsibility is a contract or an obligation of a class.

Page | 14
The below given diagram represents Class diagram for Online Banking system.

Page | 15
Page | 16
4.3 Interaction Diagrams:

An interaction diagrams shows an interaction, consisting of a set of objects and their

relationships including the messages that may be dispatched among them.

Interaction diagrams involve modeling concrete or prototypical instances of classes, interfaces,

components, and nodes along with messages dispatched among them all in the context of a
scenario that illustrates a behavior.

Interaction diagrams are of two types:

1) Sequence diagram
2) Collaboration diagram
(1) A sequence diagram is an interaction diagram that emphasizes the time ordering of
messages. A sequence diagram is a table that shows objects that are arranged along x-axis and
messages, ordered in increasing time, along y-axis. Sequence diagram has two features that
distinguish them from collaborations diagrams:
a) Object lifelines ->is a vertical dash line that represents an existence of an object
over a period of time.

b) Focus of control->is a tall thin rectangle that shows the period of time during
which an object is performing an action either directly or through an subordinate
procedure.

(2) ACollaboration diagram is an interaction diagram that emphasizes the structural

organization of objects that send and receive messages. Graphically a collaboration diagram is
a collection of vertices and arcs. Collaboration diagram has two features that distinguishes them
from Sequence diagrams:

a) Path -> to indicate how one object is linked to another. We can attach a path
stereotype to far end of a link.

b) Sequence number -> to indicate the time ordering of a message prefix by

number.

Page | 17
The below given diagram represents for Online Banking system.

Page | 18
Page | 19
The below given diagram represents for Online
Banking System.

Page | 20
4.4 Activity Diagram:

An activity diagram shows the flow from activity to activity. An activity is an ongoing non-
atomic execution within a state machine. Activities ultimately result in some action, which is
made up of executable atomic computations that result in a change in state of a system or return
of a value. Activity diagram is a collection of vertices and arcs.Activity diagrams commonly
consist of activity states and action states, transitions, objects.
Action state is an executable atomic computation such as calling an operation on an object, send
a signal to an object, or even create or destroy an object.
Activity state can be defined as a composite whose flow of control is made up of activity states
and actions states. An activity state may have additional parts such as entry and exit actions.
Transition -> Flow of control from one action or activity state to another shown as a simple
directed line.
Branch -> Is a place where we check conditions represented as an diamond may have one
incoming transition two or more

Fork -> It is a synchronization bar that shows start of an activitiesthat run in parallel. It has
one incoming transition and two or more outgoing transitions.
Join -> It represents an synchronization of two or more concurrent flows of control. It may
have two or more incoming transitions and one outgoing transitions.
Swimlanes -> It specifies a locus of activities used especially when we are modeling the
workflow of business process to partitioning the activity state on an activity diagram into groups,
each group representing the business organization responsible for those activities.
The below given diagram represents Online Banking system.

Page | 21
Page | 22
Page | 23
4.5 State Chart:

State diagrams are used to describe the behavior of a system. State diagrams describe all of the
possible states of an object as events occur. Each diagram usually represents objects of a single
class and track the different states of its objects through the system. Use state diagrams to
demonstrate the behavior of an object through many use cases of the system. Only use state
diagrams for classes where it is necessary to understand the behavior of the object through the
entire system. State diagrams have very few elements. The basic elements are rounded boxes
representing the state of the object and arrows indicting the transition to the next state. The
activity section of the state symbol depicts what activities the object will be doing while it is in
that state.
The below given diagram represents for Online Banking
System.

Page | 24
4.6 Component Diagram:

Component diagrams are used to visualize the organization and relationships among
components in a system. These diagrams are also used to make executable systems. Component
diagrams are different in terms of nature and behavior. Component diagrams are used to model
physical aspects of a system.

Page | 25
Physical aspects

Physical aspects are the elements like executables, libraries, files, documents etc which resides
in a node. Component diagram is a special kind of diagram in UML. The purpose is also
different from all other diagrams discussed so far. It does not describe the functionality of the
system but it describes the components used to make those functionalities. Component diagrams
can also be described as a static implementation view of a system. Static implementation
represents the organization of the components at a particular moment single component diagram
cannot represent the entire system but a collection of diagrams are used to represent the whole.
So the purpose of the component diagram can be summarized as:

Visualize the components of a system.

Construct executables by using forward and reverse engineering.
Describe the organization and relationships of the components.
How to draw Component Diagram?

Component diagrams are used to describe the physical artifacts of a system. This artifact
includes files, executables, libraries etc. So the purpose of this diagram is different, Component
diagrams are used during the implementation phase of an application. But it is prepared well in
advance to visualize the implementation details. Initially the system is designed using different
UML diagrams and then when the artifacts are ready component diagrams are used to get an
idea of the implementation. This diagram is very important because without it the application
cannot be implemented efficiently. A well prepared component diagram is also important for
other aspects like application performance, maintenance etc.

So before drawing a component diagram the following artifacts are to be identified clearly:

Files used in the system.

Libraries and other artifacts relevant to the application.
Relationships among the artifacts.

The below given diagram represents Component Diagram for Online Banking system.

Page | 26
4.7 Deployment Diagram:

Deployment diagrams are used to represent the physical architecture of a system. They
present the distribution of the software components on the set of execution units
(nodes).Nodes and artefacts are the main concepts in a deployment diagram. Deployment
diagrams are created in packages, classes, interfaces, components, artefacts or
nodes.Deployment diagrams are used for describing the hardware components where
software components are deployed. So deployment diagrams are used to describe the static
deployment view of a system. Deployment diagrams consist of nodes and their relationships.

Page | 27
 Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.

Purpose:

Deployment diagrams and Component diagrams are closely related. Component diagrams are
used to describe the components and deployment diagrams shows how they are deployed in
hardware. UML is mainly designed to focus on software artifacts of a system. But these two
diagrams are special diagrams used to focus on software components and hardware components.
So most of the UML diagrams are used to handle logical components but deployment diagrams
are made to focus on hardware topology of a system. Deployment diagrams are used by the
system engineers.

The purpose of deployment diagrams can be described as:

Visualize hardware topology of a system.

Describe the hardware components used to deploy software components.
Describe runtime processing nodes.

A deployment diagram consists of nodes. Nodes are nothing but physical hardware used to deploy the
application.

Performance
Scalability
Maintainability
Portability

Page | 28
The below given diagram represents Deployment Diagram for Online Banking system.

Page | 29
4.8 Object Diagram:

An object diagram in the Unified Modeling Language (UML), is a diagram that shows a
complete or partial view of the structure of a modeled system at a specific time.

An Object diagram focuses on some particular set of object instances and attributes, and the
links between the instances. A correlated set of object diagrams provides insight into how an
arbitrary view of a system is expected to evolve over time. Object diagrams are more concrete
than class diagrams, and are often used to provide examples, or act as test cases for the class
diagrams. Only those aspects of a model that are of current interest need be shown on an object
diagram.

The below given diagram represents Object Diagram for Online Banking system.

Page | 30
5. TESTING
There are many testing strategies, but most testing uses a combination of these: black box testing,
white box testing, top down testing and bottom-up testing. However, no strategy or combination
of strategies truly can prove the correctness

5.1 Black Box Testing:

The concept of the black box is used to represent a system whose inside workings are not available for
inspection. In a black box, the test item is treated as

comes out, or the input and output.

The black box is an imaginary box that hides its internal workings

5.2 White-box Testing:

White box testing assumes that the specific logic is important and must be

is an error-based testing, when you already have tested all objects of an application and all
external or public methods of an object that you believe to be of greater importance. In white
box testing, you looking for bugs that have a low probability of execution, have been carelessly
implemented, or were overlooked previously. One form of white box testing, called path-testing,
makes certain that each

path testing are statement testing coverage and branch testing coverage.

Statement testing coverage:

The main idea of statement testing coverage is to test

Page | 31
realistically, it is impossible to test a program on every single input, so you never can be sure
that a program will not fail on some input.

Branch testing coverage: The main ideas behind branch coverage outperform enough tests to
ensure that every branch alternative has been executed at least once under some test. As in
statement testing coverage, it is unfeasible to fully test any program of considerable size.

Most debugging tools are excellent in statement and branch testing coverage.
White box testing is useful for error-based testing.

In white-box testing strategy, the internal workings are known.

5.3 Top-Down Testing:

Top-down testing assumes that the main logic or object interactions and

methods or supporting logic. A top-down strategy can detect the serious design flaws early in
the implementation.

In theory, top-down testing should find critical design errors early in the testing process and
significantly improve the quality of the delivered software because of the iterative nature of the
test. A top-down strategy supports testing the user interface and event-driver systems.

Testing the user interface using a dip-down approach means testing interface navigation. This
serves two purposes, according to Conger. First, the top-down approach can test the navigation
through screens and verify that it matches the requirements. Second, users can see, at an early
stage, how the final applications will look and feel. This approach also is useful for scenario-
based testing. Top-down testing is useful to test subsystem and system investigation.

Page | 32
6. Conclusion
Thus reaching to the conclusion of our project we observe that Traditional banks offer many
services to their customers, including accepting customer money deposits, providing various
banking services to customers, and making loans to individuals and companies. Compared with
traditional channels of offering banking services through physical branches, e-banking uses the
Internet to deliver traditional banking services to their customers, such as opening accounts,
transferring funds, and electronic bill payment.
E-banking can be offered in two main ways. First, an existing bank with physical offices can
also establish an online site and offer e-banking services to its customers in addition to the
regular channel. For example, Citibank is a leader in e-banking, offering walk-in, face-to-face
banking at its branches throughout many parts of the world as well as e-banking services through
the World Wide Web. Generally, e-banking is provided without extra cost to customers.
Customers are attracted by the convenience of e-banking through the Internet, and in turn, banks
can operate more efficiently when customers perform transactions by themselves rather than
going to a branch and dealing with a branch representative.
E-banking services are delivered to customers through the Internet and the web using Hypertext
Markup Language (HTML). In order to use e-banking services, customers need Internet access
and web browser software. Multimedia information in HTML format from online banks can be
displayed in web browsers. The heart of the e-banking application is the computer system,
which includes web servers, database management systems, and web application programs that
can generate dynamic HTML pages.
One of the main concerns of e-banking is security. Without great confidence in security,
customers are unwilling to use a public network, such as the Internet, to view their financial
information online and conduct financial transactions. Some of the security threats include
invasion of individuals' privacy and theft of confidential information.

Page | 33
7. Bibliography
www.google.com
www.scribd.com
www.wikipedia.org

Page | 34