The scenario
An expense tracker application supports users in logging expenses manually or via bank imports, categorizing transactions, generating reports, and setting budgets. Recurring expenses extend manual logging, and categorization is included in both logging and import to avoid redundancy.
What is in this drawing
Read the decisions behind it.
01
Used include relationship for categorization to centralize the common action
02
Added extend relationship for scheduling recurring expenses from the manual log flow
03
Modeled external bank system as an actor to represent API integration
Use this pattern when designing personal finance or expense management systems that require bank integration, recurring transaction handling, and modular categorization logic.
More like this