A PROJECT REPORT

ON
Bank Management System
Presented and Submitted By

MD TALIB MD MUSA
PRN No. 04421003676

ANSARI IBRHAIM MOHD RASHID

PRN No. 04421003651

Bachelor of Computer Application

Vikas College Study

Center, Vikhroli (East),

Tilak Maharashtra Vidyapeeth, Pune

Faculty of Distance Education
2023-2024

0
 A PROJECT REPORT
ON
Bank Management System

Presented and Submitted By

MD TALIB MD MUSA
PRN No. 04421003676

ANSARI IBRHAIM MOHD RASHID

PRN No. 04421003651

Towards The Partial Fulfilment of the

Bachelor of Computer Application

Vikas College Study

Center, Vikhroli (East),
Tilak Maharashtra Vidyapeeth, Pune
Faculty of Distance Education
2023-2024

1
 Bank Management System

MD TALIB MD MUSA

PRN No. 04421003676

&
ANSARI IBRHAIM MOHD RASHID
PRN No. 04421003651

Head of Department
Project Guide Examiner Vikas College- Vikhroli
2
Ms. Priti Pal

Vidya Vikas Education Society’s

VIKAS COLLEGE STUDY CENTRE
Vikas High School Marg, Kannamwar Nagar No.2, Vikhroli (East), Mumbai – 400 083.

Prof. Vikas P.Raut Shri.P.M.RAUT

Study Centre Co-ordinator Chairman, V.V.E. Society

CERTIFICATE
THIS IS TO CERTIFY THAT THE PROJECT
“BANK MANAGEMENT SYSTEM”
HAS BEEN SATISFACTORILY COMPLETED BY

MD TALIB MD MUSA (PRN NO :04421003676) SEAT NO : 2072

ANSARI IBRHAIM MOHD RASHID (PRN NO : 04421003651) SEAT NO : 2041

TOWARD THE PARTIAL FULFILMENT OF THE

“ BACHELOR OF COMPUTER APPLICATION ”,
FOR THE ACADEMIC YEAR [2024-2025] AT VIKAS COLLEGE,VIKHROLI
TILAK MAHARASHTRA VIDYAPEETH, PUNE
(FACULTY OF DISTANCE EDU CATION),
AND IT IS APPROVED.

……………………………………………………………………………………………………………………
PROJECT GUIDE EXAMINER HEAD OF DEPARTMENT
MS. PRITI PAL

3
 PREFACE

 With the rapid globalization of the Indian economy, enterprises are facing
with ever changing competitive environment. Enterprises are adopting
strategies aImedat developing competitive advantage based on enhanced
customer value in terms of product differentiation, quality, speed, service
and costs. In the post liberalizationera, with the deregulation of Indian
economy, the financial service sector witnessing a complete metamorphosis
and technology is playing a very signify.
 control in this record. Over the last decade India has been one of the fastest
adopters of information technology, particularly because of its capability to
provide software solution to organizations around the world. This capability
has provided a tremendous impetuous to the domestic banking industry in
India to deploy the latest in technology, particularly in the Internet banking
and e-commerce arenas. Banks are growing in size by mergers and
acquisitions, which have been driven by communication and technology.
Technology is playing a major role in increasing the efficiency, courtesy and
speed of customer service. It is said to be the age of E- banking. Bank user
is expected to perform at least one of the following transactions:

● Sign in
● Sign up
● Forgot Password
● Change Password
● Cash Withdraw
● Cash Deposit
● Balance Enquiry
● Logout

 Modules for Admin

● Transaction Report
● All Accounts Report
● Update Account
● Delete Account

4
 From a banks perspective, using the Internet is more efficient than using
other distribution mediums because banks are looking for an increased
customer base. Using multiple distribution channels increases effective
market coverage by enabling different products to be targeted at different
demographic segments. Also Banks cannot risk losing customers to
competitors within the aggressive competition in the banking industry
around the world. Moreover, bank delivery offers customized service to suit
the needs and the likes of each user. Mass customization happens
effectively through Banking Management System. It reduces cost and
replaces time spent on routine errands with spending time on business
errands. Bank Management System means less staff members, smaller
infrastructure demands, compared with other banking channels. From the
customer’s perspective.
 Bank Management System provides a convenient and effective way to
manage finances that is easily accessible 24 hours a day, seven days a
week. In addition, information is up to date. Nevertheless, Bank
Management System has disadvantages for banks like how to work the
technology, set-up cost, legal issues, and lack of personal contact with
customers. And for customers there are security and privacy issues.

5
 ACKNOWLEDGEMENT

 It is with great satisfaction and achievement that we have completed our

MAJOR-PROJECT of BANK MANAGEMENT SYSTEM. We take this
opportunity to acknowledge each and every one who contributed towards
our work. I express my sincere gratitude towards Prof DR. Rajeev Kumar,
Head of the Department, of DIMS, for his guidance and support. I take this
opportunity to thank our Project-coordinator and Project Guide Mr.Munish
Sharma Professor of Dept. DIMS for her suggestions, valuable support,
encouragement and guidance throughout the project. I also convey my
gratitude to all other members in the Project panel and those who have
contributed to this project directly or indirectly.

6
 ABSTRACT

 This project is aimed at developing Bank Management System for

customer. The system is a windows application that can be accessed
throughout the organization and outside as well with proper login provided.
The project has been planned to be having the view of distributed
architecture, with centralized storage of the database. The application for
the storage of the data has been planned. Using the constructs of MySQL
and all the user interfaces have been designed using the JAVA. The
database connectivity is
 planned using the “Database” methodology. The standards of security and
data.
 protective mechanism has been given a big choice for proper usage. The
application takes care of different modules and their associated reports,
which are produced as per the applicable strategies and standards that are
put forwarded byte administrative staff. The entire project has been
developed keeping in view of the distributed client server computing
technology, in mind. The specification has been normalized up to 3NF to
eliminate all the anomalies that may arise due to the database transaction
that are executed by the general users and the organizational
administration. The user interfaces are browser specific to give distributed
accessibility for the overall system. The internal database has been selected
as MySQL. The basic constructs of table spaces, clusters and indexes have
been exploited to provide higher consistency and reliability for the data
storage. The MySQL was a choice as it provides the constructs of high-level
reliability and security. The total front end was dominated using the JAVA
JDK 1.7. At all proper levels high care was taken to check that the system
manages the data consistency with proper business rules or validations.
The database connectivity was planned using the latest “Database
connection” technology provided by MySQL. The authentication and
authorization was crosschecked at all the relevant stages. The user level
accessibility has been restricted into two zones namely.

7
 CHAPTER 1
OVERVIEW OF THE PROJECT

8
 INTRODUCTION

 Bank Management System means banks provide comprehensive electronic

fund transfer and payment solutions that enable thousands of Citizens,
Financial Institutions and hundreds of businesses the convenience of
receiving and transferring their funds online.
 It's fast, easy and puts you in complete control you decide who to transfer
funds, checking of the account details. Receive and pay all your paper bills
at one site at your bank, credit union Plus, you can enhance the
convenience of transferring funds by receiving your bills electronically,
checking statuses of accounts and viewing the statements can possible with
this system. You can do this from one secure online location, in just a few
minutes.
 Banking system provides the greater opportunity to interact with Account
holder. But in regular system there are no more interactions with an account
holder or trustee. Authorities of Bank Management System Can Provides
the greater knowledge on Bank Management System and they can
effectively.
 This Bank System is windows software designed in Java programming
language for the purpose of effective Bank Management System. It mainly
aims at making the banking system easily accessible from anywhere and
improving and enhancing the running banking process. With the use of this
 software, bank customers don’t
 need to go to bank to make inquiry regarding their balance or to transfer
their balance to other account or for any other banking services.

9
1.1 PURPOSE OF THE SYSTEM

1. SECURITY:
 There is a lot of security of data on this content management system.
One cannot open our system without knowing the password. Immediately
after opening login screen will appear on screen. Only after entering the
correct username and password user can operate our system.

2. REFERENTIAL INTEGRITY:
 User cannot change the date in the transaction files. Addition of data can
be done only on the master files date in transaction files cannot be
entered until addition is done on the master files.

3. EASY RETRIEVAL OF DATA:

 Data is retrieved easily and quick using sq. commands. Online
commands are used to retrieve huge amount of data.

4. GENERATION OF AUTOMATIC VALUES:

 In project in some screen some fields generated automatically like Profile
detail, Account number, etc.

1.2 SCOPE OF THE PROPOSED SYSTEM

 Though there are many online systems available on internet but this can
compete with them with some advancement in its functionality and can be
used by any bank organization to maintain their customers account and
online transaction process.
 The basic functionalities of the system are:

10
 Modules for Customer: -
1. Sign up Module: -
 Description- New customer can sign up in to the system. New
customer should enter personal details and password in the
registration form and then click on
“submit” button. A new account will make in the system.

2. Sign in Module: -
 Description- Existing customer must have user-id and password to
login into the system. Customer should enter user-id and password
and click on sign in button for login into the system.

3. Change Password Module: -

 Description- Existing customer can change their existing password
with new password through the application by login into the system.
Customer should enter User-Id and password into the login page and
then click on sign in button. Now, various services appear on screen
from which user must click on “Change Password” button. Now, enter
the new password and then click on “Set Password” button for reset
the password.

4. Forgot Password Module: -

 Description- If existing customer forgot his/her password then,
customer can retrieve their password by simply clicking on “Forgot
Password”. Now, new page will appear on screen where he/she can
fill user-id and email-id which is linked to the account. In this way, we
can retrieve their password.

5. Cash Withdraw Module: -

 Description- Existing customer can withdraw money from their account
through the application by login into the system. Customer should
enter user-Id and password into the login page and then click on sign
in button. Now, various services will appear on screen from which user
must click on “Cash Withdraw”
11
 Button.
6. Cash Deposit Module:-
 Description- Existing customer can deposit money in their account
through the application by login into the system. Customer should
enter user-Id and Password into the login page and then click on sign
in button. Now, various services will appear on screen from which user
must click on “Cash Deposit” button and then, new page will appear
on screen to fill the required details for depositing money.

7. Balance Enquiry Module:-

 Description- Existing customer can see their account balance through
the application by login into the system. Customer should enter user-
Id and password into the login page and then click on sign in button.
Now, various services will appear on screen from which user must
click on “Balance Enquiry
” button and then existing account balance will appear on screen.

8. Logout Module:-
 Description- Existing customers can logout from the system by simply
clicking on logout button which was already login into the system.

9. Transactions Report Module:-

 Description- Administrator can see transactions report through the
application by login into the system. Administrator should enter user-Id
and password into the login page and then click on login button. Now,
various services will appear on screen from which admin must click on
“Transactions Report” button and then, transactions history will appear
on screen.

10. All Accounts Report Module:-

 Description- Administrator can see all accounts report through the
application by login into the system. Administrator should enter user-Id
and password into the login page and then click on sign in button.
Now, various services will appear on screen from which admin must

12
 click on “ All Accounts Report” button and then, report will appear on
screen.

11. Update Account Module:-

 Description- Administrator can update accounts details through the
application bylogin into the system. Administrator should enter user-Id
and password into thelogin page and then click on sign in button.
Now, various services will appear on screen from which admin must
click on “Update Account” button and then, update account page will
appear on screen.

12. Delete Account Module:-

 Description- Administrator can delete any account through the
application by login into the system. Administrator should enter User-
Id and password into the login page and then click on login button.
Now, various services will appear on screen from which admin must
click on “Delete Account” button and then, delete account page will
appear on screen.

13
1.3 OVERVIEW OF PROPOSED SYSTEM

1. MENU DRIVEN:
The project uses menu throughout which we can choose required options.
Menus are self-explanatory, as they are very easy to use and user can go to
any other web page using the menu.

2. USER CONFIRMATION:
Whenever the user tries to delete or edit the data, the system asks for the
confirmation. This is used to avoid the accidental changes to the database. A
confirmation is also provided for the exit of the application.

3. GRAPHICAL USER INTERFACE:

User is provided with a graphical interface in which user can select from
various options and can perform desired operations with perfect understanding
of the menu selected.

4. MULTIPLE DOCUMENT INTERFACE:

The package provides a multiple document interface to the user. The user can
view more than one entry form or pages at the same time.

5. SECURITY AND ACCESS:

A password form has been provided at the beginning of the package. Entering
the correct password will take user to the main user page.

14
1.4 BUSINESS CONTEXT

 Existing banking system is a manual system, which leads to a number of

problems in maintaining proper records.

These are:
1. PAPER WORK:
All the activities that are performed by Management involve a lot of paper work
involving register consultations and entries. A separate file has to be
maintained for each kind of activity and for different periods of time.

2. TIME CONSUMPTION:
A lot of time is consumed in referencing the registers involved for particular
activities and a lot of computation as well as report verification activity is also
paper based and time consuming.

3. COMPLEXITY:
Complexity of information handling and the gathering and determination of
information is usually the most difficult problem faced.

4. REDUNDANCY:
Maintaining separate files for each department can lead to duplication of data
present in files. This can lead to a) Inconsistencies b) Update anomaly esc)
Decentralization problems.

5. HUMAN ERRORS:
Human kind of errors may be generated in typing errors and slow arithmetic
calculations, fatigue and boredom.

6. ILLEGAL ACCESS:
The security of a lot of documents, which are paper, base difficult may be in
terms of illegal access or manipulation by malicious personals either
intentionally or by accident.

15
 Objective
 To allow only authorized user (Bank Employee) to access various functions
available in the system.
 Open any account wanted by the user.
 Reduce clerical work as most of the work done by computer.

 Provide greater speed & reduced time consumption.

 To increase the number of account and customer.

 This will reduce the manual workload and give information instantly. The
software will maintain the list of A/C and customer record and Transaction
record.

 The software will be user friendly so that even a beginner can operate the
package and thus maintain the status of A/C, do the transaction and
maintain balance status easily.

 The Project Banking system has been made to automate the Banking
system being followed by a banking company that deals in current account
with or without check facility.
 Functionalities provided by Bank

16
 Management System are as follow:

 Provides the searching facilities based on various factor such as account

customers, user-id and email-id.

 Bank Management System also manage the balance detail for transaction
Details, banking detail, accounts.

 It tracks all the information of bank, balance, transaction etc. Manager the
information of bank.

 Show the information and description of the account customer.

 To increase efficiency of manage the accounts of bank.

 It deals with monitoring the information and transaction of transaction.

 Manage the information of transaction.

17
 CHAPTER- 2
System Analysis

18
 SYSTEM ANALYSIS:
 System analysis is a process of gathering and interpreting facts, diagnosing
problems and the information about the Bank Management System to
recommend improvements on the system. It is problem solving activity that
requires intensive communication between the system users and system
developers. System analysis or study is an important phase of any system
developments process. The system is studied to the minutest detail and
analyse. The system analyst plays the role of the interrogator and dwells
deep into the working of the present system. The system is viewed as a
whole and the input to the system are identified. The outputs from the
organizations are traced to the various processes, system analysis is b
concerned with becoming aware of the problems, identifying the relevant
and decisional variables, analysing, and synthesizing the various factors
and determining an optimal or at least a satisfactory solution or program of
action. A detailed study of the process must be made by various techniques
like interview, question queries etc. the data collected by these sources
must be scrutinized to arrive to a conclusion. The conclusion is an
understanding of how the system functions. This system is called the
existing system. Now the existing system is subjected to close study and
problems areas are identified. The designers now function as a problem
solver and try to sort out the difficulties that the enterprise faces. The
solutions are given as proposals. The proposal is than weighed with the
existing system analytically and the best one is selected. The proposal is
presented to the user for an endorsement by the user. The proposal is
reviewed on user request and suitable changes are made. This is loop that
ends as soon as the user is satisfied with proposal. Preliminary study is the
process of gathering and interpreting facts, using the information for further
studies on the system. Preliminary study is problem-solving activity that
requires intensive communication between the system users and system
developers. It does various feasibility studies. In these studies, a rough
figure of the system activities can be obtained, from which the decision
about the strategies to be followed for effective system study and analysis
can be taken.

19
 Existing system of Bank Management System

 Existing system is the traditional banking, where customers have to go

through the long queue, time wasted and still wouldn’t have access to
efficient and effective banking system The developed system is an
innovation in the area of private banking. In the existing system the no. of
staff required for completing the work is more, while the new system
requires lesser staffs generally. The data entry process requires the data on
the paper, which is then feed into the application by the operator while doing
so; the data entry operator has to look into the paper again &again and thus
the chances of in accuracies in the typed contents increases. Also the
process includes higher transportation cost, increased handling cost, more
time delays, low accuracy, more usage of resources like registers, books,
papers, etc.

● Lack of security of data.

● More man power.
● Time consuming.
● Consumers large volume of pare work.
● Needs manual calculations.
● No direct role for the higher officials.

20
 Proposed system of Bank Management System

 The aim of process system is to develop a system of improved facilities. The

proposed system can overcome all the limitations of the existing system.
The system provided security and reduces the manual world. Hence the
requirement is to develop a system that minimizes all these overheads
included while giving the maximum output for the organization. The basis for
the project is to develop a fully automated banking system that includes
depositing of amount, withdrawal of amount and exporting the outcome
back to the client while considering all the tools and facilities than a client
may need for efficient and effective output.

● Security of data.
● Ensure data accuracy`s.
● Proper control of the higher officials.
● Minimize manual data entry.
● Minimum time needed for the various processing.
● Greater efficiency.
● Better service.
● User friendliness and interactive.

21
 Benefits of the system
● quick, authenticated access to accounts via the desktop.
● Easily scalable to grow with changing system requirement.
● Enterprise wide access to information.
● Improved information security, restricting unauthorized access.
● Minimize Storage Space

 In manual system, much storage space for data files is required so to

overcome this problem, on automated well managed database is developed
for saving storage space. This s/w saves space and stores information
efficiently. It ends the burden of having large manual filing storage system.

 Banking System can be used extensively

● Withdrawal of amount by the client.
● Deposition of amount by the client.
● Faster balance enquiry.

 Analysis is also detailed study of the various operations performed by the

system and their relationship within and outside the system.

1. Data Dictionary: -
 A Data Dictionary is a structure repository of data about data. It is a set of
rigorous definitions of all the data flow diagram, data elements and data
structure. There are three classes of items to be defined:
 Data element: smallest unit of data.
 Data structure: group of data element handled as a unit.
 Data flow and data stores: temporary location of data and permanent
location of data.

2. Decision tree: -

 A decision tree is a diagram that presents condition and actions sequentially. It

is a method of showing relationship of each condition and its permissible
actions.
22
3. Decision table: -
 A decision table is a table of contingencies for defining a problem and
actions to be taken single representation of the relationship between
conditions and actions.
 Following are some rules, which define the construction of data A
dictionary entry:
 Words should be defining to understand for what they need and not the
variable need by which the may be described in the program.
 Each word must be unique. we cannot have two or more definition of the
same client.

23
 FEASIBILITY ANALYSIS

 Feasibility is the determination of whether or not a project is worth doing.

The processes are followed in making this determination is called feasibility
study. Feasibility study is the test of system proposal according to its work
ability, Impact on the organization ability to meet user’s needs, and effective
use of resources. The result of feasibility study is a formal proposal. This is
simply report a formal document detailing the nature and scope of the
proposed solution. The main objective of a feasibility study is to test the
technical, social and economic feasibility of developing a computer system.
This is done by investigation the existing system in the area under
investigation and generating ideas about a new system. On studying the
feasibility of the system, three major considerations are dealt with, to find
whether the automation of the system is feasible.

 Main task done during the feasibility study are: -

1. Evaluation of existing system and procedures. Our group went to various
Banking Professionals together information about the software system.
They are using and evaluating those systems and the procedures invoked in
it during the period of feasibility study.
2. Analysis of alternative candidate systems after studying the various systems
we derived various alternatives through which we develop our project and
evaluated the alternative. The most appropriate is selected.

 Three aspects in which the system has to be feasible are: -

24
 ECONOMICAL FEASIBILITY

 The economic analysis checks for the high investment incurred on the
system. It evaluates development & implementing charges for the proposed
“Banking Project”. The S/W used for the development is easily available at
minimal cost & the database applied is freely available hence it results in
low cost implementation. The only tangible benefit provided by the proposed
system is that the paper work is reduced to the minimum and hence the
reduction in cost incurred on Stationary and its storage. The system
provides many benefits that can’t be measured in terms of Money for e.g.
user’s friendliness, more user response being more efficient.

TECHNICAL FEASIBILITY:

 This aspect concentrates on the concept of using Computer Meaning,

“Mechanization” of human works. Thus the automated solution leads to the
need for a technical feasibility study. The focus on the platform used
database management &users for that S/Wither proposed system doesn’t
require an in depth technical knowledge as the system development is
simple and easy to understand. The result obtain should be true in the real
time conditions.

 Minimum requirement for execution of the project is a java supporting

operating system since the connection to the database will be made using
JSP and SERVLETS, minimum of 64 MB of RAM, a database software, a
server and a web browser with which we were previously equipped.

25
 Operational feasibility:

 Now almost all Banks branches are connected through the Bank
Management System facilities. The transactions of a particular bank are
transmitted through the Micro-Bank software from INFLEX Solutions to the
Head Office, where every data is stored in the database. Real-time On-line
any branch banking for the clients is used to facilitate the clients to deposit
/draw or remit funds to and from their accounts, from one bank to another.
Meanwhile, for the Smooth operation and efficient functioning of the system
they have completed the proper training to the related personnel.

26
 CHAPTER- 3
Software Requirement&
Specification

27
 Software requirement specification:

 The software requirements specification is a produced at the culmination of

Thea task. The function and performance allocated to software as a part of
system engineering are refined by establishing a complete information
description, detailed functional and behavioural, an indication of
performance requirements and design constraints, appropriate validation
criteria and other data pertinent to requirements. The proposed system has
the following requirements:

1. System needs store information about new entry of accounts.

2. System needs to help the internal staff to keep information of bank and find
them as per various queries.
3. System need to maintain quantity record.
4. System need to keep the record of customer.
5. System need to update and delete the record.
6. System also needs a search area.

 It also needs a security to prevent data. The reason behind it is that there is
lot of information to be maintained and have to be kept in mind while
running the business. for this reason, we have provided features present
stem is partially automated(computerized), actually existing system is quite;
laborious as one has to enter same information at three different places.
Following points should be well considered:

 Documents and reports that must be provided by the new system, there can
also be few report, which can help management in decision making and
cost controlling, but since these report do not get required attention, such
kind of reports and information were also identified and given required
attention. Details of the information needed for each document and report.
The required frequency and distribution for each document and report. With
the implementation of computerized system, the task of keeping records in
an organized manner will be solved. The greatest of all is the retrieval of
information which will be at the click of the mouse.

28
Software Required:
 The project is implemented in Core Java as it provides the implementation
of art package that are used to connect distinct applications, hence the
software’s required in the creation and execution of the project are JAVA
JDK 1.7. As we know JAVA is a platform independent language so this
software runs with JRE environment on any desired platform i.e. Linux,
windows 9x, XP, or 2000 or any operating system.

Hardware Required:
 As the project involve database, its hardware requirements are minimal. Any
System with Pentium P2 or above processor, 32MB RAM, 1GB Hard Disk, a
LAN Card, and a CDROM is sufficient. Its network based software so
computers connected with any kind of mode (wireless, LAN connected etc.)
will suit its requirements ...... It can also be run on a single machine for its
demo use. Best suited in laboratory where we can run its server on any
machine and many clients can use it simultaneously.

Technologies and Requirements

 Front End: JAVA JDK 1.7

 Programming Language: JAVA
 Back End: MySQL

Non-functional Requirements

 Secure access of require data.

 24X7 availability
 user friendly
 Intelligent user interfaces

29
 Chapter - 4
Introduction to Tool /
Language

30
 JAVA: -
Platform independent:
 The concept of Write-once-run-anywhere (known as the Platform
independent) is one of the important key feature of java language that
makes java as the most powerful language. Not even a single language is
idle to this feature but java is closer to this feature. The programs written on
one platform can run on any platform provided the platform must have the
JVM.

Simple:
 There are various features that make the java as a simple language.
Programs are easy to write and debug because java does not use the
pointers explicitly. It is much harder to write the java programs that can
crash the system but we cannot say about the other programming
languages. Java provides the bug free system due to the strong memory
management. It also has the automatic memory allocation and de-allocation
system.

Object Oriented:
 To be an Object Oriented language, any language must follow at least the
four characteristics.

Inheritance:
 It is the process of creating the new classes and using the behaviour of the
existing classes by extending them just to reuse the existing code and
adding the additional features as needed.

Encapsulation:
 It is the mechanism of combining the information and providing the
abstraction.

Polymorphism:

31
 As the name suggest one name multiple form, Polymorphism is the way of
providing the different functionality byte functions having the same name
based on the signatures of the methods.
Dynamic binding:
 Sometimes we don't have the knowledge of objects about their specific
types while writing our code. It is the way of providing the maximum
functionality to a program about the specific type at runtime. As the
languages like Objective C, C++ fulfils the above four characteristics yet
they are not fully object oriented languages because they are structured as
well as object oriented languages. But in case of java, it is a fully Object
Oriented language because object is at the outer most level of data
structure in java. No standalone methods, constants, and variables are
there in java. Everything in java is object even the primitive data types can
also be converted into object by using the wrapper class.

Robust:
 Java has the strong memory allocation and automatic garbage collection
mechanism. It provides the powerful exception handling and type checking
mechanism as compare to other programming languages. Compiler checks
the program whether there any error and interpreter checks any run time
error and makes the system secure from crash. All of the above features
makes the java language robust.

Distributed:
 The widely used protocols like HTTP and FTP are developed in java.
Internet programmers can call functions on these protocols and can get
access the files from any remote machine on the internet rather than writing
codes on their local system.

Portable:
 The feature Write-once-run-anywhere makes the java language portable
provided that the system must have interpreter for the JVM. Java also have
the standard data size irrespective of operating system or the processor.
These features make the java as a portable language.

32
 Dynamic:
 While executing the java program the user can get the required files
dynamically from a local drive or from computer thousands of miles away
from the user just by connecting with the Internet.
Secure:
 Java does not use memory pointers explicitly. All the programs in java are
run under an area known as the sand box. Security manager determines the
accessibility options of a class like reading and writing a file to the local disk.
Java uses the public key encryption system to allow the java applications to
transmit over the internet in the secure encrypted form. The byte code
Verifier checks the classes after loading.

Performance:
 Java uses native code usage, and lightweight process called threads. In the
beginning interpretation of byte code resulted the performance slow but the
advance version of JVM uses the adaptive and just in time compilation
technique that improves the performance.

Multithreaded:
 Java is also a multithreaded programming language. Multithreading means
a single program having different threads executing independently at the
same time. Multiple threads execute instructions according to the program
code in a process or a program. Multithreading works the similar ways
multiple processes run on one computer. Multithreading programming is a
very interesting concept in Java. In multithreaded programs not even a
single thread disturbs the execution of other thread. Threads are obtained
from the pool of available ready to run threads and they run on the system
CPUs. This is how Multithreading works in Java which you will soon comet
know in details in later chapters.

Interpreted:
 We all know that Java is an interpreted language as well. With an
interpreted language such as Java, programs run directly from the source
code. The interpreter program reads the source code and translates it on

33
 the fly into computations. Thus, Java as an interpreted language depends
on an interpreter program.
platform independent:
 The source code to be written and distributed is platform independent.
Another advantage of Java as an interpreted language is its error debugging
quality.

Architecture Neutral:
 The term architectural neutral seems to be weird, but yes Java is an
architectural neutral language as well. The growing popularity of networks
makes developers think distributed. In the world of network, it is essential
that the applications must be able to migrate easily to different computer
systems. Not only to computer systems but to a wide variety of hardware
architecture and operating system architectures as well. The Java compiler
does this by generating byte code instructions, to be easily interpreted on
any machine and to be easily translated into native machine code on the fly.

 The compiler generates an architecture-neutral object file format to enable a

Java application to execute anywhere on the network and then the compiled
code is executed on many processors, given the presence of the Java
runtime system.

 Hence Java was designed to support applications on network. This feature

of Java has thrived the programming language.

JDK: -

 The Java Development Kit (JDK) is a Sun Microsystems product aimed at

Java developers. Since the introduction of Java, it has been by far the most
widely used Java SDK. On 17 November 2006, Sun announced that it
would be released under the GNU General Public License(GPL), thus
making it free software. This happened in large part on 8 May 2007 and the
source code was contributed to the Open JDK. The primary components of
the JDK are a selection of programming tools, including:
34
 Java–
 The loader for Java applications. This tool is an interpreter and can interpret
the class files generated by the java compiler. Now a single launcher is
used for both development and deployment. The old deployment launcher,
jre, is no longer provided with Sun JDK.

javac –
 The compiler, which converts source code into Java bytecode

Jar –
 The archiver, which packages related class libraries into a single JAR file.
This tool also helps manage JAR files.

Javadoc –
 The documentation generator, which automatically generates
documentation from source code comments

jdb –
 The debugger

javap –
 The class file disassembler

Applet viewer –
 This tool can be used to run and debug Java applets without web browser.

javah –
 The C header and stub generator, used to write native methods

Ext check –
35
 This utility can detect JAR-file conflicts.

apt–
 The annotation processing tool

jhat –
 (Experimental) Java heap analysis tool

Jstack –
 (Experimental) This utility prints Java stack traces of Java threads.

jstat –
 (Experimental) Java Virtual Machine statistics monitoring tool

jstatd –
 (Experimental) jstat daemon

Jinfo –
 (Experimental) This utility gets configuration information from a running Java
process or crash dump.

jmap –
 (Experimental) This utility outputs the memory map for Java and can print
shared object memory maps or heap memory details of a given processor
core dump.

idlj–
 The IDL-to-Java compiler. This utility generates Java bindings from a given
IDL file.

policy tool –
 The policy creation and management tool, which can determine policy for a
Java runtime, specifying which permissions are available for code from
various sources.
36
 VisualVM –
 Visual tool integrating several command line JDK tools and lightweight
performance and memory profiling capabilities.
 The JDK also comes with a complete Java Runtime Environment, usually
called a private
 runtime. It consists of a Java Virtual Machine and all of the class libraries
that will be present in the production environment, as well as additional
libraries only useful to developers, such as the internationalization libraries
and the ID Libraries. Also included is a wide selection of example programs
demonstrating the use of almost all portions of the Java API.

INTRODUCTION TO BACK END TOOL:

 Introduction to SQL: -
1. SQL is a standard language for accessing and manipulating databases.
2. SQL stands for Structured Query language.
3. SQL allows you to access a database.
4. SQL is an ANSI standard computer language.
5. SQL can execute queries against a database.
6. SQL can retrieve data from a database.
7. SQL can insert new records in a database.
8. SQL can delete records from a database.
9. SQL can update records in a database.
10.SQL is easy to learn.

 SQL is an ANSI (American National Standards Institute) standard for

accessing and manipulating database systems. SQL statements are
used to retrieve and update data in a database. SQL works with
database programs like MS Access, DB2, Informix, MS SQL Server,
Oracle, Sybase, etc.

37
 CHAPTER-5
System Design

38
5.1 INTRODUCTION:

 Software design sits at the technical kernel of the software

engineering process and applied regardless of the development
paradigm and area of application. Designs the first step in the
development phase for any engineered product or system.
 The designer’s goal is to produce a model or representation of an
entity that will
 later be built. Beginning, once system requirement has been specified
and analysed, system design is the first of the three technical activities
-design, code and test that is required to build and verify software.
 The importance can be stated with a single word “Quality”. Design is
the place
 where quality is fostered in software development. Design provides us
with representations of software that can assess for quality. Design is
the only way that
 we can accurately translate a customer’s view into a finished software
product or
 system. Software design serves as a foundation for all the software
engineering steps that follow. Without a strong design we risk building
an unstable system
– one that will be difficult to test, one whose quality cannot be
assessed until the last stage. During design, progressive
refinement of data structure, program structure, and procedural
details are developed reviewed and documented. System design
can be viewed from either technical or project management
perspective. From the technical point of view, design is
comprised of four activities
– architectural design, data structure design, interface design and
procedural design.

39
 Data base design:
 Database Design is a collection of processes that facilitate the designing,
development, implementation and maintenance of enterprise data
management systems. It helps produce database systems.
 1. That meet the requirements of the users.
 2. Have high performance.

 The main objectives of database designing are to produce logical and

physical designs models of the proposed database system. The logical
model concentrates on the data requirements and the data to be stored
independent of physical considerations. It does not concern itself with how
the data will be stored or where it will be stored physically. The physical
data design model involves translating the logical design of the database
onto physical media using hardware resources and software systems such
as database management systems (DBMS). For developing an efficient
data base, we will have to full fill certain condition such as:

1. *Control Redundancy.
2. *Ease of use.
3. *Accuracy and integrity.
4. *Avoiding inordinate delays.
5. *Recovery from failure.
6. *Privacy and security.
7. *Performance.
 There are 6 major steps in design process. The first 5 steps are usually
done on paper and finally the design is implemented.

1. *Identify the tables and relationship.

2. *Identify the data that is needed for each table and relationship.
3. *Resolve the relationship.
4. *Verify the design.
5. *Implement the design.

40
 NORMALIZATION:

 Normalization is a technique that is more applicable to record based data

models. Each of the process can be carried out independently to arrive at
normalized tables. Normalization refines the data structure and data are
group in simple way as possible. So later changes can be bringing about the
least impact on database structure and eliminates data redundancy.

DATA INTEGRITY

 Data integrity refers to the procedure that ensures correctness of the data
entered in the database. Functions have been provided in the software,
which check data while being entered. Integrity problems are occurred due
to hardware or software malfunctions such as power failure and disk
crashes. Side effect from the program development may also be the reason.

DATA CONSISTENCY

 Problem with data consistency occur when adding records without first
checking for records with same key or deleting records without deleting
other related records. Likewise, the software is coded such that primary
keys can’t be duplicated.
 For developing an efficient database, we have to fulfil certain conditions
such as:
1. *Control redundancy.
2. *Ease of use.
3. *Data independence.
4. *Privacy and security.

Performance for achieving the above criteria’s we have to make use of various
features that are available with DBMS such as:
1. *Enforcing integrity constraints to ensure data integrity and to reduce data
inconsistency.
2. *Recovery from failures using backup facility

41
5.2 NORMALIZATION:

 It is a process of converting a relation to a standard form. The process is

used to handle the problems that can arise due to data redundancy i.e.
repetition of data in the database, maintain data integrity as well as handling
problems that canaries due to insertion, updating, deletion anomalies.
 Decomposing is the process of splitting relations into multiple relations to
eliminate anomalies and maintain anomalies and maintain data integrity. To
do this we use normal forms or rules for structuring relation.

1. Insertion anomaly: Inability to add data to the database due to absence of

other data.
2. Deletion anomaly: Unintended loss of data due to deletion of other data.
3. Update anomaly: Data inconsistency resulting from data redundancy and
partial update.
4. Normal Forms: These are the rules for structuring relations that eliminate
anomalies.

FIRST NORMAL FORM:

 A relation is said to be in first normal form if the values in the relation are
atomic for every attribute in the relation. By this we mean simply that no
attribute value can be a set of values or, as it is sometimes expressed, a
repeating group.

SECOND NORMAL FORM:

 A relation is said to be in second Normal form is it is in first normal form and
it should satisfy any one of the following rules.
1) Primary key is a not a composite primary key
2) No non key attributes are present
3) Every non key attribute is fully functionally dependent on full set of primary
key.

THIRD NORMAL FORM:

 A relation is said to be in third normal form if their exits no transitive
dependencies.
42
 Transitive Dependency: If two non-key attributes depend on each other as
well as on the primary key then they are said to be transitively dependent.

5.3 DATA FLOW DIAGRAMS:

 A data flow diagram is graphical tool used to describe and analyse

movement of data through a system. These are the central tool and the
basis from which the other components are developed. The transformation
of data from input to output, through processed, may be described logically
and independently of physical components associated with the system.
These are known as the logical data flow diagrams. The physical data flow
diagrams show the actual implements and movement of data between
people, departments and workstations. A full description of a system
actually consists of a set of data flow diagrams. Using two familiar notations
Yourdon, Gain and Sarson notation develops the data flow diagrams. Each
component in a DFD is labelled with a descriptive name. Process is further
identified with a number that will be used for identification purpose. The
development of DFD’S is done in several levels. Each process in lower level
diagrams can be broken down into a more detailed DFD in the next level.
The lop-level diagram is often called context diagram. It consists a single
process bit, which plays vital role in studying the current system.
 The process in the context level diagram is exploded into other process at
the first level DFD. The idea behind the explosion of a process into more
process is that understanding at one level of detail is exploded into greater
detail at the next level. This is done until further explosion is necessary and
an adequate amount of detail is described for analyst to understand the
process. Larry Constantine first developed the DFD as a way of expressing
system requirements in a graphical from, this lead to the modular design.

 A DFD is also known as a “bubble Chart” has the purpose of clarifying

system requirements and identifying major transformations that will become
programs in system design. So it is the starting point of the design to the
lowest level of detail. A DFD consists of a series of bubbles joined by data
flows in the system.

43
DFD SYMBOLS:

 In the DFD, there are four symbols

1. A square defines a source(originator) or destination of system data
2. An arrow identifies data flow. It is the pipeline through which the information
flows
3. A circle or a bubble represents a process that transforms incoming data flow
into outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of
data process that transforms data flow. Source or Destination of flow Data
Store.

CONSTRUCTING A DFD:
 Several rules of thumb are used in drawing DFD’S:
1. Process should be named and numbered for an easy reference. Each name
should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow back to
the source. One way to indicate this is to draw long flow line back to a source.
An alternative way is to repeat the source symbol as a destination. Since it
issued more than once in the DFD it is marked with a short diagonal.
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters.
Process and dataflow names have the first letter of each work capitalized DFD
typically shows the minimum contents of data store. Each data store should
contain all the data elements that flow in and out. Questionnaires should
contain all the data elements that flow in and out. Missing interfaces
redundancies and like is then accounted for often through interviews.

44
 SAILENT FEATURES OF DFD’S
1. The DFD shows flow of data, not of control loops and decision are
controlled considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process
whether the dataflow take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.

 TYPES OF DATA FLOW DIAGRAMS

1. Current Physical
2. Current Logical
3. New Logical
4. New Physical

CURRENT PHYSICAL:
 In Current Physical DFD 45recess label include the name of people or
their positions or the names of computer systems that might provide
some of the overall system-processing label includes an identification
of the technology used to process the data. Similarly, data flows and
data stores are often labels with the names of the actual physical
media on which data are stored such as file folders, computer files,
business forms or computer tapes.

CURRENT LOGICAL:
 The physical aspects at the system are removed as much as possible so
that the current system is reduced to its essence to the data and the
processors that transform them regardless of actual physical form. This is
exactly like a current logical model if the user were completely happy with
the user were completely happy with the functionality of the current system
but had problems with how it was implemented typically through the new
logical model will differ from current logical model while having additional
functions, absolute function removal and inefficient flows recognized.

45
 NEW PHYSICAL:
The new physical represents only the physical implementation of the new
system.

RULES GOVERNING THE DFD’S PROCESS

1) No process can have only outputs.
2) No process can have only inputs. If an object has only inputs than it must
be a sink.
3) A process has a verb phrase label.

E–R DIAGRAMS:

 The relation upon the system is structure through a conceptual ER-Diagram,

which not only specifics the existential entities but also the standard
relations through which the system exists and the cardinalities that are
necessary for the system state to continue.

 The entity Relationship Diagram (ERD) depicts the relationship between the
data objects. The ERD is the notation that is used to conduct the date
modelling activity the attributes of each data object noted is the ERD can be
described resign a data object description.

 The set of primary components that are identified by the ERD are
 Data object
 Relationships
 Attributes
 Various types of indicators. The primary purpose of the ERD is to represent
data objects and their relationships

46
 User case diagram:

 A use case diagram is a dynamic or behaviour diagram in UML. Use case

diagrams model the functionality of a system using actors and use cases.
Use cases are a setoff actions, services, and functions that the system
needs to perform. In this context, a "system" is something being developed
or operated, such as a web site. The “actors" are people or entities
operating under defined roles within the system. Use case diagrams are
valuable for visualizing the functional requirements of system that will
translate into design choices and development priorities. They also help
identify any internal or external factors that may influence the system and
should be taken into consideration. They provide a good high level analysis
from outside the system. Use case diagrams specify how the system
interacts with actors without worrying about the details of how that
functionality is implemented.
 Basic Use Case Diagram Symbols and Notations System

 Draw your system's boundaries using a rectangle that contains use cases.
Place actors outside the system's boundaries.

Use case
 Draw use cases using ovals. Label the ovals with verbs that represent
the system’s functions.

Actors
 Actors are the users of a system. When one system is the actor of
another system, label the actor system with the actor stereotype.

Relationships
 Illustrate relationships between an actor and a use case with a simple
line. For relationships among use cases, use arrows labelled either
"uses" or "extends.

47
Use Case Diagram

48
 6.4 WATERFALL MODEL

 The Waterfall Model was first Process Model to be introduced. It is also

referred to as a linear-sequential life cycle model. It is very simple to
understand and use. In a waterfall model, each phase must be completed
fully before the next phase can begin. At the end of each phase, a review
takes place to determine if the project is on the right path and whether or not
to continue or discard the project. In waterfall model phases do not overlap.
1. Simple and easy to understand and use.
2. Easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
3. Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well
understood.

When to use the waterfall model:

1. Requirements are very well known, clear and fixed.
2. Product definition is stable.
3. Technology is understood.
4. There are no ambiguous requirements.
5. Ample resources with required expertise are available freely.

49
WATERFALL MODEL

50
CHAPTER- 6
Coding

51
public class Login1 extends Frame Implements Action Listener {
Button login, signup, reset;
JTextField AccountTextField;
JPasswordField pinTextField;

Login1() {
setTitle("AUTOMATED TELLER MACHINE");
setLayout(null);

ImageIcon i1 = new
ImageIcon(ClassLoader.getSystemResource("icons/loggn.jpg"));
Image i2 = i1.getImage().getScaledInstance(700, 700,
Image.SCALE_DEFAULT);
ImageIcon i3 = new ImageIcon(i2);
JLabel label11 = new JLabel(i3);
label11.setBounds(750, 50, 700, 700);
add(label11);

ImageIcon l1 = new
ImageIcon(ClassLoader.getSystemResource("icons/bankinglogo1.jpg"));
Image l2 = l1.getImage().getScaledInstance(100, 100,
Image.SCALE_DEFAULT);
ImageIcon l3 = new ImageIcon(l2);
JLabel label = new JLabel(l3);
label.setBounds(70, 10, 100, 100);
add(label);

ImageIcon j1 = new
ImageIcon(ClassLoader.getSystemResource("icons/loginpage1.jpg"));
Image j2 = j1.getImage().getScaledInstance(700, 200,
Image.SCALE_DEFAULT);
ImageIcon j3 = new ImageIcon(j2);
JLabel label6 = new JLabel(j3);
label6.setBounds(20, 580, 700, 200);
add(label6);

52
 ImageIcon h1 = new
ImageIcon(ClassLoader.getSystemResource("icons/log_login.png"));
Image h2 = h1.getImage().getScaledInstance(70, 70,
Image.SCALE_DEFAULT);
ImageIcon h3 = new ImageIcon(h2);
JLabel label5 = new JLabel(h3);
label5.setBounds(300, 190, 70, 70);
add(label5);
JLabel text1 = new JLabel("LOGIN");
text1.setFont(new Font("Osward", Font.BOLD, 20));
text1.setForeground(Color.black);
text1.setBounds(300, 260, 450, 40);
add(text1);

JLabel text = new JLabel("WELCOME TO THE BANK ");

text.setFont(new Font("Osward", Font.BOLD, 32));
text.setForeground(Color.black);
text.setBounds(200, 50, 450, 40);
add(text);

JLabel AccountNo = new JLabel("Account no");

AccountNo.setFont(new Font("Raleway", Font.BOLD, 24));
AccountNo.setBounds(100, 320, 200, 40);
add(AccountNo);

AccountTextField = new JTextField();

AccountTextField.setBounds(250, 325, 300, 33);
AccountTextField.setFont(new Font("Arial", Font.BOLD, 15));
AccountTextField.setCaretColor(Color.blue);
add(AccountTextField);

JLabel pin = new JLabel("Password");

pin.setFont(new Font("Raleway", Font.BOLD, 24));

53
 pin.setBounds(110, 390, 200, 40);
add(pin);

pinTextField = new JPasswordField();

pinTextField.setBounds(250, 395, 300, 33);
pinTextField.setFont(new Font("Arial", Font.BOLD, 15));
pinTextField.setCaretColor(Color.blue);
add(pinTextField);

login = new JButton("LOGIN");

login.setBounds(250, 480, 120, 30);
login.setBackground(Color.black);
login.setForeground(Color.white);
login.addActionListener(this);
add(login);

signup = new JButton("SIGNUP");

signup.setBounds(390, 480, 120, 30);
signup.setBackground(Color.black);
signup.setForeground(Color.white);
signup.addActionListener(this);
add(signup);

reset = new JButton("RESET");

reset.setBounds(250, 520, 260, 30);
reset.setBackground(Color.black);
reset.setForeground(Color.white);
reset.addActionListener(this);
add(reset);

getContentPane().setBackground(new Color(204, 229, 255));

setSize(1600, 1200);
setVisible(true);
}

54
 @Override
public void actionPerformed(ActionEvent ae) {
/// perform sign-in , signUp, reset

if (ae.getSource() == reset) {
AccountTextField.setText(" ");
pinTextField.setText("");
} else if (ae.getSource() == login) {
ConnectionSql c = new ConnectionSql();
String Accountno = AccountTextField.getText();
String pin = pinTextField.getText();
String query = "select *from login where Account_No = '" +
Accountno + "' and Login_Password = '" + pin + "'";
try {
ResultSet rs = c.s.executeQuery(query);
if (rs.next()) {
setVisible(false);
new Transactions(pin,Accountno).setVisible(true);
}
}

public static void main(String[] args) {

new Login1();

}
}

55
CHAPTER- 8
Testing

56
Testing:
 Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. In fact,
testing is the one-step in the software engineering process that could be
viewed as destructive rather than constructive.
 A strategy for software testing integrates software test case design
methods into well-planned series of steps that result in the successful
construction of software. Testing is the set of activities that can be
planned in advance and conducted systematically. The underlying
motivation of program testing is to affirm software quality with methods
that can economically and effectively apply to both strategic to both large
and small-scale systems.

8.2. UNIT TESTING

 Unit testing involves test planning, test case development and

measurement of test unit against the requirement specifications.
Planning involves designing the schedule, determining the resources
required and determining the features to be tested. Test case
development involves designing test cases that are to be tested; the test
cases are prepared so as to test the system exhaustively to find the bugs
present in the system. Measurement of test unit against specification
involves testing the system by giving the test cases as input and
checking the systems adherence to its specification. The following
features were tested:
• Test to see if the requirements specified are taken care of.
• Test to see if all the inputs are handled effectively.
• Test the system by traversing all paths to discover any surprises.
• Check if the errors and exceptions have been handled properly.

• See if the VA libations of input data are all taken care off. Test cases were
designed to check the results retrieved from the database and the validation of
all user inputs. All the modules were tested thoroughly. The module interface
was also tested to ensure that information flows into and out of the program
units.

57
8.3. INTEGRATION TESTING

 This testing is performed after all individual modules are developed and
ready for the integration. The objective of this testing is to build a
program structure as dictated in the design by taking unit tested modules.

REQUIREMENT TO BE TESTED
 The following requirements will be tested1. Verify if valid users are
identified.2. Verify if invalid users are blocked from logging into the
application.

GET REPORTGENERATION DETAILS

 This service validates fetches the account details given an account Id
down integration is an incremental approach to the construction of
program structure. Modules are integrated by moving downward through
the control hierarchy, beginning with the main module. Modules
subordinate to the main module are incorporated into the structure in
depth first manner. In this way, interfacing between the various modules
was also thoroughly tested. In this System, the integration testing is done
by checking all possible workflows of the analysis and cleaning process.

8.4. SYSTEM TESTING

 System Testing is a series of test, which have to be performed to fully

exercise the computer- based system. It ensures that all the system
elements are fully integrated and each element performs its allocated
function.

58
 Chapter-9
Screen Layouts

59
Welcome Page:

Balance Page:

60
Welcome Bank:

Customer Welcome:

61
Withdraw Page

Change PIN:

62
Additional Details:

Account Details:

63
 Chapter-9
Maintenance

64
Maintenance

 Software maintenance is widely accepted part of SDLC. It stands for all

the modifications and updating done after the delivery of software
product. There are number of reasons, why modifications are required,
some of them are briefly mentioned below:
1. Market Conditions- Policies, which changes over the time, such as
taxation and newly introduced constraints like, how to maintain
bookkeeping, may trigger need for modification.
2. Client Requirements - Over the time, customer may ask for new features
or functions in the software.
3. Host Modifications- If any of the hardware and/or platform (such as
operating system) of the target host changes, software changes are
needed to keep adaptability.
4. Organization Changes - If there is any business level change at client
end, such as reduction of organization strength, acquiring another
company, organization venturing into new business, need to modify in
the original software may arise.

Types of Maintenance

 In a software lifetime, type of maintenance may vary based on its nature.

It may be just a routine maintenance tasks as some bug discovered by
some user or it may be a large event in itself based on maintenance size
or nature. Following are some types of maintenance based on their
characteristics:

1. Corrective Maintenance - This includes modifications and update ions

done in order to correct or fix problems, which are either discovered by
user or concluded by user error reports.

2. Adaptive Maintenance - This includes modifications and update ions

applied to keep the software product up-to date and tuned to the ever
changing world of technology and business environment.

65
 3. Perfective Maintenance - This includes modifications and updates done
in order to keep the software usable over long period of time. It includes
new features, new user requirements for refining the software and
improve its reliability and performance.

4. Preventive Maintenance - This includes modifications and updating to

prevent future problems of the software. It aims to attend problems,
which are not significant at this moment but may cause serious issues in
future.

Maintenance Activities

 IEEE provides a framework for sequential maintenance process

activities. It can be used in iterative manner and can be extended so that
customized items and processes can be included.

These activities go hand-in-hand with each of the following phase:

1. Identification & Tracing - It involves activities pertaining to identification of

requirement of modification or maintenance. It is generated by user or
system may itself report via logs or error messages. Here, the
maintenance type is classified also.

2. Analysis - The modification is analysed for its impact on the system

including safety and security implications. If probable impact is severe,
alternative solution is looked for. A set of required modifications is then
materialized into requirement specifications. The cost of
modification/maintenance is analysed and estimation is concluded.

3. Design - New modules, which need to be replaced or modified, are

designed against requirement specifications set in the previous stage.
Test cases are created for validation and verification.

66
4. Implementation - The new modules are coded with the help of structured
design created in the design step. Every programmer is expected to do
unit testing in parallel.

5. System Testing - Integration testing is done among newly created

modules. Integration testing is also carried out between new modules
and the system. Finally, the system is tested as a whole, following
regressive testing procedures.

6. Acceptance Testing - After testing the system internally, it is tested for

acceptance with the help of users. If at this state, user complaints some
issues they are addressed or noted to address in next iteration.

7. Delivery - After acceptance test, the system is deployed all over the
organization either by small update package or fresh installation of the
system. The final testing takes place at client end after the software is
delivered. Training facility is provided if required, in addition to the hard
copy of user manual.

8. Maintenance management - Configuration management is an essential

part of system maintenance. It is aided with version control tools to
control versions, semi-version or patch management.

67
 CHAPTER-10

CONCLUSION & SCOPE FOR

FUTRURE DEVLOPMENT

68
Limitation of Project on Bank Management System:

 Although I have put my best efforts to make the software flexible easy to
operate but limitation cannot be ruled out even by me .Though the
software present a broad range of operations to its users intricate option
could not covered into it; party because of logistic and party due to lack
of sophistication .Paucity of time was also major constraint, thus it was
not possible to make the software fool proof and dynamic lack of time
also compelled me to ignore some part such as storing old result of the
candidate etc. Considerable efforts have made the software easy to
operate even for the people not related to the field of component but it is
acknowledgement that a layman may find it a bit problematic at the first
instance.

10.1 Conclusion

 This project was successfully completed within the time span allotted.
The project Bank Management System has been developed in core java.
All the modules are tested separately and put together to form the main
system. Finally, the system is tested with real data and everything
worked successfully. Thus the system has fulfilled the entire objective
identified. The system had been developed in an attractive dialogs
fashion. So user with minimum knowledge about computers can also
operate the system easily. It will make easy interactions between users
and store. The speed and accuracy are maintained in proper way.

10.2 SCOPE FOR FUTURE DEVELOPMENT

 This project was developed to fulfil user requirement. However, there are
lots of scope to improve the performance of the Banking System in the
area of user interface, database performance and query processing time.
So there are many things for future enhancement of this project. The
future enhancements that are possible in the project are as follows.

69