Bank Management System Report

BANK MANAGEMENT SYSTEM

SUMMER INTERNSHIP-II REPORT

Submitted by

BHATT NISHANT H.(236490316023)

SOLANKI DARSHAN S.(236490316202)

TRIVEDI OM G.(236490316214)
In partial fulfilment for the award of the degree

of

DIPLOMA ENGINEERING

in
INFORMATION TECHNOLOGY

Guided by

Mr. Ravi Makwana

Sir Bhavsinhji Polytechnic Institute Bhavnagar

Gujarat Technological University, Ahmedabad

October-2025

1|Page
Bank Management System Report
GUJARAT TECHNOLOGICAL UNIVERSITY AHMEDABAD
SIR BHAVSINHJI POLYTECHNIC INSTITUTE
BHAVNAGAR

Certificate

This is to certify that Mr. Bhatt Nishant H. from Sir Bhavsinhji Polytechnic
Institute, Bhavnagar College having Enrollment No:236490316023 has
completed Summer Internship-II Mini-Project having title Bank
Management, in a group consisting of 3 persons under the guidance of the faculty
guide Mr. Ravi Makwana.

Institute Guide Head of Department

2|Page
Bank Management System Report
GUJARAT TECHNOLOGICAL UNIVERSITY AHMEDABAD
SIR BHAVSINHJI POLYTECHNIC INSTITUTE
BHAVNAGAR

Certificate

This is to certify that Mr. Solanki Darshan S. from Sir Bhavsinhji Polytechnic
Institute, Bhavnagar College having Enrollment No:236490316202 has
completed Summer Internship-II Mini-Project having title Bank
Management, in a group consisting of 3 persons under the guidance of the faculty
guide Mr. Ravi Makwana.

Institute Guide Head of Department

3|Page
Bank Management System Report
GUJARAT TECHNOLOGICAL UNIVERSITY AHMEDABAD
SIR BHAVSINHJI POLYTECHNIC INSTITUTE
BHAVNAGAR

Certificate

This is to certify that Mr. Trivedi Om G. from Sir Bhavsinhji Polytechnic

Institute, Bhavnagar College having Enrollment No:236490316214 has
completed Summer Internship-II Mini-Project having title Bank
Management, in a group consisting of 3 persons under the guidance of the faculty
guide Mr. Ravi Makwana.

Institute Guide Head of Department

4|Page
Bank Management System Report

Acknowledgement

We,
Bhatt Nishant H. (236490316023)
Solanki Darshan S. (236490316202)
Trivedi Om G. (236490316214)

want to express our deep gratitude to our supervisor, Mr. Ravi Makwana, for his
guidance, patience, and support. We feel incredibly lucky to have had the
chance to work with such an encouraging professor.
Our sincere thanks go to Mr. H.P. Jagad and the Head of Department, Mr. G.M.
Pandey, for their constant support.
We're thankful to everyone at Sir BPTI, Bhavnagar, for their encouragement,
and we especially appreciate Principal Prof. H. K. Bhatt for giving us the
opportunity to undertake and represent our project work.
Together, with the help of these wonderful individuals, we've been able to
succeed in our project. Their guidance and support have been invaluable, and
we truly appreciate their contributions to our journey.

5|Page
Bank Management System Report
Abstract
Bank Management System:
Managing banking operations such as accounts, loans, savings, and customer support can be
complex and time-consuming for both banks and customers. Traditional systems often lack
convenience, security, and accessibility in a single platform.

Our Bank Management System Android application is designed to provide a secure, scalable,
and user-friendly solution for modern banking needs. Customers can easily perform essential
operations like viewing balances, transferring funds, applying for accounts, and managing
fixed deposits directly from their smartphones. At the same time, administrators can
efficiently manage accounts, loans, investments, and customer queries through dedicated
modules.

Features of the Bank Management System application:

• Customer account operations: view balance, fund transfer, update details, generate
statements

Loan management:

• eligibility checks, approvals/rejections, EMI handling

Savings & investments:
• fixed deposit management, auto-saving, profit/interest reports

Admin functions:
• account creation, modification, blocking/unblocking, and reviewing requests
• Integrated customer support with chatbot and admin response system

Benefits of using our application:

• Secure and convenient mobile banking access
• Simplified account, loan, and investment management
• Faster customer support through integrated chat system
• Transparency with detailed reports and statements

How the application helps customers and banks:

For customers, the app eliminates the need for frequent branch visits, enabling banking
anytime and anywhere. For banks, it streamlines operations, improves decision-making with
automated reports, and enhances customer satisfaction through efficient service delivery.

6|Page
Bank Management System Report

List of Tables

Sr no. Description Page no.

1 Users Table 30

2 Accounts Table 31

3 Loans Table 32

4 FixedDeposits Table 33

5 SupportTickets Table 34

6 TicketMessages Table 35

7 Transactions Table 36

7|Page
Bank Management System Report

List of Figures

Sr no. Description Page no.

1 Time Line Chart 19

2 System Architecture 23

3 DFD Level 0 24

4 DFD Level 1(Admin) 25

5 DFD Level 1(Client) 25

6 DFD Level 2.1 26

7 DFD Level 2.2 27

8 DFD Level 2.3 28

9 Use Case Diagram 29

10 Activity Diagram 30

8|Page
Bank Management System Report

List of Symbol

Sr No Symbol Description
1 A stage of process

2 Task of stage

3 Milestone (Showing
completion of a
Stage)

Sr No Symbol Description
1 0.0 Process

2 Entity

3 Data Flow

4 Data Store

Sr No Symbol Description
1 A stage of process

2 Task of stage

3 Milestone (Showing
completion of a
Stage)

9|Page
Bank Management System Report

Sr No Symbol Description
1 Start

2 Stop

3 Actions

4 Decisions

5 Fork

6 Decision Flow

Sr No Symbol Description
1 Entity

2 Attribute

3 Relationship

4 One
Cardinality
5 Many
Cardinality

10 | P a g e
 Bank Management System Report
INDEX
Sr no. Page no.
Topic Name
1 Introduction 14
i. Project Introduction / Profile + Company Profile 14

ii. Purpose 14

iii. Scope 15

2 16
System Requirement Analysis
i. Current System Study 17

ii. Weakness of Current System 18

iii. Problem Identification / Definition 18

iv. Requirement of New System 19

v. Feasibility Study 20

a. Technical 20

[Link] 20

c. Operational 21

[Link] (Time Line Chart) 21

vi. Development model used (Software Process Model) 22

vii. Requirement Validation 23

viii. Tools and Technology / Minimum Hardware and Software Requirements 24

ix. System Architecture 25

x. Data Flow Diagram 26

xi. Use –case Diagram 31

xii. Activity Diagram 32

3 System Design

i. Database Design 34

a. Data Dictionary 34

[Link]-Relationship Diagram 41
ii. GUI Design 50
References 50
Apendix(PPT)
11 | P a g e
Bank Management System Report

1
…
Chapter # 1: Introduction

1.1 Project Introduction / Profile

1.2 Purpose
1.3 Scope
12 | P a g e

.
Bank Management System Report

1.1 Project Introduction

We are proud to introduce the "Bank Management System," a modern Android-based
application designed to provide customers and administrators with a secure, efficient, and
intuitive platform for managing essential banking operations.

This comprehensive mobile solution is tailored to meet the growing demand for digital
banking services, combining core functionalities such as account management, transactions,
loan processing, and fixed deposit handling within a single, user-friendly interface.

By leveraging the robustness of Java and PostgreSQL, the system ensures reliability,
scalability, and security, aligning with contemporary standards in financial technology.

1.2 Purpose
The "Bank Management System" application serves as a vital tool for customers and
administrators to carry out a wide range of banking operations with security, speed, and
convenience. It is designed to streamline traditional banking processes by providing digital
access to essential services, thereby reducing manual work, improving efficiency, and
enhancing user satisfaction.

• Core Banking Features:

Our application offers comprehensive functionality for account management, fund
transfers, fixed deposits, loan processing, and transaction tracking. These features
empower customers to manage their finances independently while ensuring
transparency and control over every activity.
• Admin Oversight:
Administrators are equipped with tools for account approval, loan management,
customer requests, and support handling. This ensures that banking operations are
monitored and regulated effectively, maintaining trust and security.
• User-Friendly Interface:
The application provides a modern and intuitive interface, designed to be accessible to
users of different technical backgrounds. From simple balance inquiries to complex
loan approvals, the interface ensures smooth navigation and usability.

The Bank Management System is positioned to redefine everyday banking by integrating

advanced digital tools with traditional financial services. By bridging the gap between
customers and administrators, the application delivers a secure, reliable, and scalable solution
that meets the needs of modern banking.

13 | P a g e
Bank Management System Report

1.3 Scope
• User-Friendly Interface: The application features a clean and intuitive interface,
enabling both customers and administrators to easily perform banking operations
regardless of their technical background.
• Comprehensive Banking Services: Digital management of accounts, transactions,
loans, fixed deposits, and customer requests, ensuring all essential banking functions
are available in one platform.
• Security: Emphasis on secure handling of sensitive data such as account details, PINs,
and transactions, reducing risks of unauthorized access or fraud.
• Convenience: By digitizing core banking processes like fund transfers, loan
applications, and account updates, the application saves time and minimizes the need
for physical branch visits.
• Accessibility: The system is designed for wide accessibility, catering to individual
customers, salaried users, business account holders, and bank administrators.
• Efficiency: Streamlines traditionally manual banking tasks, automating processes
such as EMI calculation, fixed deposit maturity, and transaction recording for
improved efficiency.
• Transparency: Customers can view transaction histories, loan statuses, and account
information in real time, ensuring accountability and informed decision-making.

14 | P a g e
Bank Management System Report

2
2
Chapter # 2: System Requirement Analysis

2.1 Current System Study

2.2 Weakness of Current System

1
2.3 Problem Identification / Definition
2.4 Requirement of New System
2.5 Feasibility study a) Technical b) Economical c)
Operational d) Schedule (Time Line Chart) 2.6

1
Development Model (Software Process Model)
2.7 Requirement Validation
2.8 Tools and Technology / Minimum Hardware and
Software Requirements

1
2.9 System Architecture
2.10 Data Flow Diagram
2.11 Use-Case Diagram
2.12 Activity Diagram
15 | P a g e

1
Bank Management System Report

2.1 Current System Study

In the current scenario of banking operations, both customers and banks primarily rely on
multiple traditional and fragmented methods to manage financial activities:

1. Customers often need to visit bank branches physically to open accounts, apply for
loans, manage fixed deposits, and perform fund transfers. This involves waiting in
queues and handling paperwork, which consumes considerable time and effort.
2. Manual Record-Keeping and Processing:
Many banking processes such as loan approvals, EMI tracking, and account
management are still managed through manual record-keeping, relying heavily on
bank staff. This can lead to delayed approvals, processing errors, and inefficient
workflows.
3. Limited Digital Access:
Some banking services are available online through web portals or basic mobile apps,
but they often provide limited functionalities. Customers may need separate apps or
systems for account management, loan applications, and customer support, which
reduces convenience.
4. Customer Support Challenges:
Customer support is generally handled through call centers or branch visits, which can
result in long wait times and inadequate tracking of queries or complaints. There may
be minimal real-time assistance or integrated chatbot systems for immediate help.
Currently, banking operations lack a unified, user-friendly mobile platform that integrates
comprehensive services such as account management, loan processing, savings and
investment tracking, and customer support. This results in inefficiencies for customers
seeking convenient access and for banks needing streamlined management.

16 | P a g e
Bank Management System Report

2.2 Weakness of Current System

Here are the five most significant limitations of the current banking systems and processes,
which the Bank Management System application aims to address:

1. Limited Accessibility and Convenience:

Customers often rely on physical branch visits for most banking operations, which is
time-consuming and inconvenient, especially for routine tasks like balance checks or
fund transfers.
2. Fragmented Services:
Banking functions such as account management, loans, fixed deposits, and customer
support are usually handled through separate platforms or manual processes, lacking
integration and seamless user experience.
3. Delayed Processing and Approvals:
Manual handling of loan applications, EMI tracking, and account requests often
results in slow response times, inefficient workflows, and increased chances of errors.
4. Lack of Real-Time Support:
Customer support is generally accessible via call centers or branches with limited
real-time assistance, leading to long wait times and insufficient query resolution
tracking.
5. Security Concerns and Transparency Issues:
Traditional systems may have vulnerabilities due to manual processes and
decentralized data management, resulting in potential data privacy risks and limited
transparency in transactions and account status updates.

2.3 Problem Identification / Definition

Limited accessibility to integrated and real-time banking services, fragmented platforms,
and delayed manual processing hinder customers and banks in efficiently managing
financial operations. Customers face inconvenience and lack transparency, while banks
struggle with inefficient workflows and slower decision-making. The Bank Management
System application aims to streamline and enhance banking operations by providing a
secure, consolidated, and user-friendly digital platform.

17 | P a g e
Bank Management System Report

2.4 Requirement of New System

Functional Requirements

• The system must allow customers to create, view, and manage bank accounts
securely.
• The system must support fund transfers within the bank and to other banks via NEFT,
UPI, and RTGS.
• The system must enable customers to apply for loans and track loan statuses with EMI
schedules.
• The system must support fixed deposit account creation, management, interest
calculation, and maturity tracking.
• The system must allow administrators to approve or reject account requests, loan
applications, and other customer requests.
• The system must provide real-time notifications and alerts to customers about
transactions, EMIs, and account activities.
• The system must facilitate customer support through chatbots and admin response
modules.
• The system must generate statements, detailed reports, and summaries for customers
and administrators.
• The system must enable secure login and role-based access control for admin and
customers.
Non-Functional Requirements

• The system must ensure high availability and reliability, accessible 24/7 on mobile
devices.
• The system must provide strong security measures, including encrypted data
transmission, safe authentication, and privacy protection.
• The system must have an intuitive and user-friendly interface for customers and
administrators with smooth navigation.
• The system must be scalable to handle a growing number of users and transactions
efficiently.
• The system must maintain data integrity and consistency through all operations.
• The system must support cross-platform compatibility on Android devices with
different screen sizes.
• The system must handle errors gracefully, providing meaningful user feedback and
logging for administrators.

18 | P a g e
Bank Management System Report

2.5 Feasibility Study

The feasibility study evaluates whether the Bank Management System project is practicable
from technical, economic, and operational perspectives, ensuring that it can be successfully
developed, deployed, and sustained.

a) Technical Feasibility

Technical feasibility addresses the hardware and software technology requirements for the
development and deployment of the Bank Management System application. This project is
designed as an Android mobile application with backend server support.

Key technical components include:

• Programming Language: Java for Android application development.

• Database Management: PostgreSQL or MySQL for secure, scalable backend
storage.
• Development Tools: Android Studio as IDE, Postman for API testing, Git for version
control.
• Cloud Services: Firebase for notifications and cloud services integration.
• Design Tools: UI/UX design tools for app interface development.
All these technologies and tools are widely available, reliable, and well-supported. Free and
open-source options reduce barriers to development. This confirms the project is technically
feasible, with no major technical constraints anticipated.

b) Economical Feasibility

Economical feasibility analyzes the cost-effectiveness of the Bank Management System

project, comparing expected costs against anticipated benefits.

Economic benefits and costs include:

• Cost Savings: Digital banking reduces the need for physical branch visits and manual
processing, lowering operational expenses for banks.
• Development Costs: Mainly involve software development, cloud service
subscriptions, and infrastructure, which can be managed with open-source and free
tools, minimizing initial investment.
• User Benefits: Customers gain convenient, anytime access to banking services; banks
improve customer satisfaction and operational efficiency.
• Market Reach: With growing smartphone penetration, a mobile banking application
has a large potential user base.

19 | P a g e
Bank Management System Report
Given these factors, the project is economically viable, promising good returns on investment
through cost reductions and improved service quality.

c) Operational Feasibility

Operational feasibility assesses how well the Bank Management System can be integrated
into existing banking operations and how easily users can adopt and use the system.

Operational considerations include:

• Ease of Use: The app will feature an intuitive interface suitable for users with varying
technical proficiency.
• Improved Workflow: Automation of routine tasks such as loan processing, EMI
tracking, and account management enhances operational efficiency.
• Customer Support: Integrated chatbot and admin response modules provide real-
time assistance, improving user experience.
• Adoption: Mobile-based access aligns with modern customer preferences, increasing
likelihood of widespread adoption.
The system is expected to significantly streamline banking tasks and improve service
delivery, making it operationally feasible.

d) Time Line Chart

20 | P a g e
Bank Management System Report

2.6 Development model

For the development of the Bank Management System, the Linear Sequential Model
(Waterfall Model) has been chosen due to its systematic and structured approach. The
Waterfall Model divides the software development life cycle into distinct, sequential phases,
with each phase dependent on the successful completion of the previous one. This ensures
clear documentation, easy management, and traceability of progress.

The main phases in this model for our project are:

• Requirements Gathering: Analyzing the current banking systems, identifying

weaknesses, and gathering detailed requirements to overcome those deficiencies.
• System Analysis: Assessing the feasibility—technical, economic, and operational—
of the proposed banking application to ensure viable development.
• Designing: Creating the system architecture and database design, alongside
developing the user interface (UI) designs, with tools like Figma for prototyping.
• Implementation: Coding the Android application frontend and backend services
using Java and PostgreSQL/MySQL.
• Testing: Conducting unit, integration, and system testing to ensure all features work
as intended without defects.
• Deployment and Maintenance: Deploying the application for use, followed by
ongoing maintenance and support to enhance performance and fix issues.
This model is ideal for the Bank Management System project as the requirements are clearly
defined and expected to remain stable during development. The Waterfall Model delivers a
disciplined approach, ensuring each phase receives focused attention before moving forward,
which promotes quality and reduces risks associated with undisciplined development.

However, flexibility for major requirement changes during development is limited. Hence,
thorough initial planning and requirement analysis are emphasized to minimize mid-
development changes.

21 | P a g e
Bank Management System Report

2.7 Requirement Validation

Requirement validation is the process of ensuring that the requirements defined for the Bank
Management System accurately represent the needs and expectations of the users and
stakeholders. Validating requirements early in development helps avoid costly rework and
ensures that the final system delivers intended functionalities.

Key validation techniques used for this project include:

• Validity Checks:
Each function and feature is verified to ensure it aligns with the system's goals and
user needs. This helps identify if any essential functions are missing or if extra
functionalities are needed to meet user expectations.
• Completeness Check:
The requirement documents are reviewed comprehensively to confirm that all
necessary requirements, constraints, and use cases have been included. This assures
that no critical functionality or system constraint is overlooked.
• Prototyping:
Early-stage UI/UX prototypes of the application are developed and shared with end
users and stakeholders. Their feedback is collected on usability, feature completeness,
and overall satisfaction. This iterative process helps refine requirements and aligns
them closely with user needs before full-scale development.
Through thorough validation, this project aims to minimize errors and ensure the Bank
Management System meets all functional and non-functional requirements satisfactorily.

22 | P a g e
Bank Management System Report

2.8 Tools and Technology / Minimum Hardware and Software

Requirements
Android Studio:

• Android Studio is the official Integrated Development Environment (IDE) for

Android application development.
• It supports Java, the primary programming language used for this project.
• Comes with built-in Android SDK and emulator for testing across different devices.
• Free to download and widely used in the industry for mobile app development.
PostgreSQL/MySQL:

• These are open-source relational database management systems used to store and
manage all backend data securely.
• They support complex queries, transactions, and data integrity required by banking
systems.
• Easy to install and maintain on common server hardware.
Firebase:

• Firebase provides cloud services for notifications, authentication, and real-time data
synchronization.
• It integrates seamlessly with Android apps and offers a free tier for development and
basic usage.
Git:

• Git is a version control system that manages source code changes and facilitates
collaboration.
• Essential for tracking revisions and managing project codebase efficiently.
Figma:

• Figma is a graphic design tool used to create UI/UX prototypes and wireframes.
• It offers both free and paid versions; the free version provides all necessary design
components for the project.
• Highly user-friendly and ideal for real-time design collaboration.
[Link]:

• [Link] is a free online diagramming tool used for creating system diagrams such as
Data Flow Diagrams (DFD), Entity-Relationship (ER) diagrams, and Use Case
diagrams.
• Provides a straightforward interface and is easily accessible via the web.
23 | P a g e
Bank Management System Report

Minimum Hardware Requirements:

• Development PC with at least Intel i5 processor, 8GB RAM, and 256GB SSD to run
Android Studio emulator and database server smoothly.
• Android device (smartphone/tablet) running Android 6.0 or higher for testing the app
on real hardware.
• Reliable internet connectivity for cloud services and version control operations.
Minimum Software Requirements:

• Windows 10 (64-bit) or macOS Mojave (or higher) operating system.

• Java Development Kit (JDK) 8 or above installed for Android development.
• Supported browser for accessing design and diagramming tools like Figma and
[Link].

2.9 System Architecture

24 | P a g e
Bank Management System Report

2.10 Data Flow Diagram

DFD Level 0

25 | P a g e
Bank Management System Report

DFD Level 1(Admin)

DFD Level 1(Client)

26 | P a g e
Bank Management System Report

DFD Level 2.1

27 | P a g e
Bank Management System Report

DFD Level 2.2

28 | P a g e
Bank Management System Report

DFD Level 2.3

29 | P a g e
Bank Management System Report
2.11 Use –case Diagram

30 | P a g e
Bank Management System Report
2.12 Activity Diagram

31 | P a g e
Bank Management System Report

3
Chapter # 3: System Design

3.1 Database Design

a. Data Dictionary
b. Entity-Relationship Diagram
3.2 GUI Design (Self Created GUI Screen
shot)

32 | P a g e
Bank Management System Report

3.1 Database Design

a. Data Dictionary
Users Table

Stores information for both customers and administrators.

Column Name Data Type Constraints / Notes

user_id INT Primary Key, Auto-Increment

full_name VARCHAR(100) Not Null

email VARCHAR(100) Not Null, Unique

phone_number VARCHAR(15) Not Null, Unique

address TEXT -

date_of_birth DATE -

password_hash VARCHAR(255) Not Null

role ENUM('Customer', 'Admin') Not Null, Default: 'Customer'

ENUM('Active', 'Inactive', Not Null, Default:

status
'PendingApproval') 'PendingApproval'

created_at TIMESTAMP Default: Current Timestamp

updated_at TIMESTAMP Updates on change

33 | P a g e
Bank Management System Report
Accounts Table

Holds individual bank accounts linked to a user.

Column Name Data Type Constraints / Notes

account_id INT Primary Key, Auto-Increment

user_id INT Not Null, Foreign Key to Users

account_number VARCHAR(20) Not Null, Unique

account_type ENUM('Savings', 'Current') Not Null

balance DECIMAL(15, 2) Not Null, Default: 0.00

status ENUM('Active', 'Frozen', 'Closed') Not Null, Default: 'Active'

created_at TIMESTAMP Default: Current Timestamp

Loans Table
34 | P a g e
Bank Management System Report
Manages the entire lifecycle of loan applications.

Column Name Data Type Constraints / Notes

Primary Key, Auto-

loan_id INT
Increment

Not Null, Foreign Key to

user_id INT
Users (Applicant)

Nullable, Foreign Key to

approved_by_admin_id INT
Users (Admin)

loan_type VARCHAR(50) Not Null

loan_amount DECIMAL(15, 2) Not Null

interest_rate DECIMAL(5, 2) Not Null

tenure_months INT Not Null

ENUM('Pending', 'Approved', Not Null, Default:

status
'Rejected', 'Active', 'Closed') 'Pending'

Default: Current
applied_at TIMESTAMP
Timestamp

decision_at TIMESTAMP Nullable

closed_at TIMESTAMP Nullable

35 | P a g e
Bank Management System Report

FixedDeposits Table

Stores all information related to Fixed Deposit investments.

Column Name Data Type Constraints / Notes

Primary Key, Auto-

fd_id INT
Increment

Not Null, Foreign Key

account_id INT
to Accounts

principal_amount DECIMAL(15, 2) Not Null

interest_rate DECIMAL(5, 2) Not Null

tenure_months INT Not Null

maturity_date DATE Not Null

maturity_amount DECIMAL(15, 2) Not Null

ENUM('Active', Not Null, Default:

status
'EarlyWithdrawalRequested', 'Closed') 'Active'

Default: Current
created_at TIMESTAMP
Timestamp

closed_at TIMESTAMP Nullable

36 | P a g e
Bank Management System Report

SupportTickets Table

Tracks customer support requests.

Column Name Data Type Constraints / Notes

Primary Key, Auto-

ticket_id INT
Increment

Not Null, Foreign Key to

user_id INT
Users (Customer)

Nullable, Foreign Key to

assigned_to_admin_id INT
Users (Admin)

subject VARCHAR(255) Not Null

ENUM('Open', 'InProgress',
status Not Null, Default: 'Open'
'Closed', 'Escalated')

priority ENUM('Low', 'Medium', 'High') Not Null, Default: 'Medium'

created_at TIMESTAMP Default: Current Timestamp

closed_at TIMESTAMP Nullable

37 | P a g e
Bank Management System Report

TicketMessages Table

Stores the chat history for each support ticket.

Column Name Data Type Constraints / Notes

message_id INT Primary Key, Auto-Increment

ticket_id INT Not Null, Foreign Key to SupportTickets

sender_id INT Not Null, Foreign Key to Users

message_body TEXT Not Null

sent_at TIMESTAMP Default: Current Timestamp

38 | P a g e
Bank Management System Report
Transactions Table

Logs every financial movement within the system.

Constra
Column
Data Type ints /
Name
Notes

Primar
y Key,
transaction
INT Auto-
_id
Increm
ent

Nullabl
e,
Foreig
from_accou
INT n Key
nt_id
to
Accoun
ts

Nullabl
e,
Foreig
to_account
INT n Key
_id
to
Accoun
ts

Not
amount DECIMAL(15, 2)
Null

transaction ENUM('D‘POSIT',’'W‘THDRAWAL',’'T‘ANSFER',’'L‘AN_DIS Not

_type BURSAL',’'F‘_INTEREST', 'FEE') Null

Nullabl
description VARCHAR(255)
e

Default
Current
timestamp TIMESTAMP
Timest
amp

39 | P a g e
Bank Management System Report

b. Entity Relational Diagram

40 | P a g e
 Bank Management System Report

3.3 GUI Design

A)Login
B)Reset Password

C)Account Type Selection D) Registertion

41 | P a g e
 Bank Management System Report

F)Apply for Loans

E)Fund Transfer

H)Notification center
G)Loan Management

42 | P a g e
Bank Management System Report

I)Beneficiary Management J)Profile & Settings

L)Admin Dashboard
K)Service & Support

43 | P a g e
Bank Management System Report

M)Info Request N)Stop payment

P)Report & Analytics

O)Open request

44 | P a g e
Bank Management System Report

R)Saving Account
Q)Fund Transfer

T)Current Account
S)Services

45 | P a g e
Bank Management System Report

U)Accounts V)Loans & FD

X)Loan Dashboard
W)Dashboard

46 | P a g e
Bank Management System Report

Y)Support Tickets
Z)FD Management

Aa)New FD
Ab)FD Management

47 | P a g e
Bank Management System Report

Ac)Savings

48 | P a g e
Bank Management System Report

Reference

• Perplexity
• GeeksForGreeks
• Scribd
• Gemini
Appendix
PPT

49 | P a g e
Bank Management System Report

50 | P a g e
Bank Management System Report

51 | P a g e
Bank Management System Report

52 | P a g e
Bank Management System Report

53 | P a g e
Bank Management System Report

54 | P a g e
Bank Management System Report

55 | P a g e
Bank Management System Report

56 | P a g e