How maximusf/wallet-watch works
Project type and purpose
• Wallet-Watch is a Java-based, command-line personal budget manager. It’s a monolithic, layered application with a CLI “UI,” a service layer, a DAO (data access) layer, a domain (models) layer, and a MySQL database backend.
File structure
• Top-level folders:
• bin/ (compiled .class files)
• lib/ (MySQL connector jar)
• db/ (schema & reset scripts)
• src/ (source code, subdivided into dao, models, services, util, test)
• planning/ (flowchart PDF)
• Key files:
• Main.java: application entrypoint
• dao/*.java: CRUD operations for Transaction, Income, Expense
• services/*.java: business rules, validation, error handling
• models/*.java: domain objects, inheritance (Transaction → Income/Expense)
• util/Environment.java & PrintBuilder.java: config loader & console formatting
README for architectural insights
• Confirms layered OOP design: inheritance, encapsulation, abstraction in service/DAO layers, PrintBuilder for output formatting, MySQL for persistence.
• No external web or microservice components, but a clear separation of concerns and a console UI.
Components
a. User / CLI (Main + PrintBuilder)
b. Service Layer (ExpenseService, IncomeService, Transaction orchestration)
c. DAO Layer (ExpenseDAO, IncomeDAO, TransactionDAO)
d. Domain Models (Transaction ← Income, Expense)
e. Utilities (Environment, PrintBuilder)
f. Database (MySQL with schema.sql, reset_db.sql)
g. External library (mysql-connector-j)
Relationships & Data Flow
• User types commands → Main invokes PrintBuilder → Main calls appropriate Service
• Service enforces rules & validation → calls DAO
• DAO executes SQL queries on MySQL → returns data models
• Service may transform models → PrintBuilder formats & prints results
• Environment utility reads DB connection settings → DAO uses them
Architectural patterns & principles
• Layered Architecture: UI → Service → DAO → Database
• Inheritance/Polymorphism: Transaction base class, Income/Expense subclasses
• DAO Pattern for persistence
• Single Responsibility: each package has a clear role
• Abstraction: Service/DAO interfaces hide implementation details from Main