← ~/projects
$ cat projects/dams-dealer-activity.md
DAMS — Dealer Activity Management System
Multi-tenant accounting workflow for truck-dealer service stations.
Contributor · JJ Software internshipSeptember 2026Full Stack
// why: Replaces Excel-based service-station bookkeeping with an auditable multi-tenant system.
$ cat projects/dams-dealer-activity.md▌
TL;DR
- Multi-tenant: org-level isolation enforced in the persistence layer
- Auditable: maker-checker approvals, gap-free document numbers
- Scoped: five roles plus a read-only auditor, each limited to their branches
// what does it do?
Java 21 and Spring Boot 3 backend with a React front end for dealership receipts, expenses, cash and warranty claims. Contributed merged pull requests (responsive interface overhaul, login normalization, vehicle de-duplication) during the JJ Software internship.
// why this project?
Service-station bookkeeping lives in Excel, which makes audits and approvals hard to trust.
// results
- Tenant isolation is enforced structurally with an org-level Hibernate filter, approvals follow a maker-checker rule, and document numbers are gap-free per branch and month. Five roles plus a read-only auditor see only their branches. The repository is maintained by the project lead
- my work is the merged pull requests.
Java 21 + Spring Boot 3 + ReactMerged PRs: responsive overhaul, login normalization, vehicle de-duplication
Tech stack
Java 21Spring Boot 3PostgreSQLFlywayReactTypeScript