System design dossier · Team lead
MOAB Family RV Park Reservation System
A requirements-and-design case study for replacing paper records and phone reservations with a responsive reservation platform covering availability, booking, payments, role-based operations, reporting, auditability, and system design artifacts.
The design targets a manual campground process built around paper records and phone reservations, where double bookings, inconsistent tracking, and payment delays can occur.
Customer, Employee, and Admin workflows are separated with role-aware reservation, account, reporting, pricing, and management capabilities.
Reservations must prevent overlapping double-bookings. Payments are linked to reservations and customers, while categories, sites, rates, and availability remain manageable by staff.
The requirements target 99.5% monthly uptime, comfortable concurrency for roughly 50 staff and 200 customers, audit logs, operational metrics, alerts, and rate-limited authentication.
Visual architecture
Jump straight into the engineering artifacts.
The document includes a UML use-case model, activity diagrams, a class model, reservation sequence flow, an entity-relationship model, and working UI mockups. The embedded viewer opens directly on the ER diagram; the links below jump to the most useful visual sections.
If your browser blocks embedded PDF viewing, use “Open full design PDF” above. Page anchors are included so hiring managers can jump directly to the architecture artifacts instead of searching the document.
What this demonstrates
Requirements translated into a system, not just a screen.
Stakeholder analysis across customer, employee, and administrator responsibilities.
Functional design for accounts, reservations, payments, site categories, pricing, reporting, search, and access control.
Non-functional thinking around availability, concurrency, logging, security, monitoring, and modular service boundaries.
Visual modeling through UML, sequence flows, ER design, and UI mockups before implementation.