ABSTRACT

This is a simple GUI based system which is very easy to understand and use. In this project, it
contains all the basic functions of [Link] a new account,Transactions like withdrawal and
deposit amount to the account, Getting the balance details, Closing an account Updating the
account details.

In this project, he/she can use all those available features easily without any restruction. It
is too easy to use, he/she can check the total bank account records [Link] about the
features of the bank management system, A user can create an account by providing the
name of the account holder, number, selecting amount type (Saving account or current
account) and providing an initial amount more than or equal to 500.

Then the user can also deposit and withdraw money just by providing his/her account and
entering the amount. For certain purpose, he/she can also check for the balance inquiry
which displays the account number and amount. He/She can also view the entire account
holder’s list. Another feature that he/she can modify their account detail and type if they
want to.

This simple GUI based Bank Management system provides the simplest management of
bank account and transaction. In short, this project mainly focuses on CRUD operation.
There’ s an external data base connection file used in this project to save user’s data
permanently.
 INTRODUCTION
1.1 General Overview of the Problem:
A bank is a commercial or state institution that provides financial services, including
issuing money in form of coins, banknotes or debit cards, receiving deposits of money, lending
money and processing transactions. A commercial bank accepts deposits from customers and in
turn makes loans based on those deposits. Some banks (called Banks of issue) issue banknotes as
legal tender. Many banks offer ancillary financial services to make additional profit; for
example: selling insurance products, investment products or stock broking.
Currently in most jurisdictions commercial banks are regulated and require permission to
operate. Operational authority is granted by bank regulatory authorities and provides right to
conduct the most fundamental banking services such as accepting deposits and making loans. A
commercial bank is usually defined as an institution that provides selected banking services
without meeting the legal definition of bank.
Banks have a long history, and have influenced economy and politics for centuries. In
history, the primary purpose of a bank was to provide liquidity to trading companies. Banks
advanced funds to allow business to purchase inventory, and collected those funds back with
interest when the goods are sold. For centuries, the banking industry only dealt with business not
customers. Commercial lending today is a very intense activity, with banks carefully analyzing
the financial condition of its business clients to determine the level of risk in each loan
transaction. Banking services have expanded to include services directed at individuals and risks
in these much smaller transactions are pooled.

1.2 Problem Definition:

Although the basic type of services offered by a bank depends upon the type of bank and the
country, services provided usually include:
 Taking deposits from their customers and issuing current or checking accounts
and savings accounts to individuals and business.
 Extending loans to individuals and business
 Cashing cheque
 Facilitating money transactions such as wire transfer and cashier’s cheque
 Consumer & commercial financial advisory services
 Financial transactions can be performed through many different channels:
o A branch, banking centre or financial center is a retail location where a
bank or financial institution offers a wide array of face to face services to
customers.
o ATM is computerized telecommunications device that provides a financial
institution’s customers a method of financial transactions in a public space
without the need for a human clerk or bank teller
 o Online banking is a term used for performing transactions , payments etc,
over internet through a bank, credit union or building society’s secure
websites.
We are mainly concerned with developing a banking system where a Customer can submit
his/her deposit amount to bank if he/she has an account or can create a new account in this bank.
Customer can also view the status of his/her bank account, can view account balance, can modify
and delete it.
One can easily maintain the above things if he/she has an account by login through a
username and password given to him

1.3 Analysis of the Problem:

The project that we have undertaken aims to develop a banking system that is clean, user-
friendly and multi-functional. Development of this application includes a number of fields such
that user feels comfortable and the system appears as dynamic to him. The project “Banking
System” includes the following functionalities:
 Transactions can be done with minimum user events.
 All transactional details and accounts are stored in files on stable storage.
 Customers can view their own account details and can use them as necessary
 Customer can inquire an account and can inquire about interest
 All customer’s data are stored in files on a stable storage
 Account holders have to pass through a login system to enter their accounts
 This system possess password-protected administrative access; thus preventing
the whole management system from unauthorized access
 Customer can get help in any time he/she wants
1.4 The Proposed Solution Strategy:
The application will be extremely beneficial for the Customers intending to use and
operate their bank account and will get various benefits in the field of management of accounts
on a clean and user-friendly platform.

 Complex Banking operations and Transaction operations are efficiently handled

by the application
 It is cost effective
 It has ease of use along with complete reference
 It is highly secured and less time consuming; hence time wastage can be avoided
 Up to date records of the customers are maintained by the authority.

SOFTWARE REQUIREMENT SPECIFICATION

2.1 Overall Description:

FOR THE SOFTWARE USED:

TURBO C++
Processor:

 1 GHz PENTIUM Processor (Recommended)

Operating System:

 WINDOWS 2000 SP4

 WINDOWS XP SP3

RAM

 512MB or above

Hard Drive:

 1GB of available space required

2.2 Specific Requirements:

2.2.1 Front End:

 Turbo C ++ Compiler;
 Easier programming & reduced amount of events;
 Declarative programming Model;
 Richer control hierarchy and events;
 Larger class library;
 Better support for development tools;
 Advanced programming language;
 Development environments;
 Programming with C++ is made easier by various built in objects. Each object
corresponds to a group of frequently used functions useful for creating dynamic
environment;
 The compiler runs inside the most familiar Os , i.e. Windows.
 Does not require too much resources for the development of the system;
2.2.2 Back End:

 Databases are saved as a file system on the stable storage;

 Quickly insert, update, or delete data;

PROJECT PLAN
3.1 Life Cycle Model:
 Here in the work, we use EVOLUTIONARY MODEL. This is also referred
to as successive version model of incremental model.

B
B

A A
A

The project is first broken into several modules, such as developing new accounts (A),
developing account modification process (B), and linking between these different features (C)
which can be incrementally constructed. The skeleton is refined into increasing levels of
capability by adding new functionalities in succession.

We have chosen Evolutionary Model because: 1st implement the main feature as account, then
according to requirement step wise implementing is done.

DESIGN
4.1 Architecture of The System:
FOR THE SOFTWARE USED:

Turbo C++
Operating System:
WINDOWS 2000 SP4

WINDOWS XP SP3

4.2 Data Flow Diagram:

A Data Flow Diagram (DFD) is a graphical representation of the “flow” of data through
an information system. A data flow diagram can also be used for the visualization of the data
processing (structured design).

Elements of a DFD:
There are four key elements in a Data Flow Diagram; Processes, Data Flows, Data Stores
& External entities and each element is drawn differently.

Process entity:
The Process entity identifies a process taking place; it must have at least one input and
output. A process with no input is known as a “miracle process” and one with no output is a
“black hole process”. Each process has the following:

 A Number
 A Name
 A Description
 At least one input
 At least one output

Data flow entity:

  The Data Flow Entity identifies the flow of data between processes, data stores &
external entities. A data flow cannot connect an external entity to the data source;
at least one connection must be with a process. There are also physical flows, i.e.,
those that use a physical medium. Each data flow has the following:
 A Name (Noun)
 A description
 One or more connections to a process

Data Store entity:

The Data Store entity identifies store of data, both manual and electronic. Each data store
has the following:

 A Number
 A Name
 A Description
 One or more input data flows
 One or more output data flows.

External entity:

The External entity identifies external entities which interacts with the
system, usually clients but can be within the same organization. Each external
entity has the following:
 A Name (Noun)
 A Description

The different notations to draw DFD are as follows:

Process Data Store

Data Flow

Entity set

BANKING SYSTEM
 0 Level DFD

Banking

System

Manages accounts and software Gives confirmation and work

resources done

Queries information about

current balance, debit, credit,
etc

Admin Customer
Gives confirmation report

Level 1 DFD
Customer Verifies user_id
Admin & password

admin

Process Display Banking

customer Services
request

Admin

Customer

Level 2 DFD

Customer
 Admin

Add record Updata record

View record Loan facilities

accountdets accountdets

account accountdets

Admin

customer

NEW USER AUTHENTICATION

LOGIN PAGE
LOGIN SUCCESSFUL & CHANGING DETAILS OPTION
MAIN WINDOW
CREATE ACCOUNT
RESULT
Testing:
The aim of testing process is to identify all defects existing in our banking software.
However, for most practical system, even after satisfactorily carrying out the testing phase, it is
not possible to guarantee that the software error free. This is because of the fact that the input
data domain of this software product is very large. It is not practical to test the software
exhaustively with respect to each value that the input data may assume. Even with this practical
limitation of testing process, we should not underestimate the importance of testing. We must
remember that testing does expose many defects existing in the software product. Therefore, we
can safely conclude that testing provides a practical way of reducing defects in the system and
increasing the users’ confidence in the developed system.

Testing a program consists of subjecting the program to a set of test inputs (or test cases) and
observing if the program behaves as expected.

We have tested the project by giving the convenient test cases and it has given the expected
results. We have already given it in Design Strategy.

Now we are testing it by giving unfavorable test cases.

1. Suppose in a account, the current balance is less than Rs10000,now if we ask for loan than
loan will not be approved.

Let account number 3 have balance less than Rs 10000. If it apply for loan the following result
will be shown
2. If we enter an invalid account number than it will not be entertained.

Suppose account no 5 does not exist and we want to see the details of the
account .Then it will give the following result.

3. If we ask for loan without having an account then it will show “account not available”.
4. If we want to debit an amount which is more than current balance then the following result
will be shown
 CONCLUSION:

The title of the project is “Banking System” is an application which helps the user to
maintain all the work modules included transactions and managing of accounts of the account
holders which includes a few hitch due to the absence of real time user and runtime application
implementation. Since our first and foremost aim is to satisfy the customer therefore we are
going to continue the use, testing, correction, and up gradation of this application as a
simultaneous procedure.

BIBLIOGRAPHY
 REFERENCES-

 [Link]

 [Link]

 [Link]

 User manual of Co-operative Bank

 User manual of Paschimbanga Gramin Bank

 BOOKS-

 The Complete Reference , C++: Herbert Schildt

 Object oriented programming in Microsoft c++ : Robert

Lafore