| 6 | | The Wedding Planner Management System is a database designed to support the organization, booking, and coordination of all services involved in planning a wedding event. The system manages structured data about venues, hotels, churches, registrars, music bands, and guest lists. It also includes booking modules for church ceremonies, registrar appointments and venue reservations. The database stores availability slots, customer profiles, reservations, pricing information, and event details, allowing efficient planning without conflicts such as double-booking. |
| 7 | | If fully developed as a complete project, it would become a platform enabling users to plan entire weddings from a single place: selecting venues, booking ceremonies, adding guests and managing timelines. The system would support the user, offering real-time availability, automated verification of bookings, and centralized data management. This project aims to demonstrate correct database modeling, ER diagrams, constraints, normalization, and relational design suitable for real-world wedding planning applications. |
| | 5 | The Wedding Planner Management System is a database-centered project designed to support the organization, booking, and coordination of all services involved in planning a wedding event. The system manages structured data related to venues, hotels, churches, registrars, music bands, photographers, and guest lists. It also includes booking modules for church ceremonies, registrar appointments, venue reservations, and additional service providers. |
| 36 | | The database and the future project are intended for a wedding planning that manages multiple users, weddings, vendors, and services simultaneously. Every user before their wedding, needs a centralized and reliable system to store information, schedule events, and avoid conflicts between bookings from other users. |
| | 25 | The database and the future application are intended to support wedding planning scenarios involving multiple users, weddings, vendors, and services operating simultaneously. Each user planning a wedding requires a centralized and reliable system to store information, schedule events, and avoid conflicts caused by overlapping bookings made by different users. |
| 39 | | **The project solves several key problems:** |
| 40 | | |
| 41 | | -lack of centralized data between different wedding service providers |
| 42 | | |
| 43 | | |
| 44 | | |
| 45 | | -risk of double-booking venues, churches, registrars, or bands |
| 46 | | |
| 47 | | |
| 48 | | |
| 49 | | -inefficient manual communication between users(In this case Groom and Bride) and Venue, Band, Church and Register bookings. |
| 50 | | |
| 51 | | |
| 52 | | |
| 53 | | -inconsistent guest management and event tracking |
| 54 | | |
| 55 | | |
| | 29 | - Lack of centralized data shared between different wedding service providers |
| | 30 | - Risk of double-booking venues, churches, registrars, bands, or photographers |
| | 31 | - Inefficient manual communication between users (bride and groom) and service providers |
| | 32 | - Inconsistent guest management and event attendance tracking |
| 60 | | |
| 61 | | -wedding planners in this case Users(Groom or Bride, can be both) |
| 62 | | |
| 63 | | |
| 64 | | |
| 65 | | -service providers (bands, hotels, registrars) |
| 66 | | |
| 67 | | |
| 68 | | |
| 69 | | **Difference from similar systems:** |
| 70 | | While existing wedding planner tools focus mostly on budgeting or design, this solution focuses on a full relational database with real booking constraints, availability management, and integration of ceremony scheduling. |
| 71 | | |
| 72 | | The final application would be primarily web-based, with the potential to extend to mobile. |
| 73 | | == |
| 74 | | |
| 75 | | |
| 76 | | |
| | 39 | **Difference from similar systems:** |
| | 40 | While many existing wedding planner tools focus primarily on budgeting or visual design, this solution emphasizes a robust relational database structure with enforced booking constraints, real-time availability checks, and integrated ceremony scheduling. The final application is envisioned as a web-based system, with the possibility of future mobile extension. |
| 113 | | |
| | 44 | || '''Phase''' || '''Phase name''' || '''Status''' || |
| | 45 | || P0 || [[https://develop.finki.ukim.mk/projects/wedding_planner2025|Project definition]] || Completed || |
| | 46 | || P1 || [[ERModel|Conceptual design – ER Diagram & data requirements]] || Submitted for review || |
| | 47 | || P2 || [[P2|Logical and physical design – Database creation (DDL)]] || Submitted for review || |
| | 48 | || P3 || [[P3|Application design – Use cases and SQL scenarios]] || Submitted for review || |
| | 49 | || P4 || [[P4|Application prototype – Backend and database]] || Backend and database prototype completed. |
| | 50 | UX/UI prototype is in progress and will be integrated soon. || |
| | 51 | || P5 || [[P5|Advanced database queries and reports]] || Not started || |
| | 52 | || P6 || [[P6|Normalization and design improvements]] || Not started || |
| | 53 | || P7 || [[P7|Advanced application development]] || Not started || |
| | 54 | || P8 || [[P8]] || Not started || |
| | 55 | || P9 || [[P9]] || Not started || |
