Discussion on Division of Project Function Modules

[PI-33]

Project Status

• Prototype design completed
• Basic framework built
• Navigation system implemented

Functional Module Division

1. Core Accounting Function (AddTransaction.fxml)

• CRUD operations for transaction records
• CSV data import/export
• Management of transaction categories
• Estimated workload: 3-4 days

2. Data Visualization Module (Dashboard.fxml)

• Home page display
• Income and expenditure trend chart
• Recent transaction display
• Estimated workload: 2-3 days

3. AI Recognition Module (AIRecognition.fxml)

• Upload of invoice images
• OCR text recognition
• Intelligent classification
• Estimated workload: 4-5 days

4. Budget Management Module (Budget.fxml)

• Budget Setting
• Budget Tracking
• Over-expenditure Alert
• Estimated Workload: 2-3 days

5. Report Analysis Module (Reports.fxml)

• Monthly/Annual Reports
• Expenditure Analysis
• Income Analysis
• Estimated Workload: 3-4 days

Technical Highlights

1. JavaFX UI Development
2. CSV File Processing
3. Chart Library Application
4. AI Interface Integration

Suggested Division of Labor

Please choose 1-2 modules based on your technical expertise in the comments below, each group member.

Timeline

1. Week 1: Complete core accounting functions
2. Week 2: Complete visualization and budgeting modules
3. Week 3: Complete AI recognition and reporting modules
4. Week 4: Overall testing and optimization

Please leave your comments below, team members:

1. Select the module you are interested in.
2. Suggest your ideas on the division of labor.
3. Share your thoughts on the technical implementation.

[PI-33]

I am very interested in participating in the development of the Data Visualization Module (Dashboard.fxml).

• Specific implementation ideas:
  • I have completed the basic layout design of the Dashboard, including the navigation bar, data cards, and chart area.
  • I plan to optimize the existing income and expenditure trend chart and add the following functions:
  • Implement dynamic data update
  • Add chart interaction functions (such as data point hover tips)
  • Support time range filtering
  • Optimize the display of the recent transaction list, add category labels and search functions
• Time planning:
  • The estimated workload of 2-3 days is reasonable and feasible
  • All core functions can be developed before Week 2
  • Leave sufficient time for UI optimization and performance tuning

[KJiwb-LG]

I will take responsibility for Budget Management Module (Budget.fxml).

Specific Implementation Ideas:
Budget Setting:

• Design a user-friendly interface for creating/editing budgets (e.g., monthly/quarterly categories like "Food," "Transport," etc.).
• Include validation rules (e.g., preventing duplicate entries or invalid amounts).
• Enable recurring budget configurations and percentage-based allocations.

​Budget Tracking:

• Automatically sync transaction data from linked accounts to update budget progress in real time.
• Visualize spending vs. budget using progress bars, pie charts, or bar graphs.
• Categorize transactions dynamically to ensure accurate budget calculations.

​Over-Expenditure Alert:

• Set customizable thresholds (e.g., 80% of budget) to trigger email/mobile notifications.
• Generate summary reports highlighting overspent categories and suggesting adjustments.

Time Planning:
Estimated Workload: 2–3 days (validated as feasible).

• Days 1–2: Develop core features (budget setup, tracking UI, alert logic).
• ​Day 3: Implement data synchronization, validation, and basic alerts.

[2247571347]

I am very interested in participating in the development of the Data Visualization Module (Dashboard.fxml).

• Specific implementation ideas:

  • I have completed the basic layout design of the Dashboard, including the navigation bar, data cards, and chart area.
  • I plan to optimize the existing income and expenditure trend chart and add the following functions:
  • Implement dynamic data update
  • Add chart interaction functions (such as data point hover tips)
  • Support time range filtering
  • Optimize the display of the recent transaction list, add category labels and search functions

• Time planning:

  • The estimated workload of 2-3 days is reasonable and feasible
  • All core functions can be developed before Week 2
  • Leave sufficient time for UI optimization and performance tuning

Then about my work, I am very happy to be involved in the development of AIRecognition.fxml).

• Concrete implementation ideas:
  ◦I have completed the basic layout design of this interface and implementation of manual modification of recognition results
  ◦I plan to use AI to organize the bookkeeping data (photos) into .json form and process it to implement the following features:
  ◦Automatically fill in the form data
  ◦ Write the data to transaction.csv file after saving it
• Time planning:
  ◦ Expected workload of 4-5 days is reasonably feasible
  ◦ All core functions can be developed before the second acceptance.
  ◦ Allow sufficient time for the third phase of user interface optimization and performance tuning and AI recognition accuracy improvement.

[TuRanJinTianNei]

Response: Volunteering for AddTransaction Module

I’ll take ownership of the Core Accounting Module (AddTransaction.fxml). Here’s my plan:

Technical Approach:

1. CRUD & UI: Implement JavaFX TableView with ObservableList for dynamic updates. Use dialogs (DialogPane) for add/edit actions, with input validation (e.g., regex for amount/date).
2. CSV Handling: Use OpenCSV for parsing/generating CSV files. Add FileChooser for import/export paths.
3. Category Management: Store categories in a SQLite table, linked via foreign keys to transactions.
4. Database: Use JDBC for SQLite integration; design schema with transactions and categories tables.

Collaboration:

• Provide a TransactionService API for other modules (e.g., Dashboard to fetch data).
• Use an EventBus to notify modules (like Budget) when transactions are updated.

Timeline:

• Day 1-2: Complete UI + CRUD + DB setup.
• Day 3: Integrate CSV features.
• Day 4: Finalize validations + unit tests.
• Buffer: Sync with Dashboard team for real-time data sync.

Optional Support:
Can assist Budget module with category-related logic if needed. Let me know if adjustments are required! 🚀

[QimingWu1]

Report Analysis Module (Reports.fxml)​​
​Specific Implementation Ideas:​​

​1. Monthly/Annual Reports​
Design an intuitive interface to generate and compare reports across customizable timeframes (e.g., monthly, quarterly, or annual summaries).
Support export functionality (PDF, CSV) for sharing or offline analysis.
Include filters for granular data segmentation (e.g., by category, payment method, or custom tags).
​2. Expenditure Analysis​
Visualize spending patterns using dynamic charts (e.g., trend lines, stacked bar charts) to highlight top expense categories.
Implement drill-down capabilities to view transaction details behind aggregated totals.
Compare actual spending against historical averages or user-defined benchmarks.
​3. Income Analysis​
Track income sources (salary, investments, etc.) with pie/bar charts to show distribution.
Calculate net savings (Income vs. Expenditure) and display progress toward financial goals.
Integrate forecasting tools to project future income based on historical trends.
​Additional Features:​​

​Interactive Dashboards: Allow users to customize widgets (e.g., top expenses, savings rate) for at-a-glance insights.
​Automated Insights: Flag anomalies (e.g., unusually high spending in a category) with actionable suggestions.
​Validation Rules: Ensure data consistency (e.g., prevent negative values or misclassified transactions).
​Time Planning:​​

​Estimated Workload: 3–4 days (validated as feasible).
​Days 1–2: Develop core reporting UI, chart integrations, and basic filtering logic.
​Day 3: Implement data aggregation, export features, and dynamic visualizations.
​Day 4: Refine user interactions (e.g., drill-downs), automated insights, and testing.

[tonysu9]

Response: Progress Report for AddTransaction Module
Technical Progress
1.Transaction List Implementation
Functional transaction history display with dynamic sorting (date-based) and basic UI rendering (icons, styled amounts).
Initial filtering logic for date ranges and transaction types via UI controls (DatePicker, ComboBox).
Pagination support with fixed item count per page.
2.Navigation & Data Initialization
Seamless module navigation through centralized controller methods.
CSV-based transaction data loading with file parsing and validation.
3.Dynamic Filtering Upgrade
Transition from manual list iteration to JavaFX FilteredList with predicate bindings for real-time, efficient filtering.
Auto-refresh UI on filter changes without full list reloads.
4.Pagination-Dynamic Data Sync
Link pagination controls to filtered dataset size for accurate page count updates.
Ensure page navigation retains active filters.
5.Transaction Detail Layer
Implement click-triggered dialog displaying full transaction metadata (category details, remarks, attachments placeholder).
6.Data Persistence Transition
Migrate from CSV to SQLite with indexed date/type columns for query optimization.
Schema design to support category relationships and bulk operations.
Collaboration & Interfaces
Cross-Module Data Services
Develop TransactionQueryService to provide filtered datasets (e.g., monthly summaries for Dashboard charts).
Standardize data formats for inter-module consistency (e.g., date ranges, category IDs).
Implementation Timeline
Day 1-2: SQLite migration + FilteredList/predicate integration
Day 3: Pagination-dynamic binding + Detail dialog implementation
Day 4: Search field integration + CSV export/import refinement
Buffer Day: Stress testing + UI responsiveness tuning
Optional Support Offerings
Assist Budget Module with category-based filtering hooks.
Develop shared validation utilities for amount/date inputs.