BACHELOR OF COMPUTER APPLICATIONS

Fifth SEMESTER

BATCH-B

SUBMITTED TO: - SUBMITTED BY:

DR. Chitreshh Banerjee Rohan Pareek

Enrollment No:
A217048220%4

AMITY INSTITUTE OF INFORMATION A N D TECHNOLOGY

AMITY UNIVERSITY RAJASTHAN

 AMITY INSTITUTE OF INFORMATION
TECHNOLOGY

I, Rohan Pareek, Enrolment number –

A21704822054, student of Bachelor of Computer
Applications (BCA), Amity University Rajasthan
hereby declare that I have done my internship from
“Klimax techno” company of “Sales Marketing ”
from 6th June 2024 to 21st July 2024.

Rohan Pareek
BCA 5th sem. A21704822054
Amity Institute of Information Technology
 Acknowledegement
I would like to express my special thanks
of gratitude to my teacher (DR. Chitresh
Banerjee) who gave me the golden
opportunity to do this wonderful project on
the topic (Banking management system),
which also helped me in doing a lot of
Research and i came to know about so
many new things I am really thankful to
them. Secondly i would also like to thank
my parents and friends who helped me a
lot in finalizing this project within the
limited time frame.

I am are over helmed in all humbleness

and gratefulness to acknowledge my
depth to all those who have helped me to
put these ideas, well above the level of
simplicity and into something concrete. I
would like to express my special thanks
of gratitude to my teacher as well as our
principal who gave me the golden
opportunity to do this wonderful project
on the topic “Banking management
system”, which also helped me in doing
a lot of Research and i came to know
about so many new things.
I am really thankful to them. Any attempt
at any level can 't be satifactorily
completed without the support and
guidance of MY parents and friends. I
would like to thank my parents who
helped me a lot in gathering different
information, collecting data and guiding
me from time to time in making this project
, despite of their busy schedules ,they
gave me different ideas in making this
project unique.
Thanking you
Table of Contents
1. Introduction
1.1 Purpose
1.2 Product Scope
1.3 Technologies to be used
1.4 Definition, Acronyms and
Abbreviations
2. Overall Description
2.1 Product Perspective
2.2 User Classes and Characteristics
2.3 Operating Environment
2.4 Software Interfaces
2.5 Hardware Requirements
2.6 Functionalities
2.7 General Constraints
3. System Features
3.1 Functional Requirements
 3.2 Technical Issues
3.3 Non-functional Requirements
4. Design
4.1 Decision tree
4.2 Use Case Diagrams
4.3 Class Diagram
4.4 State chart
4.5 DFD 0 and DFD 1
5. Database Design
5.1 E-R Diagram
6. Future Scope
7. Conclusion
8. Reference
9. bibliography
1) Introduction
1.1 Purpose: The purpose of this document is
to present a detailed description of the
Online Banking System.It will describe the
system's functions, features, interfaces,
what it will accomplish, the limitations it
must work under, and how it will respond
to outside stimuli. This document is meant
for both system developers and
stakeholders, and it will be responsible for
determining if the Bank community
approves or disapproves of the project.
1.2 Scope
An online banking system will be
applicable everywhere, where banking
exists.Compared to the existing banking
system, it will be a more effective and
straightforward method to have records
on systems that anybody can simply
access according to his privileges. Since
online banking offers more convenient
features and faster ways to complete
 transactions than traditional banking
does, all banks will choose it over the latt.
1.3 Technologies to be used:
Web Development: PYTHON , and web
frameworks for the interface, backed by server-
side languages. Database Management:
Use databases like MySQL, PostgreSQL, or No SQL
for data storage. Security: Implement encryption,
multifactor authentication, and security
measures. Payment Processing: Integrate with
payment processors (e.g., Stripe, PayPal). Mobile
Banking: Develop mobile apps for iOS and
Android. Cloud Computing: Hosting on AWS,
Azure, or GCP for scalability and high availability.
API and Integration: Development of API to
connect with third-party services. Compliance:
Adherence to financial regulations such as KYC
and A
Backup and Recovery: Automated backup
solutions for data integrity. User Notifications:
Email and SMS gateways for alerts. Logging and
Auditing: Record and audit user and system
activities. Compliance and Maintenance:
Ensure compliance with financial regulations,
regular maintenance, and security 1.4
Definition, Acronyms and Abbreviations
SQL Server Structured query language intended
for database use.utilized to specify data storage
and retrieval protocol
User Authentication The process of verifying the
identity of a user attempting to access the system.
Encryption The process of converting data into a
code to prevent unauthorized access or data theft.
API (Application Programming Interface) A set of
rules and protocols for building and interacting
with software applications
KYC (Know Customer) Your A process that financial
institutions use to verify the identity of their
customers.
Compliance Adherence standards. to legal and
regulatory requireme.
Credit card In order to complete your purchases
and payments, utilize credit cards. Each of these
cards is issued by various banks, ensuring that the
cardholder possesses an account and balance
within the respective bank.
SRS A document that completely describes all of
the functions of a proposed system and the
constraints under which it must operate. For
example, this document.
Cloud Computing The delivery of computing
services, including servers, storage, and
databases, over the internet.
Stake Holders Any individual who possesses an
inclination towards the project and does not
engage in development work.
Scalability The ability of a system to handle
increased loads and demand by adding resources
or expanding infrastructure.
2) Overall Description
2.1 Product Perspective:
 The Banking Management System (BMS) is a
sophisticated software solution developed to
revolutionize and optimize the operations of a
modern banking institution. It stands as an
integral part of the bank's technology
infrastructure, serving as the central hub for
various banking activities. BMS is designed to
replace or integrate with existing legacy
systems, offering a more efficient and user-
friendly banking experience while ensuring
compliance with industry regulations.
2.2 User Classes and Characteristics :
BMS caters to a diverse range of users with
varying roles and responsibilities, including:
• Bank Staff: This class includes tellers, loan
officers, customer service representatives, branch
managers, and executives. They need different
levels of system access to perform tasks related to
customer accounts, transactions, approvals, and
auditing. Each staff member has specific roles
within the system, such as account creation,
transaction processing, loan origination, and
account management.
• Customers: The bank's clients represent a vital
user class. They require access to their accounts,
transaction history, and the ability to make
transactions online, such as deposits, withdrawals,
transfers, and bill payments. Customers must have
secure and easy-to-use interfaces for their
banking needs.
• Administrators: Administrators oversee the
system's configuration and maintenance. They
manage user access levels, security protocols,
system updates, and ensure overall system health.
Their responsibilities include system setup,
troubleshooting, and managing software updates.
• Auditors: Auditors represent another crucial
user class. They review and monitor financial
transactions for compliance and security, ensuring
that the bank operates within legal and regulatory
frameworks. Auditors have access to advanced
auditing tools and reports.
 2.3 Operating Environment:
The Banking Management System is designed
to operate efficiently within a Windows-based
environment, ensuring compatibility with a
wide range of Windows operating systems,
including Windows 7 and subsequent
versions. The system can be run on standard
desktop computers or servers, depending on
the bank's requirements. It is expected to be
hosted on a dedicated server within the
bank's premises and accessed through a
secure network to maintain the highest level
of data security.
2.4 Software Interface:
The BMS interfaces with several key software
components to deliver its functionality,
including:
• Database Management System: BMS connects
to a robust and secure database management
system, such as Oracle, MySQL, or SQL Server, to
store and retrieve customer data, transaction
records, and system logs. This integration ensures
data integrity, reliability, and accessibility.
• Web Services: To facilitate online banking,
BMS interfaces with web services for customer
account access and transaction processing. This
includes features like online account
management, fund transfers, and account
statements. Web services allow customers to
interact with the bank 24/7 from various devices,
including web browsers and mobile applications.
• Payment Gateways: The system integrates
with payment gateways to enable electronic fund
transfers, online payment processing, and
integration with external financial networks like
SWIFT and ACH.
• Third-Party APIs: BMS can incorporate
thirdparty APIs for services such as credit scoring,
identity verification, and payment processing,
enhancing its capabilities and extending the range
of services provided to customers
 2.5 Hardware Requirements:
The Banking Management System requires
specific hardware resources to operate
effectively. The following hardware
requirements should be met for optimal
system performance:
• CPU: An Intel Core i5 or equivalent processor
is recommended to handle the system's
computational demands efficiently.
• RAM: A minimum of 8 GB of RAM is necessary
to ensure smooth operation when handling
multiple users and large datasets.
• Storage: The system should be equipped with
a minimum of 500 GB of SSD storage, ensuring
fast data retrieval and ample space for logs and
backups.
• Network: A high-speed and stable internet
connection is essential for seamless access to
web-based components, secure data transfers,
and communication with external financial
networks.
• Security: Robust security measures, including
firewall protection and antivirus software, should
be in place to safeguard the system from potential
threats, ensuring data integrity
2.6 Functionalities:
The Banking Management System provides a wide
array of functionalities to meet the dynamic needs
of the banking industry. Key functionalities
include:
• Customer Account Management: BMS
enables bank staff to create, modify, and close
customer accounts with comprehensive customer
profiles that include personal information,
identification documents, and account
preferences.
• Transaction Processing: The system supports
various types of transactions, including deposits,
withdrawals, transfers, bill payments, and check
clearances. Real-time transaction tracking and
confirmation features enhance customer and staff
experience.
• Loan Management: BMS facilitates the
origination, approval, and tracking of loans. This
includes comprehensive loan application
processing, risk assessment, and loan
documentation.
• Online Banking: The system provides
customers with 24/7 access to their accounts
through secure online banking interfaces. This
includes account balances, transaction history,
electronic fund transfers, and bill payments.
Customers can also apply for loans and set up
automated transfers.
• Reporting and Auditing: BMS generates a wide
variety of reports for bank staff and auditors,
offering insights into customer account activities,
financial transactions, and system performance. It
also supports auditing and compliance reporting
to meet regulatory requirements.
• Security: The system implements robust
security measures, including user authentication,
encryption of sensitive data, and access control to
safeguard customer information and financial
data.
• Notifications: BMS sends notifications to
customers for transaction alerts, account updates,
and promotional messages through various
communication channels, including email and
SMS.
• Customer Support: The system integrates a
customer support portal, allowing customers to
submit inquiries, raise issues, and track their
resolution status. Bank staff can access customer
support tickets and prioritize service requests.
2.7 General Constraints:
Several general constraints should be considered
during the development and operation of the
Banking Management System:
• Data Privacy Regulations: BMS must comply
with data privacy laws and regulations, such as
GDPR, HIPAA, and local banking regulations. It
should include features for data encryption,
consent management, and secure data storage. •
Legacy System Integration: The migration from
existing legacy systems to the BMS may pose
challenges. Careful data transfer, staff training,
and comprehensive testing are essential to ensure
a smooth transition without disrupting banking
operations.
• Security Concerns: The system must be
designed with robust security mechanisms to
protect against data breaches and cyberattacks.
Continuous monitoring and updating of security
measures are crucial, given the sensitive nature of
customer information and financial data.
• Scalability: BMS should be designed to
accommodate future growth in terms of
customers and transactions. The system's
architecture and infrastructure should be scalable,
allowing for easy expansion and system
enhancements.
• User Training: Adequate training must be
provided to bank staff and customers to ensure
the effective use of the system. A wellstructured
training program should be in place to familiarize
users with the software's features and
functionalities.
3) System feature :
3.1 Functional Requirements
A. User Authentication and Authorization :
• The BMS allows new users to register and
create accounts.
• Login: Users should be able to login using
username and password.
• Roles: Different user roles should have
different privileges.
B. Account Management :
• The BMS allows customers to open all types of
accounts like savings, fixed deposit, etc.
• Account holders will be able to view their
transaction history and their available balance. •
They will be able to transfer funds between their
own accounts or to others accounts. C. Loan
Management :
• Customers should be able to apply for loans
and view their loan status
. • The system should calculate loan interest rates
and provide repayment schedules.
• Loan officers should be able to review and
approve loan application. D. Customer Support :
• Users should be able to contact customer
support through the system, including email or
chat.
• Customer support agents should have access
to customer data to provide assistance. E. Account
Statements and Reports :

• Account holders should be able to generate

and download account statements.
• Managers should have access to various
reports, such as daily transaction summaries,
account balances, and audit logs. F. Online Bill
Payment :
• Customers should be able to pay bills online,
such as utility bills, credit card bills, and loan
payments.
• The system should securely process these
payments and provide payment confirmation. G.
Online Banking for Mobile Devices :
• The system should be accessible via web
browsers and mobile applications.
• It should provide a user-friendly interface for
mobile users.
H. Automatic Alerts for Unusual Activities :
• The system should automatically detect and
alert users to unusual or suspicious account
activities, such as large transactions from new
locations.
3.2 Technical Issues :
• Database: The Banking Management system
will use the MySQL Database, which is open
source and free to use.
• Operating System: The Development
environment can be Windows 10.
3.3 Non Functional Requirements A.
Security :
• The system should implement robust security
measures to protect against unauthorized access,
data breaches, and fraud.
• It should use encryption for data transmission
and storage.
• Access control should be granular, and data
should be protected against SQL injection and
other common vulnerabilities. B. Performance :
• The system should provide fast response
times for common operations (e.g., account
balance inquiries, funds transfers).
• It should be able to handle a high number of
concurrent users and transactions during peak
times.
• Response times should remain within
acceptable limits even during periods of heavy
usage.
C. Scalability :
• The system should be scalable to
accommodate an increasing number of users,
accounts, and transactions.
• It should allow for the addition of new servers
or resources as the system grows. D. Reliability :
• The system should have a high level of
availability, with minimal downtime for
maintenance or upgrades.
• It should have a mechanism to ensure
uninterrupted service in case of hardware or
software failures. E. Recovery and Backup :
• The system should have a robust data backup
and recovery strategy to prevent data loss in case
of system failures.
• Regular backups should be performed and
tested for reliability.
• A disaster recovery plan should be in place to
restore service quickly in the event of a
catastrophic failure. F. Compliance :
• The system should adhere to relevant banking
and financial industry regulations, including Know
Your Customer (KYC) and
Anti-Money Laundering (AML) requirements.
• It should comply with data protection and
privacy laws, such as GDPR or HIPAA, as
applicable.
G. Usability :
• The user interface should be intuitive and
user-friendly, catering to users of varying technical
abilities.
• The system should be accessible to individuals
with disabilities and comply with accessibility
standards (e.g., WCAG). H. Load Testing and
Performance Monitoring :
• The system should be subject to load testing
to ensure it can handle expected levels of usage.
• Continuous performance monitoring should
be in place to detect and address performance
bottlenecks. 4) Design
4.1 Decision tree

This Photo by Unknown Author is licensed under CC BY-SA-NC

4.2 Use Case Diagrams

This Photo by Unknown Author is licensed under CC BY

4.3 Class Diagrams

 This Photo by Unknown Author is licensed under CC BY-SA

4.4 State Chart

 This Photo by Unknown Author is licensed under CC BY-NC

4.5 DFD 0 AND DFD 1

 This Photo by Unknown Author is licensed under CC BY-SA

5) DATABASE DESIGN
5.1 Entity-Relationship Diagram (ERD)
Entity-Relationship Diagram Overview:
This Photo by Unknown Author is licensed under CC BY-SA-NC

The ERD illustrates the primary entities, attributes,

and relationships in the Banking Management
System: 1. Entities:
a. Customer - CustomerID (Primary Key)
- First Name
- Middle Name
- Last Name
- Date of Birth
- Gender
- Email
- Contact
- Permanent Account Number (PAN)
- Nationality
- Salary
- Gender
– Address
b. Account
- Account No (Primary Key)
- CustomerID (Foreign Key)
- Account Type (e.g., Savings, Checking)
- Balance
- Interest Rate
- Date Created
- Interest ID
- Interest Amoun c. Transaction
- TransactionID (Primary Key)
- Account No (Foreign Key)
- Transaction Type (e.g., Deposit, Withdrawal,
Transfer)
- Amount
- Transaction Date and Time
- Total Balance
d. Deposit Account - Deposit Account No
(Primary Key) - Account No
- Closure type
- Interest ID
- Initial Amount
- CustomerID
- Deposit Account Type
- Interested Amount
- Current Balance
- Duration
- Interest Rate
- Open Date
- Close Date
- Day
e. Officer - EmployerID (Primary Key)
- Username
- Password
- Email
- Nationality
- Salary
- Address
- Gender
- Contact
- Date of Birth
- First Name
- Middle Name
- Last N
f. Manager
- EmployerID (Primary Key)
- Username
- Password
- Email
- Nationality
- Salary
- Address
- Gender
- Contact
- Date of Birth
- First Name
- Middle Name - Last name g. Interest
- InterestID (Primary Key)
- Savings Interest
- Loan Interest
- RD Interest
- FD Interest
- Current Int
h. Loan Account
- Account No (Primary Key)
- Loan ID
- Loan Type
- Date of Loan
- Duration
- Total Amount
- Remaining Amount
- Status
- Description
- Interest
6) Future Scope :
The future scope of a Banking Management
System includes:
1. Digital Transformation: Banks will continue to
invest in digital technologies to improve customer
experiences, streamline operations, and enhance
security.
2. Artificial Intelligence: AI will play a crucial role
in customer service, fraud detection, and data
analysis for personalized financial solutions.
3. Blockchain: Blockchain technology can
enhance security, transparency, and efficiency in
various banking processes, including crossborder
payments and identity verification.
4. Open Banking: Open banking regulations will
promote collaboration between banks and fintech
companies, offering customers more choices and
personalized financial services.
5. Cybersecurity: With the increasing digitization
of banking, cybersecurity will remain a top priority
to protect customer data and financial assets.
6. Mobile Banking: Mobile apps will continue to
evolve, providing more features for managing
accounts, making transactions, and accessing
financial advice.
7. Personal Finance Management: Banking
systems may integrate advanced tools to help
customers manage their finances, make informed
decisions, and save money.
8. Regulatory Compliance: Banks will need to
adapt to evolving regulatory requirements, such
as data privacy and anti-money laundering
regulations.

9. Sustainability and ESG: Banks will focus on

environmental, social, and governance (ESG)
criteria in their operations and investment
decisions.
10. Financial Inclusion: Banking systems will work
towards greater financial inclusion, extending
services to under-served populations and remote
areas.
11. Data Analytics: Advanced data analytics will
enable banks to gain insights into customer
behavior and preferences, allowing for more
targeted services.
These trends represent the evolving landscape of
banking management systems, driven by
technological advancements, regulatory changes,
and shifting customer demands
 Conclusion
The System Requirements Specification (SRS) for a
Banking Management System is a critical
document that outlines the functional and
nonfunctional requirements of the software
system. This document serves as a foundation for
the design, development, and testing phases of
the project, ensuring that the final system meets
the needs and expectations of both the bank and
its customers. In this conclusion, we will highlight
the key takeaways and emphasize the importance
of a welldefined SRS for such a complex and
sensitive domain. First and foremost, the SRS for a
Banking Management System has been designed
with a strong emphasis on security and data
integrity. The confidentiality, availability, and
integrity of customer data are of paramount
importance in the banking industry. This
document provides a detailed outline of the
security measures, user access controls, and
encryption standards that will be implemented to
safeguard sensitive information. By doing so, it
ensures that customer trust is maintained and
regulatory compliance is upheld. Another crucial
aspect of the SRS is its comprehensive coverage of
the system's functionality. It defines the various
features and modules that the Banking
Management System will offer, including customer
account management, transaction processing,
loan management, reporting, and administrative
tools. This level of detail enables developers to
understand the full scope of the project and
minimizes misunderstandings or
misinterpretations during the development
process. In conclusion, the System Requirements
Specification for a Banking Management System is
an indispensable document that lays the
foundation for the successful development and
deployment of a sophisticated and secure banking
software solution. It encompasses the critical
aspects of functionality, security, performance,
and user experience, all of which are essential in
the banking industry. A well-defined SRS reduces
ambiguity, minimizes risks, and serves as a
roadmap for developers and stakeholders
 References
1. Academic Journals : Research articles in
finance and information technology journals often
discuss banking management systems and their
evolution.
2. Books : Books on banking technology and
management, particularly those written by
experts in the field. Some books which deserve
special mention are :
A) A Philosophy of Software Design
B) Fundamental of Software Engineering
C) Software Engineering elements
D) Mohapatra, H., & Rath, A. K. (2020).
Fundamentals of software engineering:
designed to provide an insight into the software
engineering concepts. BPB Publications. 3. Online
Databases : Online databases like PubMed, Google
Scholar, or databases specific to the finance and
technology sectors can be valuable resources for
academic papers and report.
 Bibliography

Banks and Banking Bibliography”

This compilation, provided by James R. Martin,
Ph.D., CMA, covers various topics related to
banking. While this source doesn’t provide an
extensive bibliography, it’s worth mentioning. The
book provides an introduction to banking
concepts and practices, which could be helpful for
anyone diving into the field. The Art of Cloaking
Ownership: The Secret Collaboration and
Protection of the German War Industry by the
Neutrals: The Case of Sweden. Although not
directly related to management systems, this book
sheds light on the role of banks during wartime. It
explores how neutral countries like Sweden were
involved in protecting the German war industry.
An interesting historical perspective.