# ayusshhh27/finance-tracker architecture

> Architecture diagram of the GitHub repository ayusshhh27/finance-tracker, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-29). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/ayusshhh27/finance-tracker
- Repository: https://github.com/ayusshhh27/finance-tracker

## Overview

##### Main Components
- FinanceTracker Main Class – This is the entry point to the application and will orchestrate the overall flow.
- Transaction Management Module – Handles adding, storing, and retrieving transactions. It should include functionalities such as capturing descriptions, amounts, categories, and timestamps.
- Budget Management Module – Manages the monthly budget, updates budget balance, and performs validations.
- Category Management Module – Enables dynamic creation of transaction categories.
- Transaction Summary/Reporting Module – Responsible for aggregating and displaying transaction history, summaries, and balance tracking.
- Utility Components – Highlight the use of the Java DateTime API for managing date and time, and internationalization elements for handling different currency symbols and locale-specific formats.

##### Component Relationships and Data Flow
- That the Transaction Management Module “queries” the DateTime API and internationalization utilities to correctly record and format dates and currency.

##### Architectural Patterns and Technologies
- Even though the project is a monolithic Java application, treat each module as a distinct component within the overall structure.
- That the application is designed with separation of concerns in mind – clearly isolating transaction handling, budgeting, category operations, and reporting.
- Integration of standard Java libraries (DateTime API, internationalization libraries) as utility helper components that support multiple modules.

##### Elements
- Optionally, add annotations to each component highlighting the core functionalities or responsibilities.

## Diagram (Mermaid)

```mermaid
graph TD
    subgraph "Core Modules"
        A["FinanceTracker (Main)"]:::main
        B["Transaction Manager"]:::module
        C["Budget Manager"]:::module
        D["Category Manager"]:::module
        E["Summary & Reporting"]:::module
    end
    subgraph "Utility Components"
        F["DateTime & i18n Utilities"]:::utility
    end

    A -->|"activates"| B
    A -->|"activates"| C
    A -->|"activates"| D
    A -->|"activates"| E
    B -->|"updatesBudget"| C
    B -->|"reportsTo"| E
    B -->|"queries"| F

    click A "https://github.com/ayusshhh27/finance-tracker/blob/main/FinanceTracker.java"
    click B "https://github.com/ayusshhh27/finance-tracker/blob/main/FinanceTracker.java"
    click C "https://github.com/ayusshhh27/finance-tracker/blob/main/FinanceTracker.java"
    click D "https://github.com/ayusshhh27/finance-tracker/blob/main/FinanceTracker.java"
    click E "https://github.com/ayusshhh27/finance-tracker/blob/main/FinanceTracker.java"
    click F "https://github.com/ayusshhh27/finance-tracker/blob/main/FinanceTracker.java"

    classDef main fill:#BBDEFB,stroke:#0D47A1,stroke-width:2px;
    classDef module fill:#C8E6C9,stroke:#2E7D32,stroke-width:2px;
    classDef utility fill:#FFCDD2,stroke:#C62828,stroke-width:2px;
```
