BMS Info

High Level Design
1. Architecture
Client-Server Architecture: The system follows a client-server architecture where the client side is developed using Java Swing for the GUI and the server side is managed with a MySQL database using XAMPP.
Three-Tier Architecture:
Presentation Tier: Java Swing-based GUI
Business Logic Tier: Java classes handling the core functionality
Data Tier: MySQL database for storing user data, transaction history, etc.
2. Components
User Interface Components: Login screen, main dashboard, deposit form, withdrawal form, transaction history view, balance inquiry, and pin change form.
Business Logic Components: Java classes for handling login validation, deposit/withdrawal transactions, balance checks, pin changes, and transaction logging.
Database Components: Tables for user information, account details, transaction history, and logs.

Detailed Design
1. User Interface
Login Screen: Fields for username and password, with login and reset buttons.
Main Dashboard: Navigation buttons for deposit, withdraw, check balance, transaction history, and change pin.
Deposit/Withdraw Forms: Input fields for account number and amount, with submit and cancel buttons.
Transaction History View: Table displaying list of transactions with columns for date, type, amount, and balance.
Balance Inquiry Screen: Display current balance with refresh button.
Change Pin Form: Fields for old pin, new pin, confirm new pin, with submit and cancel buttons.
2. Database Schema
User Table: Fields for userID, username, password, pin, account number.
Account Table: Fields for accountID, userID, balance.
Transaction Table: Fields for transactionID, accountID, date, type (deposit/withdraw), amount, balance after transaction.
Log Table: Fields for logID, userID, action, timestamp.
3. Business Logic
Authentication: Validation of user credentials during login.
Transaction Processing: Logic for deposit and withdrawal operations, including balance updates and transaction logging.
Balance Checking: Fetching and displaying current balance for the user.
Pin Management: Validating and updating user PINs.
Error Handling: Handling exceptions and providing user feedback for invalid operations.

Setup Development Environment
1. Tools and Technologies
IDE: NetBeans
Programming Language: Java
GUI Framework: Java Swing
Database: MySQL
Server Stack: XAMPP (Apache, MySQL, PHP, and Perl)


Coding
1. Database Connection
Code for establishing a connection: Using JDBC to connect Java application with MySQL database.
2. Authentication Logic
Code for user authentication: Methods for validating username and password during login.
3. Transaction Processing
Code for deposit and withdrawal: Methods for processing deposit and withdrawal requests, updating account balance, and recording transactions.
4. User Interface Handling
Event Listeners: Implementing action listeners for buttons and other interactive components in the GUI.
5. Error Handling
Exception Management: Code to handle SQL exceptions, invalid input, and other runtime errors gracefully.

Integration
1. GUI and Backend Integration
Connecting UI with business logic: Ensuring the actions performed in the GUI are accurately reflected in the backend processes.
2. Database Operations
CRUD Operations: Integration of create, read, update, and delete operations with the MySQL database.
3. Testing
Unit Testing: Writing unit tests for individual components and methods.
Integration Testing: Testing the system as a whole to ensure seamless interaction between different components.

Methodology
Define Project Goals
Goal 1: Provide a secure and user-friendly interface for bank customers to manage their accounts.
Goal 2: Ensure the system handles transactions efficiently and records them accurately in the database.
Goal 3: Implement robust error handling and security measures to protect user data and prevent unauthorized access.