Collaborative Boards (Trello Clone)

Fri, 01 May 2026 00:00:00 +0000

Description

Project for collaborative work management using boards and tasks. The system organizes work through cards flowing across customizable lists, ensuring data persistence and pure domain-driven design.

Core Features

Board Management: Creation of boards associated with an email address (the system’s primary identity).
Lists and Workflow: Creation of task lists (columns) within boards.
Rich Cards: Support for simple task cards and checklists (verification items).
Classification and Completion: Use of tags (name and color) to identify cards and ability to automatically send them to a designated “Completed” list.
Traceability: Board history log recording all card events and movements.
Board Control: Temporary board locking by the owner (preventing new card/list creation while allowing movement of existing ones).

Implemented Optional Features (7/7)

List-level Rules: Restriction of maximum card capacity (maxCards) per column.
Visual Filtering: GUI tool to instantly filter cards by tag name or color.
YAML Templates: Preconfigured base board loading system dynamically from .yaml files.
Automatic Compaction: Scheduled background task (@Scheduled) for automated board maintenance and cleanup.
Passwordless Authentication: Secure access system via temporary code sent by email (valid for 5 minutes), protected by REST Interceptors.
Permissions Management: Board owners can invite other users via email, granting granular READ or WRITE roles, as well as revoking access.
Automation Rules: Custom user rule engine (“If event X occurs -> do Y”).

Architecture & Design (DDD)

The project abandons traditional MVC in favor of Hexagonal Architecture (Ports and Adapters):

The Domain at the Core: Rich entities protecting their invariants.
Aggregate Roots: Board (manages lists, history, permissions, and automations) and Card (manages checklists and tags).
Value Objects: Immutable identifiers such as BoardId, CardId, ListId, and Email.
Technical Isolation: Repositories and external services communicate with the domain exclusively through Ports (Interfaces). Persistence (H2 + JPA) resides in the Infrastructure layer as an Output Adapter.
UI Protection: The desktop interface (JavaFX) acts as an Input Adapter interacting via REST Endpoints using DTOs and immutable Command Objects.

Software Testing & Quality

Unit Tests: Domain behavior and isolated use cases verified using Mockito and JUnit 5.
Integration Tests: Full validation of REST adapters, JPA repositories, and security flows using MockMvc with in-memory databases.
Architectural Testing: Intensive use of ArchUnit to guarantee that no infrastructure class breaches the domain.

Installation & Execution

Technical Requirements: Java JDK 21, Maven 3.8+.

Cloning and Running:

git clone [https://github.com/GuillermoPL/PDS-25-26.git](https://github.com/GuillermoPL/PDS-25-26.git)
cd PDS-25-26
mvn clean install

ExpenseManager V2

Fri, 01 May 2026 00:00:00 +0000

Description

ExpenseManager is a robust solution for financial control. Unlike simple expense trackers, this system implements complex logic for shared accounts (flatmates, trips, couples) and a proactive alert system based on temporal strategies.

Technical Features

Expense Management (CRUD): Detailed tracking with date, amount, category, and payer, supporting secure editing and deletion.
Shared Accounts: Group management with configurable splitting algorithms (Equitable vs. Percentage) for automatic debt calculation among users.
Alert System: Real-time notifications upon exceeding user-defined spending limits (Weekly or Monthly).
Statistical Dashboard: Data visualization using interactive charts and advanced filtering (by dates and multiple categories).
Bulk Import: Data loading from external CSV files using robust adapters.
Persistence: Automatic local storage in JSON format using the Jackson library.

Architecture & Design Patterns

The project strictly follows the MVC (Model-View-Controller) pattern alongside several GoF design patterns to ensure scalability and maintainability:

Singleton: Unique session management (ControladorSesion) and factories (FactoriaEstrategia, FactoriaImportadores).
Strategy: Interchangeable algorithms for expense splitting (RepartoEquitativo, RepartoPorcentual) and temporal alert logic (EstrategiaAlertaMensual, EstrategiaAlertaSemanal).
Factory Method: Dynamic creation of strategies and importers based on context, decoupling instantiation from business logic.
Observer: Reactive communication where ControladorAppGastos automatically notifies Views (IObservador) of model changes.
Adapter: Integration of external CSV files into the application domain (ImportadorCSV -> ImportadorGastos).
Repository (DAO): Abstraction of the data layer (RepositorioGastosJSON, RepositorioCuentasJSON) for flexible storage switching.

Code Quality (Clean Code)

Design by Contract: Defensive validations in constructors and setters to ensure data integrity (preventing negative amounts, null values, etc.).
Modern Java (Streams & Lambdas): Extensive use of the Stream API for financial calculations and collection filtering.
Immutability: Protection of internal data structures using defensive copies and unmodifiable lists.

Installation & Execution

Technical Requirements: Java JDK 21 (Mandatory), Maven 3.8+.

GUI Mode (JavaFX):

git clone [https://github.com/GuillermoPL/TDS-25-26.git](https://github.com/GuillermoPL/TDS-25-26.git)
cd TDS-25-26
mvn clean javafx:run

JavaFX | Guillermo F. Parra

Collaborative Boards (Trello Clone)

Description

Core Features

Implemented Optional Features (7/7)

Architecture & Design (DDD)

Software Testing & Quality

Installation & Execution

ExpenseManager V2

Description

Technical Features

Architecture & Design Patterns

Code Quality (Clean Code)

Installation & Execution