Table of Contents

1. Introduction ....................................................................................................................
1
1.1 Purpose .................................................................................................................. 1
1.2 Scope ..................................................................................................................... 1
1.3 Definitions, Acronyms, and Abbreviations .................................................... 1
1.4 References ............................................................................................................. 1
1.5 Overview ............................................................................................................... 1
2. Overall Description .................................................................................................... 2
2.1 Product Perspective .............................................................................................. 2
2.2 Product Functions ................................................................................................. 2
2.3 User Characteristics ............................................................................................ 2
2.4 Constraints ........................................................................................................... 2
2.5 Assumptions and Dependencies .................................................................. 2
2.6 Apportioning of Requirements ...................................................................... 3
3. Specific Requirements .............................................................................................. 3
3.1 External Interface Requirements .................................................................. 3
3.1.1 System Interfaces ........................................................................................ 3
3.1.2 User Interfaces ............................................................................................... 3
3.1.3 Hardware Interfaces ..................................................................................... 3
3.1.4 Software Interfaces ....................................................................................... 3
3.1.5 Communication Interfaces ....................................................................... 4
3.2 Functional Requirements ................................................................................. 4
3.3 Performance Requirements ............................................................................. 5
3.4 Logical Structure of the Data .......................................................................... 5
3.5 Design Constraints ............................................................................................ 6
3.6 Software System Attributes .............................................................................. 6
3.6.1 Reliability ....................................................................................................... 6
3.6.2 Availability ..................................................................................................... 6
3.6.3 Security ........................................................................................................... 6
3.6.4 Maintainability .............................................................................................. 6
3.6.5 Portability ...................................................................................................... 7
4. System Architecture .................................................................................................... 7
4.1 Overview ............................................................................................................ 7
4.2 Key Components ................................................................................................ 8
4.3 Data Flow Diagrams .......................................................................................... 9
5. Use Cases ................................................................................................................... 9
5.1 Use Case 1: User Registration ....................................................................... 9
5.2 Use Case 2: Account Login .............................................................................. 9
5.3 Use Case 3: Deposit Funds ............................................................................ 10
5.4 Use Case 4: Withdraw Funds ......................................................................... 10
6. Non-Functional Requirements ............................................................................... 11
6.1 Usability ............................................................................................................ 11
6.2 Scalability .......................................................................................................... 11
6.3 Accessibility ..................................................................................................... 11
6.4 Legal and Regulatory Compliance ................................................................ 11
7. System Testing Requirements ............................................................................... 12
7.1 Unit Testing ...................................................................................................... 12
7.2 Integration Testing ......................................................................................... 12
 7.3 System Testing ................................................................................................. 13
7.4 User Acceptance Testing ............................................................................... 13
8. Glossary .................................................................................................................... 14
9. Analysis Models ....................................................................................................... 15
10. To Be Determined List ............................................................................................ 16

1. Introduction

1.1 Purpose
This Software Requirements Specification (SRS) document describes the functionality and
requirements of the Bank Management System (BMS). The goal of this document is to define
the system’s specifications clearly, ensuring that the development team understands the
required features, constraints, and performance metrics. This will provide a comprehensive
understanding of the system to both the developers and the stakeholders.

1.2 Scope
The Bank Management System is a comprehensive software solution designed to automate
various banking operations. It will provide an interface for both customers and bank staff to
carry out essential banking tasks such as account management, deposits, withdrawals, balance
inquiries, and more. The system will use Java for the front-end application and MySQL for
database management, making it robust, secure, and scalable.

1.3 Definitions, Acronyms, and Abbreviations

 BMS: Bank Management System

 GUI: Graphical User Interface
 DBMS: Database Management System
 JRE: Java Runtime Environment

1.4 References

 Java Swing API Documentation

 MySQL Documentation
 ISO/IEC 27001:2013 Information Security Management Standard

1.5 Overview
This SRS outlines the functional and non-functional requirements for the Bank Management
System. The system will automate core banking operations such as account registration,
login, deposits, withdrawals, and balance inquiries. The document will describe the system
architecture, external interfaces, use cases, performance requirements, and various attributes
of the system.

2. Overall Description

2.1 Product Perspective

The Bank Management System is envisioned as a standalone application, built using Java and
MySQL. It will serve as a bridge between customers and banking staff, providing secure and
seamless management of banking operations.

2.2 Product Functions

The system will support the following primary functions:

 Account Registration
 Account Login
 Deposit and Withdrawal
 Balance Inquiry
 Mini Statement Generation
 Pin Change
 Account Deletion
 Contact Support

2.3 User Characteristics

The system is designed for two types of users:

 Customers: Individuals with basic knowledge of banking procedures and basic

computer literacy.
 Bank Staff: Employees trained to use the system for managing accounts, transactions,
and other banking operations.

2.4 Constraints
The system must comply with banking industry security standards such as data encryption,
secure login protocols, and regular updates to prevent security vulnerabilities.

2.5 Assumptions and Dependencies

 All users must have a stable internet connection to access their accounts.
  The system assumes that all data entered by users is accurate and validated.

2.6 Apportioning of Requirements

Future versions of the system will include additional functionalities, such as fund transfer,
mobile application integration, and the ability to handle multiple types of accounts (savings,
checking, etc.).

3. Specific Requirements

3.1 External Interface Requirements

3.1.1 System Interfaces

The system will interface with MySQL for managing user account data and transaction
records. SQL queries will be used for CRUD (Create, Read, Update, Delete) operations.

3.1.2 User Interfaces

The system will be equipped with a GUI built using Java Swing, allowing users to easily
interact with the system. The user interface will have buttons for each function (e.g.,
"Deposit", "Withdraw", "Balance Inquiry") and will display user-friendly messages and error
notifications.

3.1.3 Hardware Interfaces

The application will run on standard PCs with JRE installed. Users must have access to a
keyboard and mouse for navigation.

3.1.4 Software Interfaces

The Bank Management System will interact with MySQL for data management and Java for
GUI development. The system will run on Java 8 or above.

3.1.5 Communication Interfaces

Secure communication protocols such as HTTPS will be used to ensure secure data
transmission during transactions.
3.2 Functional Requirements

3.2.1 Account Registration

The system should allow users to create new accounts by entering personal details such as
name, address, and contact number. A secure password and PIN will also be required.

3.2.2 Account Login

The system must authenticate users using a secure login procedure, including username and
password validation.

3.2.3 Deposit and Withdrawal

The system should allow users to deposit funds into their accounts and withdraw funds,
subject to account balance limits.

3.2.4 Balance Inquiry

The system will allow users to view their account balance in real-time.

3.2.5 Mini Statement

A mini-statement feature will allow users to see the last five transactions on their account.

3.2.6 Pin Change

Users should be able to change their PIN by providing the old PIN and entering a new one.

3.2.7 Account Deletion

Users may choose to delete their account after proper verification.

3.3 Performance Requirements

 Transaction Processing Time: Each transaction (deposit, withdrawal, balance

inquiry) should complete within 2 seconds.
 System Response Time: The system should respond to user inputs within 1 second.
3.4 Logical Structure of the Data

 User Data: Includes user name, account number, contact information, and PIN.
 Transaction Data: Includes transaction type (deposit/withdrawal), transaction
amount, and date of transaction.

3.5 Design Constraints

The system must be designed using Java and MySQL. It should follow MVC (Model-View-
Controller) design principles to separate business logic from the user interface.

3.6 Software System Attributes

3.6.1 Reliability
The system should be reliable, with a target uptime of 99.9%.

3.6.2 Availability
The system should be available to users 24/7 with minimal downtime for maintenance.

3.6.3 Security
Sensitive data must be encrypted, and secure user authentication protocols must be
implemented.

3.6.4 Maintainability
The system must be easy to maintain, with clear documentation and well-structured code.

3.6.5 Portability
The system should be able to run on multiple operating systems, including Windows, macOS,
and Linux.