Domain modelling
Structured entities and workflows for accounts, transactions, positions, reporting and user-facing summaries.
A private Java application used as a design reference for this portfolio. Public material is intentionally limited to architecture and engineering decisions; source code, credentials and private operational data are not distributed.
Structured entities and workflows for accounts, transactions, positions, reporting and user-facing summaries.
Layered Java design, persistence, validation, access control, error handling and maintainable separation of concerns.
Information hierarchy, filterable data views, responsive layouts and clear states for complex financial information.
The project demonstrates translating a multi-step domain into interfaces, validation rules and persistent data structures.
Secrets must remain outside front-end and repository history, database users should follow least privilege, and public deployments must separate source, runtime configuration and generated artefacts.
Future public documentation can include unit tests, integration tests, database migration checks and browser-level workflow tests once evidence is prepared for release.
No user numbers, financial returns, production uptime or commercial claims are made because public verification has not been provided.