Changes between Initial Version and Version 1 of ERModel

Timestamp:

12/27/25 19:04:29 (3 days ago)

Author:

213087

Comment:

--

ERModel

@@ +1 @@
+
+
+
+== ** Entity-Relationship Model Wedding_Planner** 
+
+
+
+
+== **Diagram**
+[[Image(Wedding_planner_Version.01.png, width=100%)]]
+
+
+
+== **Data requirements** 
+
+== **Entity: User**
+
+Explanation:
+The User entity represents a registered person who uses the system to organize and manage weddings and related events. It stores personal and contact information and serves as the main actor that creates weddings, organizes events, and interacts with guests and service providers. The entity is modeled separately to centralize user data and enable secure identification and ownership of weddings.
+
+
+**Candidate keys:**
+
+user_id – chosen as the primary key because it is a system-generated, stable, and unique identifier.
+
+email – candidate key because it is unique per user, but not selected as the primary key since it can change.
+
+
+**Attributes:**
+
+user_id – numeric, required
+
+first_name – text, required
+
+last_name – text, required
+
+email – text, required, valid email format
+
+phone_number – text, optional
+
+gender – text, optional
+
+birthday – date, optional
+
+
+== Entity: Wedding
+
+Explanation:
+The Wedding entity represents a specific wedding event being planned and managed in the system. It acts as the central entity that connects all reservations, services, guests, and events related to a wedding. It is modeled as a separate entity to clearly group all wedding-related data and enable independent management of multiple weddings by different users.
+
+
+**Candidate keys:**
+
+wedding_id – chosen as the primary key as a unique system-generated identifier.
+
+
+**Attributes:**
+
+wedding_id – numeric, required
+
+date – date, required
+
+budget – numeric, optional
+
+notes – text, optional
+
+
+== **Entity: Event**
+
+Explanation:
+The Event entity represents individual events related to a wedding, such as ceremonies, receptions, or parties. It allows the system to track schedules, types, and statuses of events. Modeling events separately enables flexibility in planning multiple events for a single wedding.
+
+
+**Candidate keys:**
+
+event_id – chosen as the primary key because it uniquely identifies each event.
+
+
+**Attributes:**
+
+event_id – numeric, required
+
+event_type – text, required
+
+date – date, required
+
+start_time – time, required
+
+end_time – time, required
+
+status – text, required
+
+
+== **Entity: Event_RSVP**
+
+Explanation:
+The Event_RSVP entity records responses of users or guests to event invitations. It is necessary to track attendance confirmations and response statuses for proper event organization.
+
+
+**Candidate keys:**
+
+response_id – chosen as the primary key as it uniquely identifies each RSVP response.
+
+
+**Attributes:**
+
+response_id – numeric, required
+
+status – text, required
+
+response_date – date, required
+
+
+== **Entity: Guest**
+
+Explanation:
+The Guest entity represents individuals invited to the wedding. It stores guest-specific information independently from registered users, as guests do not need system accounts.
+
+
+**Candidate keys:**
+
+guest_id – chosen as the primary key.
+
+
+**Attributes:**
+
+guest_id – numeric, required
+
+first_name – text, required
+
+last_name – text, required
+
+email – text, optional
+
+
+== **Entity: Attendance**
+
+
+Explanation:
+The Attendance entity represents the participation of guests in wedding events. It enables tracking seating, roles, and attendance status.
+
+
+**Candidate keys:**
+
+attendance_id – chosen as the primary key.
+
+
+**Attributes:**
+
+attendance_id – numeric, required
+
+status – text, required
+
+table_number – numeric, required
+
+role – text, required
+
+total – numeric, required
+
+
+== **Entity: Venue**
+
+Explanation:
+The Venue entity represents physical locations where wedding events take place. It stores capacity, pricing, and contact details to support venue selection and booking.
+
+
+**Candidate keys:**
+
+venue_id – chosen as the primary key.
+
+
+**Attributes:**
+
+venue_id – numeric, required
+
+name – text, required
+
+location – text, required
+
+city – text, required
+
+address – text, required
+
+capacity – numeric, required
+
+menu – text, optional
+
+phone_number – text, optional
+
+price_per_guest – numeric, required
+
+
+== **Entity: Venue_Type**
+
+Explanation:
+The Venue_Type entity categorizes venues (e.g., restaurant, hall, outdoor space). It is separated to ensure data consistency and easy extensibility.
+
+
+**Candidate keys:**
+
+type_id – chosen as the primary key.
+
+
+**Attributes:**
+
+type_id – numeric, required
+
+type_name – text, required
+
+
+== **Entity: Venue_booking**
+
+Explanation:
+The Venue_booking entity represents reservations of venues for weddings. It captures scheduling and pricing information and ensures no booking conflicts occur.
+
+
+**Candidate keys:**
+
+booking_id – chosen as the primary key.
+
+
+**Attributes:**
+
+booking_id – numeric, required
+
+date – date, required
+
+start_time – time, required
+
+end_time – time, required
+
+status – text, required
+
+price – numeric, required
+
+
+== **Entity: Photographer**
+
+Explanation:
+The Photographer entity represents professional photographers available for weddings. It stores contact and pricing information to support booking and comparison.
+
+
+**Candidate keys:**
+
+photographer_id – chosen as the primary key.
+
+
+**Attributes:**
+
+photographer_id – numeric, required
+
+name – text, required
+
+email – text, required
+
+phone_number – text, required
+
+price_per_hour – numeric, required
+
+
+== **Entity: Photographer_booking**
+
+Explanation:
+This entity records bookings of photographers for specific weddings and time periods.
+
+
+**Candidate keys:**
+
+booking_id – chosen as the primary key.
+
+
+**Attributes:**
+
+booking_id – numeric, required
+
+date – date, required
+
+start_time – time, required
+
+end_time – time, required
+
+status – text, required
+
+
+== **Entity: Band**
+
+Explanation:
+The Band entity represents music performers available for weddings. It allows storage of genre, equipment, and pricing information.
+
+
+**Candidate keys:**
+
+band_id – chosen as the primary key.
+
+
+**Attributes:**
+
+band_id – numeric, required
+
+band_name – text, required
+
+genre – text, required
+
+equipment – text, optional
+
+phone_number – text, required
+
+price_per_hour – numeric, required
+
+
+== **Entity: Band_booking
+
+Explanation:
+The Band_booking entity represents reservations of bands for weddings, including timing and booking status.
+
+
+**Candidate keys:**
+
+booking_id – chosen as the primary key.
+
+
+**Attributes:**
+
+booking_id – numeric, required
+
+date – date, required
+
+start_time – time, required
+
+end_time – time, required
+
+status – text, required
+
+
+
+== **Entity: Church**
+
+Explanation:
+The Church entity represents religious locations where wedding ceremonies can take place.
+
+
+**Candidate keys:**
+
+church_id – chosen as the primary key.
+
+
+**Attributes:**
+
+church_id – numeric, required
+
+name – text, required
+
+location – text, required
+
+contact – text, required
+
+
+== **Entity: Church_booking**
+
+Explanation:
+The Church_booking entity records church reservations for wedding ceremonies.
+
+
+**Candidate keys:**
+
+booking_id – chosen as the primary key.
+
+
+**Attributes:**
+
+booking_id – numeric, required
+
+date – date, required
+
+start_time – time, required
+
+end_time – time, required
+
+status – text, required
+
+
+== **Entity: Priest**
+
+Explanation:
+The Priest entity represents clergy members who perform wedding ceremonies. It is modeled separately to allow assignment to church ceremonies.
+
+
+**Candidate keys:**
+
+priest_id – chosen as the primary key.
+
+
+**Attributes:**
+
+priest_id – numeric, required
+
+name – text, required
+
+contact – text, required
+
+
+
+== **Entity-Relationship Model History**
+
+*.01 – Initial version of the ER model