How vaibhav-pant/atm-management-system works
Project Type and Purpose
• This is a standalone desktop ATM Management System written in Java, using JSwing and AWT for the GUI.
• It simulates ATM operations (sign-up, login, deposit, withdraw, balance inquiry, fast cash, mini statement, PIN change) and persists data in a MySQL database.
Analysis of File Structure
• Top-level Java classes each correspond to a GUI screen or transaction:
• SignUp1.java, SignUp2.java, SignUp3.java – three-step user registration
• LoginPage.java – authentication screen
• deposit.java, withdraw.java, FastCash.java – cash operations
• BalanceEnq.java – balance enquiry
• MiniStatement.java – transaction history
• PinChange.java – PIN update
• transaction.java – core transaction logic
• mysql.java holds JDBC connection and query execution code.
• mysqlQueries.sql defines the database schema and initial data.
• images/ contains UI graphics.
• Two JARs for third-party dependencies: jcalendar-tz and MySQL connector.
Key Components
a. Presentation Layer (Swing/AWT GUIs)
• Sign-up forms, Login page, Dashboard, Transaction screens.
b. Application Logic Layer
• transaction.java orchestrates operations.
• Each Java class handles its own event listeners and invokes transaction methods.
c. Data Access Layer (DAL)
• mysql.java uses JDBC to run SQL statements defined in mysqlQueries.sql.
d. Database
• MySQL server hosting user, account, and transaction tables.
e. External Libraries
• mysql-connector-java.jar for JDBC.
• jcalendar-tz.jar for date-picker UI component.
Relationships and Data Flows
• User interacts with a GUI screen → Controller code in the same Java class validates input.
• Controller calls methods in transaction.java for business rules.
• transaction.java uses mysql.java to execute SQL queries via JDBC.
• JDBC returns results, which propagate back to the GUI for display.
• All screens share a single MySQL connection (or connection pool) managed by mysql.java.
Architectural Patterns and Principles
• Layered architecture: Presentation → Business Logic → Data Access → Database.
• Single-process monolith: all modules in one JVM.
• Separation of concerns: GUI classes vs. transaction logic vs. database connectivity.