Changes between Version 2 and Version 3 of P3

Timestamp:

01/03/26 14:15:23 (2 weeks ago)

Author:

193284

Comment:

--

P3

@@ -175 +175 @@
 These SQL scenarios demonstrate how the database supports the main wedding planning operations:
 user and wedding management, event scheduling, guest tracking, attendance recording, and venue bookings.
+
+
+
+
+== UX/UI Development Plan ==
+
+This section is intended to guide UX/UI designers on the sequence and contents of the web pages
+based on the current database design and application scenarios.
+
+=== General Guidelines ===
+* The UI should follow the database structure and SQL use cases listed in P3.
+* Each major user interaction (e.g., creating a wedding, adding guests, booking venues) should
+  correspond to a logical group of SQL queries and entities in the database.
+* Screens should be organized to match the real-world process flow: login → wedding creation →
+  event creation → guest management → attendance tracking → bookings → summaries/reports.
+
+=== Suggested Page Flow ===
+1. **User Login / Registration Page**
+   - Capture user credentials (User entity).
+   - Link to Wedding creation/dashboard once logged in.
+
+2. **Wedding Dashboard**
+   - List all weddings for the user.
+   - Options to create/edit/delete wedding records (Wedding entity).
+
+3. **Event Management**
+   - Page for adding, editing, and viewing events for selected wedding.
+   - Connects to Event entity.
+
+4. **Guest List and Attendance**
+   - Page to add/edit guest details (Guest entity).
+   - Multi-select or event-specific attendance (Attendance entity).
+   - Optional table assignment if applicable.
+
+5. **Bookings Page**
+   - Separate sections for:
+     * Venue booking (Venue & Venue_booking entities)
+     * Photographer booking (Photographer & Photographer_booking)
+     * Other service bookings
+   - Include date/time pickers and status fields.
+
+6. **Reports / Summary Pages**
+   - Show aggregated data such as guest count, attendance status,
+     booked services overview, and cost estimates.
+
+=== Interaction-to-SQL Mapping ===
+* For each user action, refer to specific SQL scenarios in P3:
+  - Wedding creation → `INSERT INTO Wedding`
+  - Adding guest → `INSERT INTO Guest`
+  - Recording attendance → `INSERT INTO Attendance`
+  - List events → `SELECT FROM Event WHERE wedding_id = ?`
+  - Booking venue → `INSERT INTO Venue_booking`
+  - etc.
+
+=== Design Notes ===
+* Use consistent navigation (e.g., top bar with links: Weddings | Events | Guests | Bookings).
+* Forms should validate required fields before submission (e.g., wedding date, event time).
+* Views for lists should support sorting/filtering/search (e.g., guests by name).
+
+== UX/UI Pages Checklist ==
+* Login / Registration
+* Wedding Dashboard
+* Event Management
+* Guest List + Attendance
+* Venue & Services Booking
+* Reports / Summary
+
+