BANK MANAGEMENT SYSTEM

Project report Submitted in partial

fulfillment of the Requirements
for the award of the Degree

BACHELOR OF SCIENCE
In
INFORMATION TECHNOLOGY
By

Nikhil Surendra Pandey

DEPARTMENT OF
INFORMATION TECHNOLOGY
ANNASAHEB VARTAK COLLEGE OF
SCIENCE AND ENGINEERING
(Affiliated to University of mumbai)
MUMBAI,400064
MAHARASHTRA
2023-2024

ANNASAHEB VARTAK COLLEGE

OF SCIENCE AND ENGINEERING
 (Affiliated to University of mumbai)

MUMBAI- MAHARASHTRA-400064
DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE
This is to certify that the project entitled, "BANK MANAGEMENT SYSTEM ", is bonafied
work of Nikhil Surendra Pandey bearing Seat.No: submitted in partial fulfillment of
the requirements for the award of degree of BACHELOR OF SCIENCE in INFORMATION
TECHNOLOGY from University of Mumbai.

INTERNAL GUIDE COORDINATOR

EXTERNAL EXAMINER

DATE: COLLEGE SEAL

 ABSTRACT
This project is aimed at developing an Online Banking for customer. The system is an online
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 DB and all the user interfaces have
been designed using the ASP.NET. The database connectivity is planned using the “Database”
methodology. The standards of security and data protective mechanism have 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 by the
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 Oracle.

The basic constructs of table spaces, clusters and indexes have been exploited to provide
higher consistency and reliability for the data storage. The Oracle was a choice as it provides
the constructs of high-level reliability and security. The total front end was dominated using
the ASP.NET 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.
 ACKNOWLEDGEMENT
This project would not have taken shape without the contributions of many who have
extended help in one or the way. I would like to take this opportunity to express my thanks to
my father and mother who have provided the entire moral backing and encouragement all
through the course duration. In particular my father motivated me to go alone for this project
and his practical knowledge in designing the systems was greatly helpful.

A discussion on the project work, with my seniors in the college was also great source of help
and without which it would not have been possible to achieve the results reported in this
project.

I extend my gratefulness to my institute’s library and its members for their support and
heartfelt thanks to all the faculty members of the college Last but not the least I would like to
thank my family and my well-wishers. Without you all this project would have been a distant
reality.
 DECLARATION
I hereby declare that the project entitled, “BANK MANAGEMENT SYSTEM” done at place
where the project is done, has not been in any case duplicated to submit to any other
university for the award of any degree. To the best of my knowledge other than me, no one
has submitted to any other university.

The project is done in partial fulfillment of the requirements for the award of degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final
semester project as part of our curriculum.

Mr. Nikhil Surendra Pandey

 TABLE OF CONTENTS
Chapter 1: Introduction
1.1 Background
1.2 Objectives
1.3 Purpose and Scope
1.2.1Purpose
1.2.2Scope
Chapter 2: System Analysis
2.1Existing System
2.2Proposed System
2.3Requirement Analysis
2.4Hardware Requirements
2.5Software Requirements
2.6Justification of selection of Technology
Chapter 3: System Design
3.1Module Division
3.2Data Dictionary
3.3ER Diagrams
3.4DFD/UML Diagrams Chapter

Chapter 4: Implementation and Testing

4.1 Code (Place Core segments)
4.2 Testing Approach
4.2.1Unit Testing (Test cases and Test Results)
Chapter 5: Results and Discussions (Output Screens)
Chapter 6: Conclusion and Future Work
Chapter 7: References
 INTRODUCTION
During the past several decades personnel function has been transformed from a relatively obscure record keeping staff to central and top-level management

function. There are many factors that have influenced this transformation like technological advances, professionalism, and general recognition of human beings

as most important resources.

A computer-based management system is designed to handle all the primary information required to
calculate monthly statements of customer account which include monthly statement of any month.
Separate database is maintained to handle all the details required for the correct statement
calculation and generation.

This project intends to introduce more user friendliness in the various activities such as record
updation, maintenance, and searching. The searching of record has been made quite simple as all
the details of the customer can be obtained by simply keying in the identification or account number
of that customer. Similarly, record maintenance and updation can also be accomplished by using the
account number with all the details being automatically generated. These details are also being
promptly automatically updated in the master file thus keeping the record up-to-date.

The entire information has maintained in the database or Files and whoever wants to retrieve cannot
retrieve, only authorization user can retrieve the necessary information which can be easily be
accessible from the file.
 1.1 BACKGROUND

INTRODUCTION TO FRONT END TOOL

 Visual programming aims at providing the user with an interface that is intuitive and easy
to use. In developing such an interface, the programmer employs user-friendly features
such as windows, menus, buttons and list boxes.

 Its Environment provides all features that are required to develop a graphical user
interface as ready -to- use components. The programmer does not have to write code to
create and display commonly required user-friendly features each time around.

 When the programmer needs a specific user interface feature such as button, he selects
the appropriate ready-to-use component provided by the visual programming
environment. These components can be moved, resized and renamed as required.

 For Example:-
If the programmer needs to have a button then the visual programming environment provides
him with one. All that, the programmer does this select the button and place it on screen at the
required position.

 Typically the mouse is used to select and place the necessary components. Thus, the visual
programming environment is also called a point and click environment.

 A visual programming environment automates the process of creating a user interface. The
interface provided by the visual programming environment to the programmer designs the user
interface visually instead of writing code.
 In addition it also provides a means of associating code with each component. In each case of
calculator, for each button, we can specific that the code is to execute when we click on it.

NEED FOR VISUAL PROGRAMMING:-

 There are several programming tools that allow us to build such visually appealing and intuitive
interface. These tools allow us to design interface that employ user friendly features such as
menus, buttons, windows etc.

 However, the disadvantage of such tools is that the interface is designed using code. The
programmer has to code the user interface features specifying the size, position etc. this makes
designing the user interface a major task in itself.

ADVANTAGES OF VISUAL PROGRAMMING:-

 Visual development of graphical user interface which are easy to use and easy to learn.
 A programmer need not write code to display the required component.

 For Example:-
The visual programming environment displays a list of available components. The programmer picks
up the required component from this list to display it.

 The component can be moved, resized and even deleted, if so required.

 There is no restriction on the number of controls that can be placed on a form.
 The interface components provided by the visual programming environment have some code
built into them.
For example:-

A button’ knows’ when it has been clicked upon. In the case of conventional programming tools, the
programmer has to write code to determine the component that has been clicked and then execute
the appropriate code.

 Visual Basic is one of the most popular programming tools available today. And it’s also
secret that there have been massive changes in it as it became Visual Basic.Net.
 The reason of that change is Visual Basic itself, which has now become Visual Basic.Net.
The difference between Visual Basic.Net and the previous version. Visual Basic 6.0 is
revolutionary and far reaching. Visual Basic.Net has been more than four years in the
marking and it represents entirely new directions for Visual Basic. Besides the biggest
change integrated support for web development the very syntax, of techniques that you’ve
probably learned carefully are now completely different such as data handling and many
controls; project types and other aspects of Visual Basic 6.0 are no longer available at all.

 Visual Basic has a long and so far glorious history. When it first appeared, it created a
revolution in windows programming. Visual Basic introduced unheard of ease to
windows programming just builds the program you want right before your eyes, and then
run it. In so doing it changed programming form a chore to something very like fun.
 INTRODUCTION TO BACK END TOOL

Introduction to SQL: -

SQL is a standard computer language for accessing and

manipulating databases.

 SQL stands for Structured Query Language.

 SQL allows you to access a database.
 SQL is an ANSI standard computer language.
 SQL can execute queries against a database.
 SQL can retrieve data from a database.
 SQL can insert new records in a database.
 SQL can delete records from a database.
 SQL can update records in a database.
 SQL is easy to learn.

 SQL is an ANSI (American National Standards Institute) standard computer language 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.

 Unfortunately, there are many different versions of the SQL language, but to be in
compliance with the ANSI standard; they must support the same major keywords in a
similar manner (such as SELECT, UPDATE, DELETE, INSERT, WHERE, and others).
 SQL Database Tables: -

A database most often contains one or more tables. Each table is identified by a name (e.g.
"Customers" or "Orders"). Tables contain records (rows) with data.

Below is an example of a table called "Persons": -

Last Name First Name Address City

Hansen Ola Timoteivn 10 Sandnes

Svendson Tove Borgvn 23 Sandnes

Pettersen Kari Storgt 20 Stavanger

 The table above contains three records (one for each person) and four columns (Last
Name, First Name, Address, and City).

 SQL Queries: -

With SQL, we can query a database and have a result set returned.

 A query like this: -

SELECT Last Name FROM Persons

 Gives a result set like this: -

Last Name

Hansen

Svendson

Petersen

SQL Data Manipulation Language (DML)

 SQL (Structured Query Language) is syntax for executing queries. But the SQL language
also includes syntax to update, insert, and delete records.
 These query and update commands together form the Data Manipulation Language
(DML) part of SQL: -

 SELECT - extracts data from a database table

 UPDATE - updates data in a database table

 DELETE - deletes data from a database table

 INSERT INTO - inserts new data into a database table

SQL Data Definition Language (DDL)

 The Data Definition Language (DDL) part of SQL permits database tables to be created
or deleted. We can also define indexes (keys), specify links between tables, and impose
constraints between database tables.

 The most important DDL statements in SQL are: -

 CREATE TABLE - creates a new database table

 ALTER TABLE - alters (changes) a database table
 DROP TABLE - deletes a database table
 CREATE INDEX - creates an index (search key)
 DROP INDEX - deletes an index MS SQL SERVER 2000

1.2 OBJECTIVES
A computer based management system is designed to handle all the primary information required to
calculate monthly statements of customer account which include monthly statement of any month.
Separate database is maintained to handle all the details required for the correct statement
calculation and generation.

This project intends to introduce more user friendliness in the various activities such as record
updation, maintenance, and searching. The searching of record has been made quite simple as all
the details of the customer can be obtained by simply keying in the identification or account number
of that customer. Similarly, record maintenance and updation can also be accomplished by using the
account number with all the details being automatically generated. These details are also being
promptly automatically updated in the master file thus keeping the record up-to-date.

The main objective of our project is providing the different typed of customers facility, the main
objective of this system is to find out the actual customer service. Etc.

 It should fulfill almost all the process requirements of any Bank.

 It should increase the productivity of bank by utilizing the working hours more and more,
with minimum manpower.
This project includes the entire upgraded feature required for the computerization banking system.
This system is very easy to use, so that any user can use without getting pre-knowledge about this. Its
very much user friendly and meet almost all daily working process requirements. This system is
completely GUI based and can be use by mouse and as well as keyboard. This system is melded in
such a way that has got all features to upgrade without making much change in existing components.
 1.3 PURPOSE AND SCOPE

1.3.1 PURPOSE
The purpose of an online bank management project is to provide a digital platform
for efficiently managing various banking operations and services over the internet.
This type of project aims to offer customers a convenient and user-friendly way to
access and handle their financial transactions and accounts without the need to visit
a physical bank branch. Here are some key purposes and benefits of such a project:

1. Convenience: Online banking allows customers to perform a wide range of

banking activities from the comfort of their own homes or any location with
internet access. This includes checking account balances, transferring funds,
paying bills, and more.
2. 24/7 Availability: Unlike traditional brick-and-mortar banks, online banking
platforms are available 24/7, enabling customers to conduct their banking
activities at any time that suits them.
3. Accessibility: Online banking is accessible to a wider range of customers,
including those with mobility challenges or those who live in remote areas far
from physical bank branches.
4. Efficiency: Online banking systems streamline many processes, reducing the
need for paper-based documentation and minimizing manual data entry. This
can lead to faster transaction processing and reduced errors.
5. Cost Savings: Online banking can reduce operational costs for banks by
minimizing the need for physical infrastructure, such as bank branches and
staff. This potential cost savings can also be passed on to customers in the
form of lower fees or better interest rates.
6. Security: While security is a concern in online banking, modern systems
incorporate robust security measures such as encryption, multi-factor
authentication, and monitoring to protect customer data and transactions.
7. Portfolio Management: Online banking systems often provide tools for
customers to manage their investments, track their portfolios, and access
financial advice.
8. Real-Time Information: Customers can access real-time information about
their account balances, recent transactions, and account history.
9. Mobile Access: Many online banking systems offer mobile apps that allow
customers to perform banking tasks using their smartphones and tablets,
further enhancing convenience and accessibility.
10. Personalization: Online banking platforms can offer personalized financial
insights and recommendations based on a customer's transaction history and
financial goals.
11. Easy Documentation: Customers can easily access and download
statements, tax documents, and other important financial documents from
their online accounts.
12. Quick Customer Support: Online banking often provides customer support
through chat, email, or phone, allowing customers to get assistance without
visiting a physical branch.
1.3.2 FUTURE SCOPE OF THE PROJECT

This project can be handled in future by doing various modifications like: -

 We can go further for Online Banking.

 We can establish and start various Branches and available help centers for Account Holder’s
Queries.

 We can also deal through internet by creating web pages and a banking website for internet
dealing.

 To attract Account Holder’s we can offer various offers during festivals months.

 We can also deal in various types of Banking Transactions.

 To have more and more customer satisfaction we will emphasize more and more on our dealings.
 SYSTEM 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 minutes 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. The solutions are given as proposals.

The proposal is then 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.

2.1 EXISTING SYSTEM

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.

DISADVANTAGES OF EXISTING SYSTEM

 Lack of security of data.

 More man power.

 Time consuming.
 Consumes large volume of pare work.

 Needs manual calculations.

 No direct role for the higher officials.

 Damage of machines due to lack of attention. To avoid all these limitations and make the
working more accurately the system needs to be computerized.

2.2 PROPOSED SYSTEM

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.

ADVANTAGES OF THE PROPOSED SYSTEM

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 accuracies.

 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.3 REQUIREMENTS ANALYSIS

Requirements analysis for a Bank Management System involves understanding and
documenting the specific needs and expectations of stakeholders within a banking
environment. Here's an overview of how to approach requirements analysis for such
a system:

1. Stakeholder Identification:
 Identify key stakeholders such as bank employees (tellers, managers,
administrators), customers, regulatory authorities, and auditors.
 Determine their roles, responsibilities, and requirements within the
bank management system.
2. Gather Initial Requirements:
 Conduct interviews and workshops with stakeholders to gather high-
level requirements.
 Understand the overall goals of the bank, its business processes, and
the pain points stakeholders are experiencing with the current system.
3. Document Requirements:
 Create a requirements document that captures functional and non-
functional requirements.
 Functional requirements should outline specific features and
functionalities needed, such as customer onboarding, account
management, transaction processing, reporting, etc.
 Non-functional requirements should cover aspects like security,
performance, scalability, availability, regulatory compliance, and user
experience.
4. Prioritize Requirements:
 Collaborate with stakeholders to prioritize requirements based on their
criticality and business impact.
 Consider using techniques like MoSCoW (Must have, Should have,
Could have, Won't have) to categorize and rank requirements.
5. Elicit Detailed Requirements:
 Break down high-level requirements into detailed components. For
instance, if the system needs to handle customer onboarding, define
the steps, data fields, and validation rules involved.
 Discuss specific workflows, user interfaces, and data flows with
stakeholders.
6. Validate and Verify Requirements:
 Review the requirements with stakeholders to ensure accuracy,
completeness, and clarity.
 Confirm that the documented requirements align with the bank's
business processes and objectives.
7. Resolve Conflicts:
 Address any conflicting requirements or discrepancies between
different stakeholder groups.
 Work with stakeholders to find suitable compromises and solutions.
8. Create Use Cases and User Stories:
 Develop use cases or user stories that describe how different users
(bank employees and customers) will interact with the system.
 Detail scenarios like customer opening an account, making a deposit,
transferring funds, generating reports, etc.
9. Define Acceptance Criteria:
 Specify clear acceptance criteria for each requirement to determine
when it is considered fulfilled.
 For instance, acceptance criteria for a transaction processing feature
might include response times, error handling, and data accuracy.
10. Review and Feedback:
 Share the detailed requirements, use cases, and user stories with
stakeholders for their review and feedback.
  Incorporate their input to ensure that the requirements accurately
capture their needs.
11. Traceability:
 Establish traceability between requirements, use cases, user stories,
and other project artifacts like design documents and test cases.
 This traceability ensures that each requirement is properly addressed
throughout the development lifecycle.
12. Change Management:
 Implement a change management process to handle any modifications
or additions to requirements as the project progresses.
 Changes should be documented, evaluated for impact, and approved
by relevant stakeholders.
13. Finalize Requirements Document:
 Compile all the gathered and refined requirements into a
comprehensive requirements document.
 This document will serve as the foundation for the subsequent design,
development, testing, and implementation phases of the Bank
Management System project.

Throughout the requirements analysis process, effective communication,

collaboration, and documentation are crucial to ensure that the Bank Management
System effectively meets the needs of all stakeholders and aligns with the bank's
operational objectives and regulatory requirements.

2.4 SOFTWARE REQUIREMENT

SPECIFICATION
SYSTEM SPECIFICATION

HARDWARE REQUIREMENTS
a) Processor : X86 Compatible processor with 1.7 GHz Clock speed

b) RAM : 512 MB or more

c) Hard disk : 20 GB or more

d) Monitor : VGA/SVGA

e) Keyboard : 104 Keys

f) Mouse : 2 buttons/ 3 button

2.5 SOFTWARE REQUIREMENTS
 Operating System : Windows 2000/XP

 Front end : Visual Studio 2008

 Back end : mySQL Server 2005

2.6 Justification of selection of technology

The selection of technology for a bank management system is a critical decision that can
significantly impact the efficiency, security, scalability, and overall success of the system.
The justification for selecting a particular technology stack should be based on a thorough
evaluation of various factors. Here are some key justifications for selecting specific
technologies for a bank management system:

1. Security: Security is paramount in a bank management system due to the sensitive

nature of financial data. The selected technology stack should provide robust security
features, including encryption, authentication, authorization, and protection against
vulnerabilities like SQL injection and cross-site scripting. Justify the chosen
technologies based on their track record of security, regular updates, and compliance
with industry standards (such as PCI DSS for payment processing).
2. Scalability and Performance: Banks deal with a large volume of transactions and
user interactions. The chosen technology stack should be capable of handling the
current load as well as being scalable to accommodate future growth. Justify your
choices by demonstrating how the selected technologies can handle high traffic,
distribute workloads efficiently, and optimize database performance.
3. Integration: A bank management system often needs to integrate with various
external systems and third-party services, such as payment gateways, credit bureaus,
and regulatory reporting systems. Justify the technology choices by showcasing their
compatibility and ease of integration with existing systems, APIs, and industry-
standard protocols.
4. User Experience: A bank management system serves both internal staff and external
customers. Justify your technology stack by explaining how it enables a smooth and
user-friendly interface, responsive design for multiple devices, and efficient data
retrieval and presentation.
5. Data Management: Banks generate and manage a vast amount of data. The selected
technology should provide efficient data storage, retrieval, and processing
capabilities. Justify your choices by highlighting the technologies' data modeling,
database management, and data analytics features.
6. Maintenance and Support: Choose technologies with active communities, ongoing
support, and regular updates. Justify your selections by demonstrating how the chosen
technologies ensure long-term viability, minimize downtime, and facilitate easy bug
fixes and enhancements.
7. Regulatory Compliance: The banking industry is heavily regulated, and the
technology stack should support compliance with relevant regulations such as KYC
(Know Your Customer), AML (Anti-Money Laundering), and data protection laws.
Justify your choices by explaining how the selected technologies facilitate adherence
to these regulations through features like audit trails and data encryption.
8. Cost-effectiveness: Consider the total cost of ownership, including licensing fees,
infrastructure costs, development efforts, and potential training needs. Justify your
technology choices by demonstrating how they provide value for money and align
with the bank's budget and resource constraints.
9. Future Proofing: Technology evolves rapidly, and the selected stack should have a
clear upgrade path and the ability to adopt emerging trends like AI, machine learning,
and blockchain. Justify your choices by explaining how the technologies are future-
ready and adaptable to changing business needs.
10. Team Expertise: Consider the skills and expertise of your development team in
relation to the chosen technologies. Justify your choices by highlighting the team's
familiarity and proficiency with the selected stack, which can lead to faster
development, fewer errors, and smoother implementation.