How lleonardogr/caixaverso works
Project type and purpose (from file tree + README)
This is a small Java/Maven project (single module, pom.xml) that looks like a console/CLI banking simulation or “cashier” domain model:
• Entrypoint: fiap.tds.Main
• Core domain: Bank, Account, Transaction + concrete transaction types (Deposit, Withdrawl, TransferIn, TransferOut)
• Domain primitives/value objects: Money, and identifier types (AccountId, TransactionId)
• Utility/service: TxFmt (likely transaction formatting for printing/statement)
There is no evidence of:
• web/API layer (no Spring, no controllers)
• persistence (no repositories, no resources, no DB drivers)
• multi-module architecture
File-structure-driven architecture (what to model)
Use the package layout as your “component boundaries”:
Runtime / Execution boundary
• fiap.tds.Main
Role: Process entrypoint; orchestrates interactions (likely reads input, calls Bank, prints output).
Core application/domain boundary
• fiap.tds.Bank
Role: Primary façade/service for banking operations. Likely coordinates accounts and transactions (create account, deposit, withdraw, transfer).
• fiap.tds.entities.account.*
• Account, AccountId
• fiap.tds.entities.transaction.*
• Transaction, TransactionId
• Concrete transaction types:
• Deposit
• Withdrawl (typo noted; still a distinct type)
• TransferIn
• TransferOut
• fiap.tds.entities.valueObjects.Money
Role: Domain value object to represent currency amounts safely.
Supporting/utility services
• fiap.tds.services.TxFmt
Role: Transaction formatting/presentation helper (likely transforms Transaction objects into strings for display/logging/statements).
Build/dependency boundary
• pom.xml
What the “system” is (and isn’t)
Since there’s no external infrastructure in the tree, treat this as:
• Actor: “User” (or “Operator”)
• System: “CaixaVerso CLI (Java process)”
• Storage: likely in-memory collections inside Bank (unless code says otherwise)
• External services: none visible
Important architectural patterns/design principles visible here
• Domain-driven modeling: Entities (Account, Transaction) + Value Object (Money) + IDs (AccountId, TransactionId)
• Transaction polymorphism: Transaction base type with subtype variations (deposit/withdraw/transfer in/out)
• Single-process layered design: CLI orchestration separated from domain model