Banking Report

A
PROJECT REPORT ON
Banking Management System
Submitted in Partial Fulfillment of the Requirements
for the award of the degree of
BACHELOR OF COMPUTER APPLICATION

(BCA)
Submitted by: Guided Guide :

Dr.Pramod Kumar
Kunal Chauhan(Roll No.190855106094) (Associate Professor
BCA Dept., SRC)
To the
Deptt. Of Computer Application

Shri Ram College of Management,
Muzaffarnagar
SHRI RAM COLLEGE,MUZAFFARNAGAR (U.P)

(Affiliated to Choudhary Charan Singh University, Meerut)
SESSION 2021-22
i
DECLARATION
I hereby declare that the project report title“BANKING MANAGEMENT SYSTEM” is an original
work carried out by us under the supervision of Dr. Pramod Kumar. Further declare that this
work has not been submitted to any other Institute/University for the award of the degree of
Bachelor of Technology.
STUDENT NAME
Kunal Chauhan
Roll No. 190855106094
ii
Forwarding Letter
This is to certify that the project entitled “Banking Management System” which is being
submitted for the partial fulfillment for the award of Bachelor Degree of Computer
Application from Ch. Charan Singh University, Meerut is an authentic work carried out by
Kunal Chauhan (Roll No. 190855106094)
under the guidance of Project Guide Dr. Pramod Kumar.
The matter embodied in this project work has not been submitted earlier for the award of degree
or diploma.
We wish him/her all the best for the future.
Internal Guide Head of Department(HOD)

Dr. Pramod Kumar Mr. Nishant Rathi
iii
ACKNOWLEDGEMENT
This project report on “Banking Management System” is the result of idea and suggestions to me
by Dr. Pramod Sharma.
We have received unfailing encouragement and inspiration of Dr. Pramod Kumar whose
exceptional knowledge and unparalleled behavior is full of ardent inspiration in it. However, we
can never adequate thank all those who have their assistance, guidance, cooperation criticism
contributed to the improvement of this report. We are ebullient in expressing my intense in
debtless heartiest gratitude to all of them.
Since performance feedback is essential for effective communication, mistakes and creative
feedback of the report may be unhesitatingly communicated to me, who will be as far as possible
duly acknowledged and most welcome.
In this report, whatever is beneficial comes from almighty, and whatever is faulty is mine.
Student Signature
Kunal Chauhan (Roll No. 190855106094)
HOD (Head Of Department) Signature
Nishant Rathi
iv
v
PREFACE
“Learning comes from doing.” To learn something, one must go through Practical condition.
Recognizing this fact, the University has made it essential for Bachelor of Computer
Applications (BCA) students to undergo Industrial Training for 10 weeks. During this period,
the student learns about the functioning of the organization and the actual business environment.
Also, this training helps the student how to implement the theoretical knowledge into practical
life, in our day to day life. This project report was prepared during the training period.
During this period, an effort was made to understand BANKING MANAGEMENT SYSTEM and to
finish the project work assigned to us. This report lays special emphasis on the operational work,
task and projects carried out during the training period.
vi
vii
CONTENTS
Contents……………………………………………………………………………….6
Ch.1.Introduction………………………...…………………………………………...7
1.1 Scope of The System…....................................................................................8

1.2 Project Description……………………………………………………………….…………………...9
1.2.1. About existing………………………………………………………………….…….10
1.2.2. Implementation of project ………………………………………….……….11
1.3. Advantages of Project………………………………................................................12
Ch.2.Project category Tools &Environment

2.1 Project Category…………………………………………………….……....13
2.2 Front end Coverage………………………………………………….……...14
2.3 Back end Coverage………………………………………………….….…...15
2.4 Software and Hardware Requirements…………………………….….…….16
Ch.3.Project Development stages

3.1. Recognition of needs…………………………………………..…………...18
3.2 Feasibility Study…………………………………………….….…………..19
3.3. System Analysis (DFD’s E-R Diagram)……………...................................24
3.4. System Development……………………………………….….….………..28
3.5. Testing, Implementation & aintenance………………….………..….….....29
Ch.4.Project form
4.1. Database Design………………….………………………………………….41
8
4.2.Forms………………………………………………………………………...48
4.3. Coding……………………………………………………..….…….……….62
Ch.5.Conclusion ..………………………………………………………….………..120
Ch.6.Future Enhancement ..……………………………………………..................122
Bibliography……………………………………………………………………........123
9
INTRODUCTION
Banking Management System is a tool that It provides efficient services to its Account
and Customer. The various types of operations and dealings take places in the Bank. But
we had undertaken the work of Computerization of Generation of Account Management
System which covers the activities related to Account and Customer etc. & All Types of
activities corresponds to the Member, these operations was manually operated by the
clerks and Operator and the operations were really time consuming task to perform. The
present system will help them a lot.
MAIN OBJECTIVE OF THIS PROJECT:
1. To provide security as only an authorized employee can interact with the system.
2. To help the customer working easily and efficiently.
3. To help the customer in reducing errors that are encountered frequently during
manual operations by concurrently updating the data stored in many places.
4. To reduce the workload on the staff by providing automatic calculation.
5. To help the customer or manager in tracing the transaction quickly.
6. To help the customer in generating various reports at various nick of time as per
their requirements e.g. daily, weekly, monthly or annually.
7. To reduce the manpower.
8. To maintain the data with complete consistency and minimum redundancy.
10
1.1 SCOPE OF THE SYSTEM
The scope of this document includes an overview of the BANKING

MANAGEMENT SYSTEM project, detailed information about the
requirements, including functional requirements, interface requirements, non-
functional requirements and additional constraints of the system.
1. There are three basic users – customer, employee, Admin.
2. All users have their own profile in this project.
3. Customer can search for open new account. They also can take loan from the
bank
4. Bank can give loan and can view account’s record.
5. Admin views and manages the customer and employee.
11
1.2 PROJECT DESCRIPTION
Today computer has become the backbone of nearly every occupation. In every
industry or company or any institution, the several employees have to maintain a
number of records in various part of the organization. In a market, there is a need
to maintain record about employees, edibles, assets & many more.
To do this work manually requires a lot of manpower and consumes too much time.
Moreover one is never sure about the efficiency & accuracy of work being done and
records being maintained. A bad part of this style of working is that, if a person
concerned for a particular job, say maintaining supplier record, is on leave, some of the
process gets standstill, which depends on the records kept by that employee. That is,
where automation comes in to help and allows simple, smooth and most efficient, secure
and easy to handle functionality.
This system will reduce the workload of the employee and time of processing of data
from one unit to another. It also will help the staff/manager in tracing the daily
transaction & maintain staff record, asset information to reduce the manpower. It also
provides the facility to prevent the unauthorized data access of other persons by
categorized the user as normal user and administrator. Only administrator can delete &
even modify the records.
This system will prove to be master key to manage of a bank. Now days all the
organizations are converting from manual to computerized transactions. This
provides better services to the employees with less effort thus increasing the
demand of this type of system day by day.
This has brought about marvelous changes in the life of human being and has
made our life easy & comfortable. It has revolutionized the whole era.
This project “BANKING MANAGEMENT SYSTEM” will help the customer & stands at
their account in every sphere of their activities regarding a taking loan. It will be
always their back & call.
12
13
1.2.1ABOUT EXISTING SYSTEM
In the general account of the customers, there are many of problems are faced . Some of
these problems can be managed easily, but some of them have many challenging work
when employee can faced that.
Some of these challenges in the general bank can be figure-out as:-
 Difficulty with the record keeping.

 Managing of all records.
 Difficulty to creation of many other recording files for records.
 All record can’t be placed in single way nature.
All of these type’s challenges can be easily generate in a general and manually operated
costumer record..
14
1.2.2 IMPLEMENTATION OF PROJECT
A crucial phase in the system life cycle is the successful implementation of the
new system design. Implementation includes all those activities that take place to
convert from the old system to tee new one. The new system may be completely
new, replacing an existing system. In either case, proper implementation
becomes necessary so that a reliable system based on the requirements of the
organization can be provided. Successful implementation may not guarantee
improvement in the organization using the new system , but improper installation
will prevent it. It has been observed that even the best system can’t show good
result if the analysts managing the implementation do not attend to every
important details. This is an area where the systems analysts need to work with
utmost care. This system will be implemented using java netbeans as front end
and MS-Access as back end windows 98 a the platform.
For the successful implementation of a system, the training of the users of the
system plays an important role. Because even well designed system can
succeed or fail because of the way they are operated and used. Therefore, the
quality of the training received by the personnel involved with the system in
various capacities helps or hinders and may even prevent the successful
implementation of management information system. Those who are directly or
indirectly related with the system development work must know in detail what
their roles will be , how they can ace efficient use of the system and what the
system will or will not do for them. Therefore both system operators and users
need training.
15
1.3 ADVANTAGE OF PROJECT
SPEED:
They understand the importance of timing, of getting there before the competition. A
rich portfolio of reusable, modular frameworks helps jump-start projects. Tried and
tested methodology ensures that we follow a predictable, low - risk path to achieve
results. Our track record is testimony to complex projects delivered within and evens
before schedule.
EXPERTISE:
Our teams combine cutting edge technology skills with rich domain expertise. What’s
equally important - they share a strong customer orientation that means they actually start
by listening to the customer. They’re focused on coming up with solutions that serve
customer requirements today and anticipate future needs.
A FULL SERVICE PORTFOLIO:

They offer customers the advantage of being able to Architect, integrate and manage
technology services. This means that they can rely on one, fully accountable source
instead of trying to integrate disparate multi vendor solutions.
SERVICES:
It Asset Manager is providing it’s services to companies which are in the field of
production, quality control etc With their rich expertise and experience and information
technology they are in best position to provide software solutions to distinct business
requirements.
16
Ch 2 PROJECT CATEGORY & ENVIRONEMENT
2.1 Project Category & Development
Today computer has become the backbone of nearly every occupation. In every
industry or company or any institution, the several employees have to maintain a
number of records in various part of the organization. In a market, there is a need
to maintain record about employees, edibles, assets & many more.
To do this work manually requires a lot of manpower and consumes too much time.
Moreover one is never sure about the efficiency & accuracy of work being done and
records being maintained. A bad part of this style of working is that, if a person
concerned for a particular job, say maintaining customer record, is on leave, some of the
process gets standstill, which depends on the records kept by that employee. That is,
where automation comes in to help and allows simple, smooth and most efficient, secure
and easy to handle functionality.
This system will reduce the workload of the employee and time of processing of data
from one unit to another.It also provides the facility to prevent the unauthorized data
access of other persons by categorized the user as normal user and administrator. Only
administrator can delete & even modify the records.
17
FRONT END
JAVA used as FRONT END
Java uses front end programming because JAVA use back end as like
ACCESS DATABASE.
18
BACK END
Back end
Microsoft Access-2007
19
2.4 Software and Hardware Requirements
Hardware Requirements:
Processor : Pentium 4 or above

Memory : 512MB RAM or above
Hard disk : 20MB
Keyboard : 104 keys
Microsoft Access : 2007
Software Requirements:
Operating System : Windows XP/2003 or Linux/Solaris

Programming Language : Java
Database Applications : JDBC
Database : MS-Access
Netbeans : 7.4
20
21
3.1 ROCOGNITION OF NEEDS
We all know the importance of computerization. The world is moving ahead at lightning
speed and everyone is running short of time. One always wants to get the information and
perform a task he/she/they desire(s) within a short period of time and too with amount of
efficiency and accuracy. The application areas for the computerization have been selected
on the basis of following factors:
1 Minimizing the manual records kept at different locations.

2 There will be more data integrity.
3 Facilitating desired information display, very quickly, by retrieving information from
users.
4 Facilitating various statistical information which helps in decision-making?
5 To reduce manual efforts in activities that involved repetitive work.
6 Updating and deletion of such a huge amount of data will become easier.
22
3.2 FEASIBILITY STUDY
SYSTEM ANALYSIS
Systems analysis refers to the process of examining a business situation with the intent of
improving it through better procedure and methods. Systems development can generally
be thought of as having two major components Systems Analysis and Systems Design.
Systems analysis is the process of gathering and interpreting facts, diagnosis problems
and using the information to recommend improvement to the system. In brief, we can say
that analysis specifies what the system should do.
System analysis is conducted with the following objectives in mind:
1. Identify the Student and Staff members need
2. Evaluate the system concept for feasibility
3. Perform economic and technical analysis
4. Allocate function to hardware, software, people, database and other system elements
5. Establish cost and schedule constraints
6. Create a system definition that forms the foundation for all subsequent engineering
FEASIBILITY STUDY
The concept of feasibility is to determine whether or not a project is worth doing.
The process followed in making this determination is called feasibility study.
Once it has been determined that a project is feasible, the system analyst can go ahead
and prepare the project specification which finalizes project requirements.
23
Types of feasibility
1. Technical Feasibility
2. Operational Feasibility
3. Economic Feasibility
4. Social feasibility
5. Management Feasibility
6. Legal Feasibility
7. Time Feasibility
Here we describe only few of these in detail:-
TECHNICAL FEASIBILITY
This is concerned with specifying equipment and software that will successfully
satisfy the user requirement. Technical needs of the system include:-
 Facility to produce output in a given time

 Response time under certain conditions
 Ability to process a certain volume of transactions at a particular period
 Facility to communicate data to distant location
In examining technical feasibility, configuration of the system is given more importance

than the actual make of hardware .Configuration should give the complete picture about
the system’s requirements: how many workstations are required , how these units are
interconnected so that they could operate and communicate smoothly. What speeds of
input and output should be achieved at particular quality of printing.
The computers are easily available in almost all the places, even in villages. The
hardware needed to carry out this project with 64 MB of RAM and 2 GB HDD.
24
The software needed to carry out this project include Visual Basic 6.0 as front end and
oracle 8 as back end .So the technology required to carry out the project is easily
available and affordable, hence this project is technically feasible.
Due to all these reasons implementation of such system becomes not only feasible but
reputed to the organization..
OPERATIONAL FEASIBILITY
This is mainly related to human organization and political aspects. The points to be
considered are:-
 What changes will be brought with the system?

 What organizational structures are disturbed?
 What new skills will be required? Do the existing staff members have these
skills?
If not, they be trained in due course of time.
This feasibility study is carried out by a small group of people who are familiar with the
information system techniques who understand the parts of business that are relevant to
the project and are skilled in the system analysis and design process. This project is not
developed just for fun. They are developed on demand of the organization for which the
system is being developed. Therefore the chances of resistance from the company Staff is
almost nil. Any disturbance to the organization if occurs will be advantageous to the
organization. Also the time required to carry out a transaction will be required to a large
extent, which will make the students and others happy and cheerful. The operators now
will be able to service more students and staff members than before in same time period.
There is no need to recruit new staff to corporate the system .The existing staff of the
company can be trained to interact with the system, which is a GUI, based software and is
easy to use. Hence the project is Operationally feasible.
25
ECONOMIC FEASIBILITY
Economic analysis is the most frequently used technique for evaluating the effectiveness
of a proposed system. More commonly known as cost-benefit analysis; the procedure is
to determine the benefits and savings that are expected from a proposed system and
compare them with costs. If benefits outweigh costs, a decision is taken to design and
implement the system.
Cost-Benefit Analysis
Since cost plays an important role in deciding the new system, it must be identified
and estimated properly. Benefits are also of different types and can be grouped on the
basis of advantages they provide to the management.
Cost-saving benefit leads to reduction in administrative and operational costs.

Cost-avoidance benefit eliminate future administrative and operational costs.
Improved-service-level benefits are those where the performance of the system is
improved by a new computer based method e.g. servicing a student in two minutes rather
than five to ten minutes is an example of this type of benefit. Improved-information
benefits is where computer based methods lead to better information for decision-
making.
Direct Or Indirect Costs And Benefits
Direct costs are those which are directly associated with a system. They are applied
directly to the operator.
Direct benefits also can be specifically attributable to a given project.
Indirect costs not directly associated with a specific activity in the system. They are
often referred to as overhead expenses.
For example cost of space to install a system, maintenance of computer centre.
26
Heat ,light and air-conditioning are all tangible costs but their proportion is difficult to
calculate to a specify activity like report.
Indirect benefits are realized as by –products of another system.
We can define cost-benefit analysis as:-
1. That method by which we can estimate the value of the gross
benefits of a new system specification.
2. That method by which we find and determine the increased
operating costs associated with the gross benefits.
3. The subtraction of these operating costs from the associated gross
benefits to arrive at net benefits.
4. That method by which we find and estimate the monetary value of
the development costs that produce the benefits.
5. Those methods by which we show the time –relationship between

net benefits and development costs as they relate to cash flow ,payback on investment,
and time-in process taking into operation factors such as inflation etc.
COST ESTIMATON OF THE PROJECT
The primary reason for cost and schedule estimation is to enable the client or developer
to perform a cost-benefit analysis and for project monitoring and control . Cost and
schedule estimates are also required to determine the staffing level for a project during
different phases.
Cost in a project is due to the requirements for software hardware and human resource.
Hardware resources are such things as the computer time, terminal time and memory
required for the project. whereas software resources include the tools and the compilers
needed during development. The bulk of the cost of software development is due to the
human resources needed , and most cost estimation procedures focus on this aspect. Most
of the estimates are determined in terms of person-months(PM)
27
3.3 DATA FLOW DIAGRAM
0 Level DFD
VENDOR PRODUCT
STOCK
MANAGEMENT
PURCHASE LOGOUT
SYSTEM
SALES
28
LOGIN MANAGEMENT CHECK USER LOGIN
VENDOR GENERATE
MANAGEMENT CUSTOMER REPORT
t
OWNER
STOCK EMPLOYEE REPORT
MANAGEMENT
MANAGEMENT
ACCOUNT ACCOUNT
SYSTEM
CHECK AVAILBLITY
AVAILABILITY
REPORT
SYSTEM USER
GENERATE SYSTEM
MANAGEMENT
REPORT
t
FIRST LEVEL DFD -ELECTRICITY BILL SYSTEM
29
CHECK
LOGIN ROLL OF
TO USER LOGIN
ACCESS
SYSTE
M
OWNER VENDOR
REPORT
STOCK OWNER EMPLOYEE

REPORT
CHECK MANAGEMENT
CREDENTIAL MANAG ACCOUNT
SYSTEM
S REPORT
MANAGE SYSTEM
REPORT
OWNER USER PERMISSION
SECOND LEVEL DFD -ELECTRICITY BILL SYSTEM
30
ENTITY – RELATIONSHIP DIAGRAM
Accno
Age Phon
Address e
Date Name
Email
ACCOUNT
CUSTOMER
Type check
Date
contains
Cid
has
ONLINE
APPOINTMENT
Has
Department Loan
Amount
Dtae due
Acc No.
DID Phone No. Email ID Date

Name 31
issue
Loan
type
3.4. SYSTEM DEVELOPMENT
Software development is a complex process so we divide the process in a small

module. These modules are called system development phases. These phases
are combined known as system development life cycle. These linear cycle
phases are given below: -
i. Recognition of Needs: - It includes preliminary survey and initial investigation by

personnel interviews and questionnaires.
ii. System Analysis: - Detailed evaluation of present system and data collection is
done. The various reports and documents used are studied in detail. After that the
interview of various levels of management is carried out. The DFD. Data dictionary,
Menu chart are the tools used for it.
iii. System Design: - It involves general and detailed design specification, output, input
files, files, program construction plans, all these details are submitted to user and got
signed.
iv. System Construction: - It involves implementation of total construction plan i.e.

coding. It is done in a language i.e. known to user, analyst and programmer.
v. Testing: - Each and every input and output program is executed separately and
tested for bugs. Whole of the system is executed and test data is prepared and is fed
in to the system and the output reports are compared with the parameters.
vi. Implementation: -It checks that users requirement are fulfilled or not.
Response time is checked and finally the user manual is prepared and
is submitted.
32
3.5 TESTING, IMPLEMENTATION AND MAINTENANCE
During system testing, the system is used experimentally to ensure that the software does
not fail. Specific test data are input for processing, and the results examined. It is
desirable to discover any surprises before the organization implements the system and
depends on it.
TESTING OBJEC TIVES:
1. Testing is a process of executing a program with the intent of finding an error.

2. A good test case is one that has a high probability of finding an as yet undiscovered
error.
3. A successful test is one that uncovers an as yet undiscovered error.
TESTING PRINCIPLES:
1. All tests should be traceable to the student and staff member’s requirements.
2. Tests should be planned long before the testing begins.
3. Testing should begin “in the small” and progress towards “in the large”.
4. Exhaustive testing is not possible.
5. To be most effective, testing should be conducting by an independent third party.
TESTING FUNDAMENTALS:
In software development project, errors can be injected at any stage during development.
Because code is the only product that can be executed frequently and who’s actual
behavior can be observed testing is the phase where the remaining errors from all the
previous phases must be detected. Testing performs a critical role for quality assurance
and for ensuring the reliability of the software. During testing, the program to be tested is
executed with a set of test cases, and the output of the program for the test cases is
evaluated to determine if the program is performing as expected. Due to this approach,
33
dynamic testing can only ascertain the presence of errors in the program; the exact nature
of errors is not usually decided by testing.
Testing a large system is a complex activity, so for a project incremental testing is

generally performed, in which components and subsystems of the system are tested
separately before integrating them to form the system for system testing. This form of
testing introduces new issues of how to select components and how to combine them to
from systems and subsystems
ERROR
It refers to the discrepancy between a computed, observed, or measured value and true,
specified or theoretically correct value i.e. it refers to the difference between the actual
output of the software and the correct value.
FAULT
It is a condition that causes system to fail in performing its required functions. A fault is
the basic reason for software null function and is synonymous with the commonly used
term bug.
FAILURE
It is the inability of a system or components to perform a require functions according to

its specification. A software Failure occurs if the behavior of the software is different
from the specified behavior. Faults have the potential to cause failures and their presence
is a necessary but not sufficient condition for failure to occur.
TEST CASES AND TEST CRITERIA
Ideally, we would like to determine a set of test cases such that successful execution of
all of them implies that there are no errors in the program. This ideal goal can’t usually
34
be achieved due to practical and theoretical constrains. Each test case costs money, as
effort is needed to generate the test case, machine time is needed to execute the program
for that test case, and more effort is needed to evaluate the results.
An ideal test case set is one that succeeds if there are no errors in the program. One
possible ideal set of test cases is one that includes all the possible inputs to the program.
This is often called exhaustive testing, however it is impractical and infeasible.
For a given program P and its specification S, a test selection criterion specifies the
condition that must be satisfied by a set of test cases. T for example, if the criterion is that
all statements in the program be executed at least one during testing, then a set of test
cases T satisfied this criterion for a program P is the execution of P with T ensures that
each statement in P is executed at least once.
There are two fundamental properties for a testing criterion: reliability and validity. A
criterion is reliable if all the set of test cases that satisfied the criterion detect the same
errors. A criterion is valid if for any error in the program there is some set satisfying the
criterion that will reveal the error.
Testing can be mainly of two types:
When we know the specified function that a product has been designed to perform, test
can be conducted that demonstrates each function is fully operational while at the same
time searching for errors in each function. A black box test examines some fundamental
aspects of a system with little regard for the internal logical structure of the software.
Black box testing also called behavioral testing, focuses on the functional requirements of
the software. Black box testing attempts to find errors in the following categories:
1. Incorrect or missing functions.

2. Interface errors.
3. Errors in data structures or external database access
4. Behavior or performance errors.
5. Initialization and termination errors.
35
WHITE BOX TESTING
When we know the internal workings of a product, tests can be conducted to ensure that
internal operations are performed according to specifications and all internal components
have been adequately exercised. This is testing is sometimes called as glass box testing.
Using white box testing methods, the software engineer can derive test cases that…
1. Guarantee that all independent paths within a modules have been exercised at least
once.
2. Exercise all logical decisions on their true and false sides.
3. Execute all loops at their boundaries and within their operational bounds.
4. Exercise internal data structures to ensure their validity.
In this project our main emphasis is on white box testing.
In order to test loops, we used the loop testing technique which is a white box testing
technique. Most of loops used in this project belong to the category of simple loops.
We applied the following set of tests to loops, where n is the maximum number of
allowable passes through the loop.
1. Skipped the loop entirely.

2. Allowed only one pass through the loop.
3. Allowed to passed through the loop.
4. Allowed m passed through the loop where m<n.
5. Allowed n-1, n, n+1 passes through the loop.
In order to test the control flow structures such as if conditions etc. we used the condition
testing technique . The condition testing method focuses on testing each condition in the
program. Condition testing strategies have two advantages. First, measurement of test
coverage of a condition is simple. Second, the test coverage of conditions in program
guidance for the generation of additional tests for the system. Branch testing is the
simplest condition testing strategy. For a compound condition C which is composed of
36
two or more simple conditions, Boolean operators and parenthesis, the true and false
branches of C and every simple condition in C need to be executed at least once.
BOUNDARY VALUE ANALYSIS:
For reason that are not completely clear, a greater number of errors tend to occur at the
boundaries of the input domain rather than in the ‘center’. It is for this reason that
boundary value analysis has been developed as a testing technique. Boundary value
analysis leads to a selection of test cases that exercise bounding values. We used this
approach to test several control statement in our project.
Guidelines for boundary value analysis are as follows:
If an input condition specifies a range bounded by values a and b, test cases should be
designed with values a and b just above and below a and b.
If an input condition specifies a number of values, test cases should be developed that
exercise the minimum and maximum numbers. Values just above and below minimum
and maximum are also tested.
Apply the same guidelines to output conditions.
If internal program data structures have prescribe boundaries, be certain to design a test
cases to exercise the data structures at its boundary.
FUNCTIONAL TESTING:
In functional testing the structure of the program is not considered. Test cases are decided
solely on the basis of the requirements or specifications of the program or module, and
the internal of module or the program are not considered for selection of test cases. Due
to its nature, functional testing is often called “ black box testing “.
37
STRUCTURAL TESTING:
In the structural approach, test cases are generated based on the actual code of the
program or module to be tested. This structural approach is sometimes called “glass box
testing”.
UNIT TESTING:
In this different modules are tested against the specifications produced during design for
the modules. Unit testing is essentially for the verification of the code produced during
the coding phase and its goal is to test the internal logic of the modules. It is typically
done by the programmer of the module. Structural testing is best suited for this level.
In our project each form works like a unit. Some forms are used to display the data stored
in the database and some forms are user to submit data to the database. Before submitting
the data to the database, it is tested individually using front end capabilities. The tests that
occurred as part of the unit tests are as follows:
The module interface was tested to ensure that information properly flows into and out of
the program unit under test.
The local data structures were examined to ensure that data stored temporarily maintains
its integrity during all steps in an algorithm’s execution.
Boundary conditions were tested to ensure that the module operates properly and
boundaries established to limit or restrict processing.
All independent paths through the control structure were exercised to ensure that all
statements in a module have been executed at least once.
Finally, all errors handling paths were tested.
INTEGRATION TESTING:
38
Integration technique is a systematic technique for constructing the program
structure while at the same time conducting tests to uncover errors associating
with interfacing. The objective is to take unit tested components and build a
program structure that has been dictated by design.
Integration can be either top down or bottom down.
Top down integration testing is an incremental approach to construction of

program structure. Modules are integrated by moving downward through the
control hierarchy, beginning with the main control module. Modules subordinate
to the main control module are incorporated into the structure in either a depth
first or breadth first manner.
Bottom up integration testing begins construction and testing with atomic

modules (i.e. components at the lowest levels in the program structure). Because
components are integrated from the bottom up, processing required for
components subordinate to a given level is always available and the need for stubs
is eliminated.
In our project, we have used the bottom up approach. When all the forms were
tested independently, they were integrated to form a module.
REGRESSION TESTING:
0Each time a new module is added as part of integration testing, the software
changes. New data flow paths are established, new I/o may occur, and new
control logic is invoked. These changes cause problems with functions that
previously worked flawlessly. In the context of an integration test strategy,
regression testing is the re-execution of some subset of tests that have already
been conducted to ensure that changes have not propagated unintended side
effects. Regression testing was used frequently in our project.
VALIDATION TESTING:
39
At the culmination of integration testing, software is completely assembled as a package,
interfacing errors have been uncovered and corrected, and a final series of software tests-
validation testing –may begin. Validation can be defined in many ways. But a simple
definition is that validation succeeds when software function in a manner that can be
reasonably expected by the student and staff members.
SYSTEM AND ACCEPTANCE TESTING:
System testing is actually a series tests, whose primary purpose is to fully exercise the
computer baed systems. Although each test has s different purpose, all work to verify that
system elements have been properly integrated and performed allocated functions. The
following types of system tests are worthwhile for software based system : recovery
testing , security testing, stress testing, performance testing. At this level of testing, the
entire software system is testing, performance testing .
In general, testing commences with a test plan and terminates with acceptance testing. A
test plan is a general document for the entire project that defines the scope, approaches to
be taken, and the schedule of testing as well as identifies the test items for the entire
testing process and the personnel responsible for different activities of testing.
The inputs for forming the test plan are: -
1. Project plan
2. Requirement Document
3. System Design Document
The project plan is needed to make sure that the test plan is consistent with the overall
plan for the project and the testing schedules matches that of the project plan.
The requirement document and the design document are the basic documents used for
selecting the test units and deciding the approaches to be used for testing. A test plan
should contain the following testing:-
 Test unit specification
40
 Features to be tested
 Approaches for testing
 Test deliverables
 Schedule
 Personnel allocation
TEST UNIT:
A test unit is a set of one or more modules together with associated data that are form a
single computer program and that are the objects of testing.
FEATURES TO BE TESTED:
It includes all software features and combination of features that should be tested. A S/W
feature is a software characteristic specified or implied by the requirements or design
documents. These may include functionally, performance, design constraints, and
attributes.
APPROACH FOR TESTING:
It specifies the overall approach to be followed in the current project. The techniques that
will be used to judge the testing effort should also be specified.
TESTING DELIVERABLES:
Testing deliverables should be specified in the test plan before the actual testing begins.
Deliverables could be a list of test cases that were used, detailed results of testing, test
summary report, test log and data about coverage.
SCHEDULE:
A schedule specifies the amount of time and effort to be spent on different activities of
testing, and testing of different units that have been identified.
41
PERSONNEL ALLOCATION:
It identifies the persons responsible for performing the different activities.
SYSTEMS OPERATORS TRAINING:
Running of the system successfully depend on the personnel working in the

computer center. They are responsible for providing the necessary support. Their
training must ensure that they are able to handle all possible operations, both
routine and extra-ordinary in nature. Operators training should include such
fundamentals as how to turn the equipment on and use it, how to power off and a
knowledge of what constitutes normal operation. The operators should also be
trained on different type of malfunctioning, how to recognize them and what steps
should be taken whenever they arise. As part of their training, operators should
be given both a troubleshooting list that identifies possible problems and
remedies for them , as well as the names and telephone numbers of individuals
to contact when unexpected or unusual problem arise. Training also involves
familiarization with run procedures, which involves working through the sequence
of activities needed to use a new system on an ongoing basis.
USER TRAINING
User may be trained on use of equipment, particularly in the case where, for
example, a Microcomputer is in use and the individual involved is both operator
and user. In such cases, user may be trivial to the analyst, such as how to turn
off the equipment without danger of data loss, are significant problems to new
user who are not familiar with computers. This is also the case with our system.
In most of the cases, user training deals with the operation of the syste itself, with
properly trained of entering transactions, editing data, formulating inquiries,
deleting and inserting of records. No training is complete without familiarizing
user with simple systems maintenance activities. Weakness in any aspect of
training may lead to awkward situations that cause user frustration and errors.
42
In our project also it is necessary to train users on how to commit the
transactions . Training of operators and users can be organized in several
different ways. Most important ways to train users are:
 Vendor and in-service training

 In –house training

Often the best source of training on equipment is the vendor who supplies the
equipment. Most vendors offer extensive educational programs as part of their
services. In the case of our project too, we’ll provide training to the users of the
project.
Conversions is also important in the implementation phase. Conversion is the
process of changing from the old system to the new one. It must be properly
planned and executed.
Four methods of conversions are common in use. They are:
1. Parallel systems
2. Direct conversion
3. Pilot systems
4. Systems phase-in
Each method should be considered in the light of the opportunities that it offers
and problems that it may create. However , it may be possible that sometimes ,
we be forced to apply one method over others, even though other methods over
others, even though other methods may be more beneficial . In general ,systems
conversions should be accomplished in shortest possible time . Long conversion
periods create problems for all persons for all persons involved including both
analysts and users.
43
PARALLEL SYSTEMS:
The most secure method of converting from an old to new system is to run both
systems parallel. Under this approach, users continue to operate the old system
in the usual manner but they also start using the new system. This method is the
safest one.
DIRECT CONVERSION:
This method converts from the old systems to the new system abruptly,
sometimes over a weekend or even midnight. The old system is used until a
planned conversion day , when it is replaced by the new system. There are not
parallel activities.
PILOT SYSTEM:
Pilot approach is often preferred in the case of the new system which involves
new system which involves new techniques or some drastic changes in
organization performance. In this method , a working version of the system is
implemented in one part of the organization, such as a single work area or
department.
PHASE-IN METHOD:
This method is used when it is not possible to install a new system throughout an
organization all at once. It allows some users to take advantage of the new
system early. Also it allows training and installation without unnecessary use of
resources.
44
The project developed by us should be implemented using the parallel systems
conversion method.
45
DATABSE DESIGN
Login table
New User table
Account table
46
Employee table
47
Pay Salary table
Department table
Transaction table
48
ATM table
Loan table
49
50
LOGIN FORM
Welcome form
51
MAINFORM
52
ADD NEW ACCOUNT
53
EDIT ACCOUNT ENTRY
54
DEPOSIT AMOUNT
55
WITHDRAWFORM
56
LIST OF ACCOUNT
57
LIST OF WITHDRAW
58
LIST OF DEPOSIT
59
CHANGE PASSWORD
60
61
LOGIN FORM
package bankingproject;
import java.sql.*;
import javax.swing.*;
private void loginbtnActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
String user1,user2,pass1,pass2;
user1=txtuser.getText();
pass1=txtpassword.getText();
try {
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection con=DriverManager.getConnection("jdbc:odbc:bank");
Statement stmt=con.createStatement();
String query="select * from logintable";
ResultSet res=stmt.executeQuery(query);
res.next();
user2=res.getString("username");
pass2=res.getString(2);
if(user1.equals(user2) && pass1.equals(pass2))
{
this.hide();
Splash_form obj=new Splash_form();
obj.show();
}
else
JOptionPane.showMessageDialog(null,"incorrect");
} catch(Exception e) {
}
}
private void cancelbtnActionPerformed(java.awt.event.ActionEvent evt) {
System.exit(0);
}
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new Lloginform().setVisible(true);
}
});
}
62
Splash form
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
mainform obj=new mainform();
obj.show();

public void run() {
new Splash_form().setVisible(true);
}
});
}
private void savebtnActionPerformed(java.awt.event.ActionEvent evt) {

int accountno,age,contact,gno,balance;
String name,accounttype,gender,idproof,email,gname,address;
accountno=Integer.parseInt(accounttxt.getText());
age=Integer.parseInt(txtage.getText());
gno=Integer.parseInt(txtgno.getText());
balance=Integer.parseInt(txtbalance.getText());
name=holdertxt.getText();
accounttype=typetxt.getText();
gender=combo.getSelectedItem().toString();
idproof=idtxt.getText();
email=emailtxt.getText();
gname=guaranternametxt.getText();
address=txtaddress.getText();
contact=Integer.parseInt(txtcontact.getText());
try {
String query="insert into Account_table
values("+accountno+",'"+name+"','"+accounttype+"',"+age+",'"+gender+"',"+contact+",'"
+idproof+"','"+email+"',"+gno+",'"+gname+"','"+address+"',"+balance+")";
stmt.executeUpdate(query);
JOptionPane.showMessageDialog(null,"successfully saved");
JOptionPane.showMessageDialog(idtxt, e.getMessage());
63
}
private void nextbtnActionPerformed(java.awt.event.ActionEvent evt) {

txtcontact.setText("");
txtage.setText("");
txtgno.setText("");
holdertxt.setText("");
typetxt.setText("");
idtxt.setText("");
emailtxt.setText("");
guaranternametxt.setText("");
txtaddress.setText("");
txtbalance.setText("");
holdertxt.requestFocus();
}
private void exitbtnActionPerformed(java.awt.event.ActionEvent evt) {

this.hide();
}
private void formWindowActivated(java.awt.event.WindowEvent evt) {

int accno=300000;
try {
String query="select * from account_table";
while(res.next())
{
accno=Integer.parseInt(res.getString(1));
}
accounttxt.setText(String.valueOf(accno+1));
accounttxt.setEnabled(false);
}
}
64
public void run() {
new Accountform().setVisible(true);
}
});
}

try {

txtage.setText("");
txtgno.setText("");
65
try {

txtage.setText("");
txtgno.setText("");
idtxt.setText("");
66
}

this.hide();
}

int accno=300000;
try {
while(res.next())
{
}
}
}

public void run() {
}
});
}

67
try {

txtage.setText("");
txtgno.setText("");
idtxt.setText("");
}

this.hide();
}
68
int accno=300000;
try {
while(res.next())
{
}
}
}

public void run() {
}
});
}

69
try {

txtage.setText("");
txtgno.setText("");
idtxt.setText("");
}

this.hide();
}

int accno=300000;
try {
70
while(res.next())
{
}
}
}

public void run() {
}
});
}

try {
71

txtage.setText("");
txtgno.setText("");
idtxt.setText("");
}

this.hide();
}

int accno=300000;
try {
while(res.next())
{
}
72
}
}

public void run() {
}
});
}
idtxt.setText("");
}

this.hide();
}

int accno=300000;
try {
while(res.next())
{
}
73
}
}

public void run() {
}
});
}

try {
74
}

txtage.setText("");
txtgno.setText("");
idtxt.setText("");
}

this.hide();
}

int accno=300000;
try {
while(res.next())
{
}
}
}
75
public void run() {
}
});
}

try {

txtage.setText("");
txtgno.setText("");
76
idtxt.setText("");
}

this.hide();
}

int accno=300000;
try {
while(res.next())
{
}
}
}

public void run() {
}
});
}
77
MainForm
private void jMenuItem1ActionPerformed(java.awt.event.ActionEvent evt) {
Accountform obj=new Accountform();
obj.show();
}

Edit_account obj=new Edit_account();
obj.show();
}

List_of_account obj=new List_of_account();
obj.show();
}

Depositform obj=new Depositform();
obj.show();
}
Withdrawform obj=new withdrawform();
obj.show() }

Passwordchange obj=new Passwordchange();
obj.show();
}

list_of_withdraw obj=new list_of_withdraw();
obj.show();
private void jMenu2ActionPerformed(java.awt.event.ActionEvent evt) {

list_of_withdraw obj=new list_of_withdraw();
obj.show();
}
78
list_of_deposit obj=new list_of_deposit();
obj.show();
}

System.exit(0);
}
79
ACCOUNT FORM
import java.sql.*;

try {

txtage.setText("");
txtgno.setText("");
80
idtxt.setText("");
}

this.hide();
}

int accno=300000;
try {
while(res.next())
{
}
}
}

public void run() {
}
});
}

81
try {

txtage.setText("");
txtgno.setText("");
idtxt.setText("");
}
82
this.hide();
}

int accno=300000;
try {
while(res.next())
{
}
}
}

public void run() {
}
});
}

83
try {

txtage.setText("");
txtgno.setText("");
idtxt.setText("");
}

this.hide();
}

int accno=300000;
try {
84
while(res.next())
{
}
}
}

public void run() {
}
});
}

try {
85

txtage.setText("");
txtgno.setText("");
idtxt.setText("");
}

this.hide();
}

int accno=300000;
try {
while(res.next())
{
86
}
}
}

public void run() {
}
});
}

try {
87

txtage.setText("");
txtgno.setText("");
idtxt.setText("");
}

this.hide();
}

int accno=300000;
try {
while(res.next())
{
}
88
}
}

public void run() {
}
});
}
89
DEPOSIT FORM
import java.sql.*;
private void verifyActionPerformed(java.awt.event.ActionEvent evt) {
try{
int accno=Integer.parseInt(combo.getSelectedItem().toString());
String query="select * from Account_table where accountno="+accno;
if(res.next())
{
txtname.setText(res.getString("hname"));
txtname.setEnabled(false);
deposit.setEnabled(true);
}
else
JOptionPane.showMessageDialog(null, "ïnvalid account number");
}
catch(Exception e)
{}
}
private void depositActionPerformed(java.awt.event.ActionEvent evt) {
int accountno,amount=0,amount2=0;
String ddate;
if(txt2.getText().equals(""))
JOptionPane.showMessageDialog(rootPane, "Mention date");
else if(txt3.getText().equals(""))
JOptionPane.showMessageDialog(rootPane, "fill amount");
else{
accountno=Integer.parseInt(combo.getSelectedItem().toString());
ddate=txt2.getText();
amount=Integer.parseInt(txt3.getText());
try{
con=DriverManager.getConnection("jdbc:odbc:bank");
stmt2=con.createStatement();
90
String query="insert into deposit
values("+accountno+",'"+ddate+"',"+amount+")";
stmt2.executeUpdate(query);
stmt=con.createStatement();
String q="select * from account_table where accountno="+accountno;
ResultSet res=stmt.executeQuery(q);
if(res.next())
{
amount+=Integer.parseInt(res.getString("balance"));
String q2="update account_table set balance="+amount+" where
accountno="+accountno;
stmt.executeUpdate(q2);
JOptionPane.showMessageDialog(null,"Amount deposited");
}
txt2.setText("");
txt3.setText("");
txtname.setText("");
combo.removeAllItems();
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
91
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
92
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
93
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
94
txt2.setText("");
txt3.setText("");
}catch(Exception e)
{
JOptionPane.showMessageDialog(null,e.getMessage());
}
}
private void backActionPerformed(java.awt.event.ActionEvent evt) {

this.hide();
}

public void run() {
new Depositform().setVisible(true);
}
});
}
95
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}catch(Exception e)
{
}
}

this.hide();
}

public void run() {
}
});
}
96
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}catch(Exception e)
{
}
}

this.hide();
}

public void run() {
}
});
}
97
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}catch(Exception e)
{
}
}

this.hide();
}

public void run() {
}
});
}
98
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}catch(Exception e)
{
}
}

this.hide();
}

public void run() {
}
});
}
99
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}catch(Exception e)
{
}
}

this.hide();
}

public void run() {
}
});
}
100
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
101
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
txt2.setText("");
txt3.setText("");
}
102
txt2.setText("");
txt3.setText("");
}catch(Exception e)
{
}
}

this.hide();
}

public void run() {
}
});
}
103
WITHDRAW FORM
import java.sql.*;
Private void verifyActionPerformed(java.awt.event.ActionEvent evt) {

try{
int accno=Integer.parseInt(combo.getSelectedItem().toString());
String query="select * from Account_table where accountno="+accno;
if(res.next())
{
txtname.setText(res.getString("hname"));
txtname.setEnabled(false);
}
else
JOptionPane.showMessageDialog(null, "ïnvalid account number");
}
catch(Exception e)
{}
private void withdrawActionPerformed(java.awt.event.ActionEvent evt) {

int accountno,amount=0,amount2=0;
String ddate;
boolean found=false;
accountno=Integer.parseInt(combo.getSelectedItem().toString());
ddate=txtwd.getText();
amount=Integer.parseInt(txtamount.getText());
try{
con=DriverManager.getConnection("jdbc:odbc:bank");
stmt2=con.createStatement();
String query="insert into withdraw
values("+accountno+",'"+ddate+"',"+amount+")";
stmt2.executeUpdate(query);
stmt=con.createStatement();
String q="select * from account_table where accountno="+accountno;
ResultSet res=stmt.executeQuery(q);
104
if(res.next())
{
amount=Integer.parseInt(res.getString("balance"))-amount;

JOptionPane.showMessageDialog(null,"Amount withdrawn");
}
txtwd.setText("");
txtamount.setText("");
}catch(Exception e)
{
}
}
dispose();
}
public void run() {
new Withdrawform().setVisible(true);
}
});
}
105
SEARCH ACCOUNT
import javax.swing.table.*;
import java.sql.*;
public class Search_account extends javax.swing.JFrame {
/**
* Creates new form Search_account
*/
Connection c;
Statement state;
int s;
public Search_account() {
initComponents();
}
private void op1ActionPerformed(java.awt.event.ActionEvent evt) {

lbl.setText("Enter account No ");
txt.setText("");
txt.requestFocus();
}

lbl.setText("Enter account holder name ");
txt.setText("");
txt.requestFocus();
}
txt.setText("");
}
private void SEARCHActionPerformed(java.awt.event.ActionEvent evt) {

DefaultTableModel m=(DefaultTableModel) tb.getModel();
try {
c=DriverManager.getConnection("jdbc:odbc:bank");
state=c.createStatement();
String query;
ResultSet res;
//Removing all rows;
int rows=m.getRowCount();
for(int i=0;i<rows;i++) {
106
m.removeRow(0);
}
if (op1.isSelected()) {
s=Integer.parseInt(txt.getText());
query="select * from account_table where accountno="+s;
res=state.executeQuery(query);
while(res.next()) {
m.addRow(new Object[]
{ res.getString(1),res.getString(2),res.getString(3),res.getString(5),res.getString(6),res.get
String(11)});
}
} else if (op2.isSelected()) {
String str=(txt.getText());
query="select * from account_table where hname='"+str+"'";
while(res.next()) {
String(6)});
}
} else if (op3.isSelected()) {
String str=(txt.getText());
query="select * from account_table";
while(res.next()) {
String(6)});
}
}
{}
}
}
private void EXITActionPerformed(java.awt.event.ActionEvent evt) {
dispose();
}

/* Set the Nimbus look and feel */
//<editor-fold defaultstate="collapsed" desc=" Look and feel setting code (optional)
">
107
/* If Nimbus (introduced in Java SE 6) is not available, stay with the default look
and feel.
* For details see
http://download.oracle.com/javase/tutorial/uiswing/lookandfeel/plaf.html
*/
try {
for (javax.swing.UIManager.LookAndFeelInfo info :
javax.swing.UIManager.getInstalledLookAndFeels()) {
if ("Nimbus".equals(info.getName())) {
javax.swing.UIManager.setLookAndFeel(info.getClassName());
break;
}
}
} catch (ClassNotFoundException ex) {
java.util.logging.Logger.getLogger(Search_account.class.getName()).log(java.util.loggin
g.Level.SEVERE, null, ex);
} catch (InstantiationException ex) {
} catch (IllegalAccessException ex) {
} catch (javax.swing.UnsupportedLookAndFeelException ex) {
}
//</editor-fold>
/* Create and display the form */

public void run() {
new Search_account().setVisible(true);
}
});
}

">
and feel.
108
* For details see
*/
try {
break;
}
}
}
//</editor-fold>

public void run() {
new Search_account().setVisible(true);
}
});
}
109
LIST OF ACCOUNT
import java.sql.*;
public class List_of_account extends javax.swing.JFrame {
/**
* Creates new form List_of_account
*/
public List_of_account() {
initComponents();
}

dispose();
}

try {
Connection c=DriverManager.getConnection("jdbc:odbc:bank");
Statement state=c.createStatement();
ResultSet res=state.executeQuery(query);
while(res.next()) {
String(6)});
}
}
catch(Exception e)
{}
}

">
and feel.
110
* For details see
*/
try {
break;
}
}
java.util.logging.Logger.getLogger(List_of_account.class.getName()).log(java.util.loggin
}
//</editor-fold>

public void run() {
new List_of_account().setVisible(true);
}
});
}
111
LIST OF DEPOSIT
import java.sql.*;
public class list_of_deposit extends javax.swing.JFrame {
/** Creates new form list_of_deposit */

public list_of_deposit() {
initComponents();
}
dispose();
}

try {
String query="select * from deposit";
while(res.next()) {
{ res.getString(1),res.getString(2),res.getString(3)});
}
}
catch(Exception e)
{}

public void run() {
new list_of_deposit().setVisible(true);
}
});
}
112
LIST OF WITHDRAW
import java.sql.*;
public class list_of_withdraw extends javax.swing.JFrame {
/** Creates new form list_of_withdraw */

public list_of_withdraw() {
initComponents();
}

dispose();

try {
String query="select * from withdraw";
while(res.next()) {
{ res.getString(1),res.getString(2),res.getString(3)});
}
}
catch(Exception e)
{}
}

public void run() {
new list_of_withdraw().setVisible(true);
}
});
}
113
PASSWORD CHANGE
import java.sql.*;
public class Passwordchange extends javax.swing.JFrame {
/** Creates new form Passwordchange */

public Passwordchange() {
initComponents();
}
private void verifyActionPerformed(java.awt.event.ActionEvent evt) {
String user1,pass1,npass2,cpass;
user1=txtuser.getText();
pass1=txtpassword.getText();
try{
String query="Select * from logintable where username='"+user1+"' and
password='"+pass1+"'";
if( res.next()) {
JOptionPane.showMessageDialog(null,"Verified Enter new password");
txtnewpass.setEnabled(true);
txtcompass.setEnabled(true);
change.setEnabled(true);
} else {
JOptionPane.showMessageDialog(null,"wrong password");
}
}
}
dispose();
}
114
private void changeActionPerformed(java.awt.event.ActionEvent evt) {
String npass,cpass;
npass=txtnewpass.getText();
cpass=txtcompass.getText();
if(npass.equals(cpass)) {
try{
String query="update logintable set password='"+npass+"'";
JOptionPane.showMessageDialog(rootPane, "Password changed
successfully");
}
} else
JOptionPane.showMessageDialog(rootPane, "Password no match");
}
public void run() {
new Passwordchange().setVisible(true);
}
});
}
115
Process Name:- Report
Description :- This process is for the displaying the reports of Customer and
transaction.
form
116
117
MODULES AND THEIR PROCESS LOGICS
Process Name:- Customer
Description :- This process is for the new Customer entry.
Process Name:- Account
Description : This process displays the all information about the Customer
according to the selection criteria of the Account.This process
gives the facility of selecting different types of query about the
particular Book.
Process Name:- Deposite
Description :- This process is for the searching the entry of particular Account for
deposte amount.
Process Name:- widthdraw
Description :- This process is for the searching the entry of particular account for
118
SCOPE OF FUTURE APPLICATION
The scope of future application for this system is:
1. A large student database can be accommodated in our application

in the future.
2. The related aspects like placement cell, staff details and customer
data can be maintained more easily.
3. In the purposed application examination monitoring, so that in

future an increased number of students can be accommodated by the sytem.
4. Employee and Salary Management System currently takes care of

Employee data.
5. The necessary steps have been taken in the proposed system to

accommodate the forthcoming changes regarding the course scheduling and the
batches thereof.
6. The format of different types of reports can be suit the

requirements in future though major modifications will be required but the base of
the project will remain the same and all the working will remain same in this
project.
119
CONCLUSION
After having completed this project, We felt that it was an excellent learning experience
as I deal with a real life project that give a opportunity to working for the students to
make their test more easy, while working on this project I got a good exposure to the
sharp programming skills and the various programming techniques while coding for this
system I was exposed to the vast knowledge about the strength and weakness of JAVA
language .
A part from this I have been able to appreciate the hard work of programmers spent in
developing such a system the most important realization was the amount of cooperation,
dedication, hardwork and team spirit that goes into making of a successful project.
120
BIBLIOGRAPHY
Books
Following books and eBook are used to complete this project reports.
I. Mastering JAVA Neat Beans
a. Author Tata McGraw-Hill’s
b. Publisher Black Book Publication
II. Oracle The Complete Reference
a. Author Robert Koch
b. Publication Tata McGraw-Hill
III. SQL, PL/SQL The Programming Language of Oracle
a. Author Ivan Bayross
b. Publication BPB Publication
IV. Software Engineering Apractitioner’s Approach
a. Author Roger S. Pressman
b. Publication Tata McGraw-Hill
V. Fundamentals of Software Engineering
a. Author Carlo Ghezzi, Mehdi Jazayeri, DinoMandrioli
b. Publisher Prentice Hall of India
WEB REFRENCES
www.microsoft.com
121

Banking Report

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Banking Report

Uploaded by

Copyright:

Available Formats

A

BACHELOR OF COMPUTER APPLICATION

Submitted by: Guided Guide :

Deptt. Of Computer Application

SHRI RAM COLLEGE,MUZAFFARNAGAR (U.P)

Roll No. 190855106094

under the guidance of Project Guide Dr. Pramod Kumar.

We wish him/her all the best for the future.

Internal Guide Head of Department(HOD)

Kunal Chauhan (Roll No. 190855106094)

HOD (Head Of Department) Signature

1.1 Scope of The System…....................................................................................8

Ch.2.Project category Tools &Environment

2.2 Front end Coverage………………………………………………….……...14

2.3 Back end Coverage………………………………………………….….…...15

2.4 Software and Hardware Requirements…………………………….….…….16

Ch.3.Project Development stages

3.5. Testing, Implementation & aintenance………………….………..….….....29

MAIN OBJECTIVE OF THIS PROJECT:

The scope of this document includes an overview of the BANKING

Some of these challenges in the general bank can be figure-out as:-

 Difficulty with the record keeping.

A FULL SERVICE PORTFOLIO:

2.1 Project Category & Development

JAVA used as FRONT END

Processor : Pentium 4 or above

Operating System : Windows XP/2003 or Linux/Solaris

1 Minimizing the manual records kept at different locations.

System analysis is conducted with the following objectives in mind:

1. Identify the Student and Staff members need

2. Evaluate the system concept for feasibility

3. Perform economic and technical analysis

5. Establish cost and schedule constraints

The concept of feasibility is to determine whether or not a project is worth doing.

The process followed in making this determination is called feasibility study.

Here we describe only few of these in detail:-

 Facility to produce output in a given time

In examining technical feasibility, configuration of the system is given more importance

 What changes will be brought with the system?

Cost-saving benefit leads to reduction in administrative and operational costs.

Direct Or Indirect Costs And Benefits

5. Those methods by which we show the time –relationship between

COST ESTIMATON OF THE PROJECT

FIRST LEVEL DFD -ELECTRICITY BILL SYSTEM

STOCK OWNER EMPLOYEE

OWNER USER PERMISSION

SECOND LEVEL DFD -ELECTRICITY BILL SYSTEM

DID Phone No. Email ID Date

Software development is a complex process so we divide the process in a small

i. Recognition of Needs: - It includes preliminary survey and initial investigation by

iv. System Construction: - It involves implementation of total construction plan i.e.

TESTING OBJEC TIVES:

1. Testing is a process of executing a program with the intent of finding an error.

Testing a large system is a complex activity, so for a project incremental testing is

It is the inability of a system or components to perform a require functions according to

TEST CASES AND TEST CRITERIA

Testing can be mainly of two types:

1. Incorrect or missing functions.

In this project our main emphasis is on white box testing.

1. Skipped the loop entirely.

BOUNDARY VALUE ANALYSIS:

Guidelines for boundary value analysis are as follows: