The scenario
Design an ER diagram for a wedding hall management system that tracks customers, hall reservations, add-on services, invoices, and payments.
What is in this drawing
Read the decisions behind it.
01
Used a composite-key junction table BookingService to model many-to-many bookings and services
02
Separated Invoice and Payment to support partial payments and due tracking
03
Kept Hall as a distinct entity with capacity and pricing attributes
Use for systems needing reservation, add-on service, and billing workflows for venue or event management.
More like this