Expense Tracking System
Designed and documented complete expense module scope: use cases, system architecture, flowcharts, ERD, implementation plan, and testing/edge cases. Includes sequential multi-level approval, paid-out handling, and final reclassification.
Mapped complete product scope and user journeys for dashboard, policy, finance, inbox, and mobile.
- Role-based use cases and permissions
- Clear request and approval status definitions
- Business rules for category and approval lifecycle
Defined service boundaries and integration points for expense flow, approvals, files, and notifications, where Setting is reference-only and not tightly coupled to Expense runtime operations.
- Setting data is used as reference metadata only
- No tight coupling between Setting and Expense module behaviors
- Web and mobile client channels
- Workflow and notification orchestration
- Security and audit boundaries
Designed sequential approval lifecycle with immutable snapshots and controlled finance transitions.
- Up to 4 approvers in strict order
- Approval to paid-out lifecycle transition
- Policy-change safety rules
Created a relational model covering categories, policy mapping, expenses, approvers, and file attachments.
- Loose coupling via request-time approver snapshot
- Policy updates do not mutate existing expense records
- Attachment + proof-of-payment traceability
Prepared phased rollout plan with API tasks, UI tasks, permissions, and migration strategy.
- Dashboard + mobile delivery slices
- Feature-ready validation gates
- Safe rollout checklist and fallback
Specified unit, integration, and E2E coverage with high-risk edge cases.
- Sequential approval race-condition checks
- Policy updates do not impact existing expenses
- Paid-out and finance field access guards