ER Model

Description

This page presents the Entity–Relationship (ER) model of the Wedding Planner system. The ER model defines the core entities, their attributes, and relationships required to support wedding organization, event scheduling, guest management, and service reservations.

Entity-Relationship Model – Wedding Planner

Diagram

Entities and Relationships

The ER model consists of the following main entities: User, Wedding, Event, Guest, Event_RSVP, Attendance, Venue, Venue_Type, Venue_Booking, Photographer, Photographer_Booking, Band, Band_Booking, Church, Priest, Registrar, and Registrar_Booking.

Wedding is the central entity of the model. It represents a single wedding and acts as the main aggregation point for all related data.

A User can organize multiple Weddings (1:N). Each Wedding belongs to exactly one User.

A Wedding can have multiple Events (1:N). Events represent scheduled parts of the wedding, such as ceremonies or receptions.

Guests are associated with a Wedding (1:N). Guests do not have system accounts and are modeled separately from users.

Guest participation in events is modeled through two associative entities: Event_RSVP (for invitation responses) and Attendance (for actual attendance details). Both represent many-to-many relationships between Guest and Event.

All service reservations (Venue, Band, Photographer, Registrar) are associated directly with Wedding through booking entities. This reflects the real-world rule that services are reserved for the entire wedding, not for individual events.

The Wedding–Church relationship is modeled as one-to-one (1:1), enforcing that each wedding is held in exactly one church.

No redundant or duplicate relationships are present in the final ER model.

ER Model History

v0.1 – Initial ER model v0.2 – Updated Church–Wedding relationship v0.3 – Refined constraints and relationships v0.4 – Model cleanup and clarity improvements v0.5 – Final ER model aligned with relational design