Bank Management system Systemreport.docx

Banking management system

1. PIRENS INSTITUTE OF BUSINESS MANAGEMENT AND
ADMINSTRATION (IBMA)
PROJECT REPORT ON
“BANK MANAGEMENT SYSTEM ”
FOR
IBMA
AP:-Loni. Tel:-Rahata
Dist:- Ahmednagar.
SUBMITTED
TO
SAVITRIBAI PHULE PUNE UNIVERSITY
BY
Mr.Rohit Raju Bodhak
FOR PARTIAL FULFILMENT
OF
MCA
FOR THE ACADEMIC
YEAR 2022-2023
1

2. Project report
On
“BANK MANAGEMENT SYSTEM ”
Submitted By: Guided :
1.Rohit Bodhak prof:M.S. langote sir



2

3. CERTIFICATE

This is to certify that Mr : Rohit Raju Bodhak of Mca has
Satisfactorily carried out the required practical work according to the
syllabus of University of Pune during the academic year 2022-2023.This
journal represents his benefited work.
Date: _____________

Prof: M S Langote External Examiner Director
(Project Guide)

3

4. ACKNOWLAGEMENT
The satisfaction that accompanies that the successful completion of
any task would be incomplete without the mention of people whose
ceaseless cooperation made it possible, whose constant guidance and
encouragement crown all efforts with success.
We are grateful to our project guide Prof.langote Sir for guidance,
inspiration and constructive suggestions that helpful us in the preparation
of this project.
We also thank our colleges who have helped in successful completion
of the project.
Name:
1)Rohit Raju bodhak

4

5. INDEX
5
SR.NO.
TITLE PAGE NO.
1. INTRODUCTION
1.2 Existing System
1.3 Scope And Objective Of System
1.4 System Configuration- Hardware and Software
2. PROPOSED SYSTEM
2.1 Advantages of Proposed System
3. FEASIBILITY STUDY
3.1 Technical Feasibility
3.2 Economical Feasibility
3.3 Operational Feasibility
4. ANALYSIS AND DESIGN
4.1 Entity Relationship Diagram
4.2 Data Flow Diagram
4.3 Data Dictionary & Tables
4.4 Forms
4.5 Report
4.6 Testing Procedure and Implementation Phase
5. USER MANUAL
5.1 Advantages of Computerized System
5.2 Conclusion
5.3 Bibliography

6. 1. INTRODUCTION TO SYSTEM
A system is an organized set of functional units or components. Central
Bank , by this definition is a system with various objectives. It consists of
inter-related subsystems such as Deposit Department, Withdrawn Department.
None of these sub-systems can perform independent of the others. This means
that proper co-ordination is required between the various departments for the
smooth and effective functioning of Central Bank as a whole.
The “Banking Management System” plays in important role of
maintaining all the transaction records daily as well as customers records. It
needs to allot customers to a account number. The system has to help to
maintain all transactions related to the banking. The details such as account
number , account holder name , balance amount are to be stored. The manager
has the right to add , delete or modify the customers entry. The system also
maintains records of customers to whom the withdrawn money is issued &
Deposit money.
1.2 EXISTING SYSTEM
6

7. The present system of the company is done manually. It contains
production, stock management. The process of production & Stock
Management System is as follows:-
1)According to the oral (telephonic or face to face) order vendor sends
the material.
2)According to the material received the sales rate is calculated for
particular product.
3)After Sales the item is reduced from stock register.
4)All Expenses are calculated.
5)Festally work.
1.3 SCOPE AND OBJECTIVE OF SYSTEM
7

8. We have developed a project named ,“ BANKING MANAGEMENT
SYSTEM ” . This system helps maintain all transactions related to the bank.
The details such as account number , account holder name , balance amount are
stored so that the user can see the details of the customer on the computer itself.
The branch manager has the right to add , delete or modify the customer
entry. The system also maintains records of customers to whom the loan is
issued & when it is returned.
Limitation of the System :
System cannot worth in Heterogeneous environment
Proper training has to be provided to employees.

Aim
In the existing system the transactions are done only manually but
in proposed system we have to computerize all the banking transaction using the
software Banking System. They are: Administrative Module
Administrative Module
8

9. This module is the main module which performs all the main
operations in the system. The major operations in the system are:
Account Opening Form
Deposit
Withdrawal
Account type
Searching Transaction
Transaction report
1.4SYSTEM CONFIGURATION
9

10. HARDWARE CONFIGURATION:
Processor: - Intel Core i3
RAM: - 4 GB SD-RAM.
Hard Disk: -1 TB.
Monitor: - 15” LED.
Mouse.
Printer: - For print report or Bill.
Floppy Disk Drive: - 1.44MB.
SOFTWARE CONFIGURATION
Operating System : Windows 7, Windows 10;Linux;
Language: Java Programming
Database : MS Access2007.
Front End : Java Development Toolkit 8.0(jdk8),Eclips(Oxyzen),NetBean 8.0.
Back end : MS Access2007.
2. PROPOSED SYSTEM
10

11. The proposes system takes care of requirement related aspects. This
system is build taking into consideration all the flaws of the existing system and
as per the users requirement for the proposal.
The system incorporates all the requirement suggested by the user .”
BANK MANAGEMENT SYSTEM” manages all the data about the sales and
purchases of the BANK MANAGEMENT SYSTEM and also provides the
report’s.
The proposed system will have the following features:
Management of in inventory data like sales, purchase etc.
Fully customized look and feel.
Generation of various reports through various criterions.
Strong database security with encryption.
Very user friendly with various messages , warnings, in simple so that
user can understand by himself.
The aim of proposed system is to develop a system of improved
facilities. The proposed system can overcome all the limitations of the existing
system. The system provides proper security and reduces the manual work.
2.1 ADVANTAGES OF PROPOSED SYSTEM
11

12. The system is very simple in design and to implement. The system
requires very low system resources and the system will work in almost all
configurations. It has got following features
Security of data.
Ensure data accuracy’s.
Proper control of the higher officials.
Reduce the damages of the machines.
Minimize manual data entry.
Minimum time needed for the various processing.
Greater efficiency.
Better service.
User friendliness and interactive.
Minimum time required.
2. FEASIBILITY STUDY
12

13. Feasibility study is the test of the system proposal according to its
workability impact on the organization. It is the ability to meet the user needs
and effective use of the resources. Feasibility study evaluates the cost and
benefits of the proposed application. To do so, it is first necessary to analyze the
problem, at least at a global level.
In short, the feasibility study tries to anticipate future scenarios of
software development for a particular problem when the available information
is still fuzzy. Feasibility study tries to anticipate future scenarios of
software development . There are three major aspects of feasibility study
3.1 Technical Feasibility Study
The technical feasibility always focuses on the existing computer
hardware , software & personnel . This also include the need for more
hardware or software or personnel & possibility of procuring / installing
such facility .
The proposed system is ware of that LAN with round about to
nodes . A main computer & other personal computer can be used & the
whole system should be online . Besides this we need to bye UPS
stabilizer & account which installed in the CPU itself .
3.2 Economical Feasibility Study
This feasibility is helpful to find the system development cost
& checks whether it is justifiable for that it checks , investigation cost ,
software & hardware cost , training cost , salaries , maintenance cost etc.
In Training Center if we use computerized system then there will
be tremendous increased in speed & occupancy of system & obviously it
will help to increase the profit & also improved the quality of services.
3.3 Operational Feasibility Study
13

14. It considers the acceptability of the system . It checks whether
system will be used if it is developed & implemented are the user of
system able to handle the system , whether the proposed system cause any
trouble.
The solution to be operational feasible , it is essential for the
analyst to be in contact with the end user through the development of the
system , so that the analyst is aware of the problems of the end user .
The positive aspect is that the work , which will normally require several
days , can be accomplish within few hours .
3.4 Behavioral Feasibility Study
This includes the following questions:
1.Is there sufficient support for the users?
2.Will the proposed system cause harm?
The project would be beneficial because it satisfies the objectives when
developed and installed. All behavioral aspects are considered carefully and
conclude that the project is behaviorally feasible.
4. ANALYSIS AND SYSTEM DESIGN
14

15. 1.Analysis
System analysis is a process of gathering and interpreting facts,
diagnosing problems and the information to recommend improvements on the
system. It is a 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 development process.
The system is studied to the minutest detail and analyzed. 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 concerned with becoming aware of the problem,
identifying the relevant and decisional variables, analyzing 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 interviews, questionnaires 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 problem areas are identified. The
designer now functions as a problem solver and tries to sort out the difficulties
that the enterprise faces.
4. SYSTEM DESIGN

15

16. INTRODUCTION :
Design is the first step into the development phase for any engineered
product or system. Design is a creative process. A good design is the key to
effective system. The term “design” is defined as “the process of applying
various techniques and principles for the purpose of defining a process or a
system in sufficient detail to permit its physical realization”. It may be defined
as a process of applying various techniques and principles for the purpose of
defining a device, a process or a system in sufficient detail to permit its physical
realization. Software design sits at the technical kernel of the software
engineering process and is applied regardless of the development paradigm that
is used. The system design develops the architectural detail required to build a
system or product. As in the case of any systematic approach, this software too
has undergone the best possible design phase fine tuning all efficiency,
performance and accuracy levels. The design phase is a transition from a user
oriented document to a document to the programmers or database personnel.
System design goes through two phases of development: Logical and Physical
Design.
Module Design
Admin
16

17. The Administrator logs in using the admin login. In this module two
operations are done. During login the Login and Password is verified with that
in the database
Input Design
The design of input focuses on controlling the amount of input required,
controlling the errors, avoiding delay, avoiding extra steps and keeping the
process simple. The input is designed in such a way so that it provides security
and ease of use with retaining the privacy. Input Design considered the
following things:
What data should be given as input? o How the data should be arranged
or coded? o The dialog to guide the operating personnel in providing input. o
Methods for preparing input validations and steps to follow when error occur.
Output Design
A quality output is one, which meets the requirements of the end user
and presents the information clearly. In output design it is determined how the
information is to be displaced for immediate need and also the hard copy output.
It is the most important and direct source information to the user. Efficient and
intelligent output design improves the system’s relationship to help user
decision-making.
Designing computer output should proceed in an organized, well thought
out manner; the right output must be developed while ensuring that each output
element is designed so that people will find the system can use easily and
effectively. When analysis design computer output, they should :
Identify the specific output that is needed to meet the requirements.
Select methods for presenting information.
Create document, report, or other formats that contain information
produced by the system.
System Implementation
Implementation is the stage of the project where the theoretical design is
turned into a working system. It can be considered to be the most crucial stage
17

18. in achieving a successful new system gaining the users confidence that the new
system will work and will be effective and accurate. It is primarily concerned
with user training and documentation. Conversion usually takes place about the
same time the user is being trained or later. Implementation simply means
convening a new system design into operation, which is the process of
converting a new revised system design into an operational one.
System Testing
Software Testing is the process of executing software in a controlled manner,
in order to answer the question - Does the software behave as specified?.
Software testing is often used in association with the terms verification and
validation. Validation is the checking or testing of items, includes software, for
conformance and consistency with an associated specification. Software testing
is just one kind of verification, which also uses techniques such as reviews,
analysis, inspections, and walkthroughs. Validation is the process of checking
that what has been specified is what the user actually wanted.
Validation : Are we doing the right job?
Verification : Are we doing the job right?
Software testing should not be confused with debugging. Debugging is the
process of analyzing and localizing bugs when software does not behave as
expected. Although the identification of some bugs will be obvious from
playing with the software, a methodical approach to software testing is a much
more thorough means for identifying bugs. Debugging is therefore an activity
which supports testing, but cannot replace testing. Other activities which are
often associated with software testing are static analysis and dynamic analysis.
Static analysis investigates the source code of software, looking for problems
and gathering metrics without actually executing the code. Dynamic analysis
looks at the behavior of software while it is executing, to provide information
such as execution traces, timing profiles, and test coverage information.

Test Plan
18

19. A test plan implies a series of desired course of action to be followed in
accomplishing various testing methods. The Test Plan acts as a blue print for the
action that is to be followed. The software engineers create a computer program,
its documentation and related data structures. The software developers is always
responsible for testing the individual units of the programs, ensuring that each
performs the function for which it was designed. There is an independent test
group (ITG) which is to remove the inherent problems associated with letting
the builder to test the thing that has been built. The specific objectives of testing
should be stated in measurable terms. So that the mean time to failure, the cost
to find and fix the defects, remaining defect density or frequency of occurrence
and test work-hours per regression test all should be stated within the test plan.
The levels of testing include:
Unit testing
Integration Testing
Data validation Testing
Output Testing

Unit Testing
Unit testing focuses verification effort on the smallest unit of software
design – the software component or module. Using the component level design
description as a guide, important control paths are tested to uncover errors
19

20. within the boundary of the module. The relative complexity of tests and
uncovered scope established for unit testing. The unit testing is white-box
oriented, and step can be conducted in parallel for multiple components.
The modular interface is tested to ensure that information properly flows
into and out of the program unit under test. The local data structure is examined
to ensure that data stored temporarily maintains its integrity during all steps in
an algorithm’s execution. Boundary conditions are tested to ensure that all
statements in a module have been executed at least once. Finally, all error
handling paths are tested.
Tests of data flow across a module interface are required before
any other test is initiated. If data do not enter and exit properly, all other tests
are moot. Selective testing of execution paths is an essential task during the unit
test. Good design dictates that error conditions be anticipated and error handling
paths set up to reroute or cleanly terminate processing when an error does occur.
Boundary testing is the last task of unit testing step. Software often fails at its
boundaries.
Unit testing was done in Sell-Soft System by treating each
module as separate entity and testing each one of them with a wide spectrum of
test inputs. Some flaws in the internal logic of the modules were found and were
rectified.
Integration Testing
Integration testing is systematic technique for constructing the program
structure while at the same time conducting tests to uncover errors associated
with interfacing. The objective is to take unit tested components and build a
20

21. program structure that has been dictated by design. The entire program is tested
as whole. Correction is difficult because isolation of causes is complicated by
vast expanse of entire program. Once these errors are corrected, new ones
appear and the process continues in a seemingly endless loop.
After unit testing in Sell-Soft System all the modules were integrated to test
for any inconsistencies in the interfaces. Moreover differences in program
structures were removed and a unique program structure was evolved.

Validation Testing
This is the final step in testing. In this the entire system was tested
as a whole with all forms, code, modules and class modules. This form of
testing is popularly known as Black Box testing or System testing.
Black Box testing method focuses on the functional requirements of the
software. That is, Black Box testing enables the software engineer to derive
sets of input conditions that will fully exercise all functional requirements for a
program.
Black Box testing attempts to find errors in the following categories;
incorrect or missing functions, interface errors, errors in data structures or
external data access, performance errors and initialization errors and termination
errors.
Output Testing
The system considered is tested for user acceptance; here it should
satisfy the firm’s need. The software should keep in touch with perspective
system; user at the time of developing and making changes whenever required.
This done with respect to the following points
Input Screen Designs,
21

22. Output Screen Designs,
Online message to guide the user and the like.
The above testing is done taking various kinds of test data. Preparation of test
data plays a vital role in the system testing. After preparing the test data, the
system under study is tested using that test data. While testing the system by
which test data errors are again uncovered and corrected by using above testing
steps and corrections are also noted for future use.
Training
Once the system is successfully developed the next important step is
to ensure that the administrators are well trained to handle the system. This is
because the success of a system invariably depends on how they are operated
and used. The implementation depends upon the right people being at the right
place at the right time. Education involves creating the right atmosphere and
motivating the user. The administrators are familiarized with the run procedures
of the system, working through the sequence of activities on an ongoing basis.
Implementation is the state in the project where the theoretical design is
turned into a working system. By this, the users get the confidence that the
system will work effectively. The system can be implemented only after
through testing.
The systems personnel check the feasibility of the system. The actual data
were inputted to the system and the working of the system was closely
monitored. The master option was selected from the main menu and the actual
data were input through the corresponding input screens. The data movement
was studied and found to be correct queries option was then selected and this
contains various reports.
4.1 ENTITY RELATIONSHIP DIAGRAM
22
SUBMIT
WITHDROW

23. M M M
1 1 1

4.2 DATA FLOW DIAGRAM (DFD)
1.2.1CONTEXT LEVEL DFD
23
EMPLOYEE
DEPOSIT
SUBMIT

24. 2. A/C Details Customer Details
3.
4. Customer Details
5. 0.0 A/C Details
Employee Details
6.
Employee Details
Salary Details A/C Details
7. Salary Details
4.2.2 FIRST LEVEL DFD
24
Bank Management
System
0.0
Account
Customer
Employee
Salary
Customer
Account
Management

25. 4.2.3 REPORT
25

26. 26

27. 4.3 DATA DICTIONARY
27

28. Customer information table
Sr.no Field nameData typeWidth Constraint
1 A/c Opening
Type
Varchar 25 Not Null
2 Customer A/C noInt 15 p.k
3 Date Date - Not Null
4 Customer TypeVarchar 30 Not Null
5 First Name Varchar 15 Not Null
6 Middle Name Varchar 15 Not Null
7 Last Name Varchar 15 Not Null
8 Mother Name Varchar 15 Not Null
9 Marital StatusVarchar 30 Not Null
10 Date of BirthDate - Not Null
11 Gender Varchar 20 Not Null
12 Place Of BirthVarchar 30 Not Null
13 Nationality Varchar 35 Not Null
14 Country Varchar 30 Not Null
15 State Varchar 30 Not Null
16 District Varchar 35 Not Null
17 Tal Varchar 35 Not Null
18 Current AddressVarchar 35 Not Null
19 Mobile No Int 30 Not Null
20 E-mail Id Varchar 35 Not Null
21 Education Varchar 35 Not Null
22 Religion Varchar 30 Not Null
23 Category Varchar 30 Not Null
24 Occupation Varchar 30 Not Null
25 Line of BusinessVarchar 35 Not Null
26 Religion Varchar 30 Not Null
27 Annual IncomeInt 25 Not Null
28 Sources of
Income
Int 25 Not Null
29 Vehicles Varchar 30 Not Null
4.3.2 TABLES
1)Account Type :
28

29. Sr.noField name Data typeWidth Constraint
1 AccountType Text 20 Not Null
2 Description Text 30 p.k
3 MinimumBalanc
e
Currency 30 Not Null
4 Rate Number 30 Not Null
2) Check Book Detail:
Sr.noField name Data typeWidthConstraint
1 CheckBookNumbe
r
Text 20 p.k
2 AccountNumber Text 30 Not Null
3 DateIssued Date/Time 30 Not Null
4 StartNumber Number 30 Not Null
3) Customer Detail :
Sr.noField nameData typeWidth Constraint
1 AccountNumber Text 20 p.k
2 First Name Text 30 Not Null
3 LastName Text 30 Not Null
4 OfficeAddres Text 30 Not Null
5 HomeAddres Text 30 Not Null
6 DateOfBirth Date/Time 30 NotNull
7AccountType Text 30 NotNull
8Gender Text 30 NotNull
4) Customer Query :
29

30. Sr.noField nameData typeWidth Constraint
1 QueryId Text 20 p.k
2 AccountNumber Text 30 Not Null
3 Query Text 30 Not Null
4 Status Text 30 Not Null
6 DateReceived Date/Time 30 NotNull
5) Stop Payment :
Sr.noField nameData typeWidth Constraint
1 CheckNumber Text 20 p.k
2 AccountNumber Text 30 Not Null
3 Instruction Text 30 Not Null
6) Transactions:
Sr.noField nameData typeWidth Constraint
1 TransactionId Int 20 p.k
2 TransationDat
e
Varchar 30 Not Null
7 )User’s:
Sr.noField nameData typeWidth Constraint
1 LoginId Text 20 NotNull
2 EmployeeId Text 30 p.k
3 Password Text 30 Not Null
4 Role Text 30 NotNull
30

31. 8) Withdrawn Table :
Sr.noField nameData typeWidth Constraint
1 Date Date 20 Not Null
2 Cust Id Int 30 p.k
3 WithdroAmoun
t
Int 30 Not Null

9) Deposite Table :
Sr.noField nameData typeWidth Constraint
1 Date Date 20 Not Null
2 Cust Id Int 30 p.k
3 DepoAmount Int 30 Not Null
31

32. 4.4 FORMS
A)Login Form :-
B)Home Page (MDI Forms):-
32

33. C)MDI Form Menu :-
1)File :-
Sub Menu :-
i)Open New Account :-
33

34. ii)Print Customer Balance :-
34

35. 2)Edit :-
Sub Menu :-
i)Deposit Money :-
35

36. ii)Withdraw Money :-
iii)Delete Account Holder :-

36

37. iv)Search Customer Account :-
3)View :-
37

38. Sub Menu :-
i)View One By One Customer Account :-
ii)View All Customer Details :-
38

39. 4)Options :-
5)Window :-
39

40. 6)Help :-
Sub Menu :-
i)Help Contents :-
40

41. ii)Help On Shortcuts :-
iii)About Bank System :-
41

42. 7)Quit Bank System …?
Commands :-

42

43. 4.5 REPORTS

User can select the reports he wants from Reports Navigation
List box. The Reports are shown on screen and if user wishes to take its print,
he may do so by selecting proper option from the browser.
This can be eliminated by providing training & testing about
funds of computers and its applications. The user gives position response
towards new computerized system, because decrease in their workload. When
any system is implemented then the users satisfaction get first preference. The
users satisfaction means real implementation of system. The user gets satisfies
only and when he required outputs.
43

44. 8.USER MANUAL
The user manual is presented over here to handle system without any
problem and it could guide through out for the “Bank Management System”.
The user manual has not been developed the knowledge of programming. Once
the system is installed on the on the disk, you can run system by clicking this
will display the password screen.
The user supposed to enter the password so as to get access to the
system. if the user enters incorrect password for three times then access to the
system is denied. User can also change user-id or password. Entering the
correct password will give access to system and menu screen will be displayed.
User can perform all the operations like data entry, updating
to the data and generation of reports through this menu.
This menu comprises following options.
1.File
2.Edit
3.View
4.Options
5.Window
6.Help

44

45. Transaction Screen
All the transaction screen contains Header and Detail
Part. User can view in the Text Box & List View provide on the screen. Also
the transaction screens are provided with Add, Edit, Save, and Delete buttons.
All these are enabled while adding new record. But once the record is saved,
system does not allow any changes to the record and this entire buttons are
disabled. This help to avoid data conflicts in the system.
Following are the submenus under transaction menu:
1. Deposit Money
2) Transfer Money
2. Withdrawn Money

45

46. 6.2 CONCLUSION
At the beginning of the implementation phase of the system, it is being
that users are quit attracted towards new computerized system, but when they
come to know the miracles of the system. They become more and more
interested and preferred work with computer. But they don’t have sufficient
knowledge about computers.
This can be eliminated by providing training & testing about funds of computers
and its applications. The user gives position response towards new
computerized system, because decrease in their workload. When any system is
implemented then the users satisfaction get first preference. The users
satisfaction means real implementation of system. The user gets satisfies only
and when he required outputs.
Commendable features of the project.
1.User Friendly.
2.Man hours saving.
3.To an extent pays way for paper less office.
4.Variety of report generation.
5.Easy backup and indexing.
6.Properly documented.
46

47. 5.3 BIBLIOGRAPHY
ONLINE REFERENCE:
1.http://www.javaworld.com/ java programming world/jw-01-1998/vb-01-
bookreview.html
2.Database Programming with Java and JDK 8.0 by O'Reilly
3.Head First JDK 8.0 Edition
4.http://www.Eclips-tutorial.com/
5.www.w3schools.com
6. www.theserverside.com
7.www.programming.com
BOOKS:
1.Charles Hampfed (2000) ‘Java Programming’ University of
Toronto
2.Herbert Schildt (2000) ‘Core Java’ Tata McGraw Hill.
3.John Zukowski (2000) ‘java programming ‘BPB Publications
4.Jamie Jaworsky ‘NetBean 8.0’Techmedia
5.Stefen Denninger ‘JVM 8.0’Author’s Press
6.Elmasri Navathe ‘Fundamentals of database systems’
47