How sarosh13/project-banking-application works
Main Components
• User Interface (UI) Layer: Represented by the Swing components. This includes several screens such as:
• FirstFrame – The dashboard where users choose to log in or create a new account.
• Login – The authentication screen for existing users.
• NewAccount – The registration screen for new users.
• Cash – Likely handling the core banking transactions (Deposit, Withdrawal, Balance enquiry, etc.).
• EndFrame – The exit or logout screen.
• Business Logic / Application Layer: Although not clearly compartmentalized into separate packages in the file tree, the code classes encapsulate the logic of handling user actions (login validations, account creation, security protocols, and money related operations).
• Data Access Layer: While there is no explicit “database” folder in the file tree, the README indicates that MySQL is used with the JDBC Connector. This suggests that database operations (like storing account balances, user credentials, transaction history) are performed through JDBC calls likely embedded within these classes.
• External Systems / Dependencies: This includes the MySQL database server and security protocols to validate login entries.
Relationships and Data Flow
• Upon successful login (using the Login screen), the user is taken to the ATM UI (Cash class), where they can choose deposit, withdrawal, balance enquiry, or exit.
• Operations from the Cash component interact with the backend (business logic) that, in turn, communicates with the MySQL database using the JDBC Connector.
• Finally, upon choosing exit, the EndFrame is displayed.
• User input → FirstFrame → (choice between “Login” or “Create Account”).
• Login → Validate credentials through business logic → Query/Update MySQL DB (via JDBC).
• Cash (ATM UI) → Transaction processing → Database update, etc.
Important Architectural Patterns
• Presentation Layer (Swing UI components)
• Business Logic Layer (which includes security checks and banking operations)
• Data Access Layer (MySQL interactions via JDBC)
• Noting any security check patterns, such as verifying login credentials before allowing access to sensitive transactions.
Relevant Technologies and Frameworks
• Java as the programming language.
• Swing for building the graphical user interface.
• MySQL for data persistence.
• JDBC Connector for database communication.