How mohinik7/budgettracker works
Main Components
• User Interface (UI) Layer: This comprises the Java Swing components (e.g., LoginFrame, BudgetFrame, AccountFrame, etc.) that handle user interactions.
• Business Logic / Controller Layer: This layer ideally processes inputs, leverages validation (via classes like ValidationUtils), and manages workflow between the UI and data access components.
• Data Access Layer: The DAO classes (AccountsDAO, BudgetsDAO, CategoriesDAO, RecordsDAO, UsersDAO) encapsulate interactions with the database.
• Database Layer: The MySQL backend which stores tables such as users, accounts, categories, records, and budgets.
• Database Connection: The DatabaseConnection class is responsible for establishing the JDBC connection between the application and the MySQL database.
Relationships and Interactions
• The User Interface (frames) communicates with the Business Logic layer to process users’ commands (e.g., log in, record a transaction, set a budget).
• The Business Logic layer calls the Data Access Objects (DAO) to retrieve or persist data.
• Data access operations rely on the DatabaseConnection to execute queries against the MySQL database.
• There is also a configuration and initialization process outlined in the README (e.g., setting up the database and establishing the connection).
Architectural Patterns and Technologies
• That the project uses the DAO pattern for data management, ensuring separation of concerns between business logic and database operations.
• The UI is built using Java Swing; thus, associate all *Frame classes (e.g., LoginFrame, DashboardFrame) with the presentation layer.
• The interplay between UI, Validations (ValidationUtils), and the DAOs should be captured clearly.