Changes between Version 4 and Version 5 of P3

Timestamp:

01/03/26 15:39:56 (2 weeks ago)

Author:

193284

Comment:

--

P3

@@ -4 +4 @@
 This phase demonstrates typical application scenarios for accessing the Wedding Planner database using SQL queries.
 The scenarios reflect real tasks such as creating weddings, managing events and guests, tracking attendance, and handling bookings of wedding services.
+
+== Actors / Roles
+
+* **Wedding Planner (User)**  
+  The main actor who creates and manages weddings, events, guests and bookings.
+
+* **Guest**  
+  A person invited to a wedding who can RSVP to events and attend them.
+
+* **Service Provider**  
+  External providers such as venues, bands, photographers, churches and registrars
+  whose services are booked for weddings.
 
 == Assumptions
@@ -27 +39 @@
 }}}
 
+=== Dialog Form (Scenario 2)
+
+1. User selects the option "Create new wedding".
+2. System displays a form for wedding details (date, budget, notes).
+3. User enters wedding data and submits the form.
+4. System validates the input.
+5. System creates a new wedding record in the database using SQL INSERT.
+6. System shows the wedding dashboard for the newly created wedding.
+
 == Scenario 3: Add events for a wedding
 Create wedding-related events such as ceremony and reception.
@@ -58 +79 @@
 (3, 'pending', 'guest', NULL, 103, 2);
 }}}
+
+=== Dialog Form (Scenario 5)
+
+1. User opens the guest list for a selected event.
+2. System displays invited guests and attendance options.
+3. User selects attendance status and optional table number.
+4. System stores the attendance data in the database.
+5. System confirms the update and refreshes the attendance overview.
 
 == Scenario 6: List all weddings for a specific user
@@ -134 +163 @@
 VALUES (1, '2026-06-20', '15:00:00', '21:00:00', 'confirmed', 4500.00, 1, 1);
 }}}
+
+=== Dialog Form (Scenario 12)
+
+1. User selects a wedding and opens the venue booking page.
+2. System displays available venues and date/time selection.
+3. User selects venue and desired time interval.
+4. System checks availability using SQL (no overlapping bookings).
+5. If available, system creates a venue booking record.
+6. System confirms the booking and shows booking details.
 
 == Scenario 13: Venue booking overview for a wedding
@@ -251 +289 @@
 
 == UX/UI Development Plan ==
+The UX/UI page flow is directly aligned with the SQL application scenarios described
+in this phase, where each user interaction corresponds to one or more SQL operations.
 
 This section guides the UX/UI designers on the structure, order, and responsibilities