| 4 | | 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. |
| | 5 | '''Course:''' Databases (Winter Semester 2025/2026) |
| | 6 | '''Started:''' December 2025 |
| | 7 | '''Under the supervision of:''' Prof. Dr. Vangel V. Ajanovski |
| 6 | | The database stores availability time slots, user profiles, reservations, pricing information, and event details, enabling efficient planning while preventing conflicts such as double-booking of resources. If fully developed as a complete application, the system would provide a unified platform where users can plan an entire wedding from a single place by selecting venues, booking ceremonies, managing guests, and organizing event timelines. |
| | 9 | == Project team |
| | 10 | * Marija Taseska (213087) – Coordinator |
| | 11 | * Slobodanka Pistolova (211171) |
| | 12 | * Jana Trpkovska (193284) |
| | 13 | * Ivan Ivanovski (212093) |
| 8 | | This project focuses on demonstrating proper database modeling techniques, including ER diagrams, constraints, normalization, relational design, and the implementation of real-world business rules relevant to wedding planning systems. |
| 9 | | |
| 10 | | **Project team:** |
| 11 | | |
| 12 | | - Marija Taseska 213087 – Coordinator |
| 13 | | - Slobodanka Pistolova 211171 |
| 14 | | - Jana Trpkovska 193284 |
| 15 | | - Ivan Ivanovski 212093 |
| 16 | | |
| 17 | | **Course**: Databases (Winter Semester 2025/2026) |
| 18 | | **Started**: December 2025 |
| 19 | | |
| 20 | | **Under the supervision of**: Prof. Dr. Vangel V. Ajanovski |
| 21 | | |
| 22 | | == Detailed description of the project |
| 23 | | |
| 24 | | 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. |
| 25 | | |
| 26 | | The system addresses several key challenges commonly encountered in wedding planning: |
| 27 | | |
| 28 | | - Lack of centralized data shared between different wedding service providers |
| 29 | | - Risk of double-booking venues, churches, registrars, bands, or photographers |
| 30 | | - Inefficient manual communication between users (bride and groom) and service providers |
| 31 | | - Inconsistent guest management and event attendance tracking |
| 32 | | |
| 33 | | **Types of users include:** |
| 34 | | |
| 35 | | - Wedding planners or end users (bride and groom) |
| 36 | | - Service providers (venues, bands, photographers, churches, registrars) |
| 37 | | |
| 38 | | **Difference from similar systems:** |
| 39 | | 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. |
| | 15 | == Short project description |
| | 16 | Wedding Planner Management System is a database-centered project that supports the organization, booking, and coordination of wedding services (venues, ceremonies, bands, photographers, guests, RSVPs). |
| | 17 | The system ensures structured storage of reservations and schedules, preventing conflicts such as double-booking. |
| 44 | | || P0 || [[https://develop.finki.ukim.mk/projects/wedding_planner2025|Project definition]] || Completed || |
| 45 | | || P1 || [[ERModel|Conceptual design – ER Diagram & data requirements]] || Submitted for review || |
| 46 | | || P2 || [[P2|Logical and physical design – Database creation (DDL)]] || Submitted for review || |
| 47 | | || P3 || [[P3|Application design – Use cases and SQL scenarios]] || Submitted for review || |
| 48 | | || P4 || [[P4|Application prototype – Backend and database]] || Backend and database prototype completed. |
| 49 | | || P5 || [[P5|Advanced database queries and reports]] || Not started || |
| 50 | | || P6 || [[P6|Normalization and design improvements]] || Not started || |
| 51 | | || P7 || [[P7|Advanced application development]] || Not started || |
| 52 | | || P8 || [[P8]] || Not started || |
| 53 | | || P9 || [[P9]] || Not started || |
| | 22 | || P0 || [wiki:P0 Project definition] || {{{#!html <span style="color:green; font-weight:bold;">Completed</span> }}} || |
| | 23 | || P1 || [wiki:ERModel Conceptual design – ER Diagram & data requirements] || {{{#!html <span style="color:green; font-weight:bold;">Completed</span> }}} || |
| | 24 | || P2 || [wiki:P2 Logical and physical design – Database creation (DDL)] || {{{#!html <span style="color:green; font-weight:bold;">Completed</span> }}} || |
| | 25 | || P3 || [wiki:P3 Application design – Use cases and SQL scenarios] || {{{#!html <span style="color:orange; font-weight:bold;">Started</span> }}} || |
| | 26 | || P4 || [wiki:P4 Application prototype – Backend and database] || {{{#!html <span style="color:gray; font-weight:bold;">Not started</span> }}} || |
| | 27 | || P5 || [wiki:P5 Advanced database queries and reports] || {{{#!html <span style="color:gray; font-weight:bold;">Not started</span> }}} || |
| | 28 | || P6 || [wiki:P6 Normalization and design improvements] || {{{#!html <span style="color:gray; font-weight:bold;">Not started</span> }}} || |
| | 29 | || P7 || [wiki:P7 Advanced application development] || {{{#!html <span style="color:gray; font-weight:bold;">Not started</span> }}} || |
| | 30 | || P8 || [wiki:P8 Advanced application development (Transactions, Pooling)] || {{{#!html <span style="color:gray; font-weight:bold;">Not started</span> }}} || |
| | 31 | || P9 || [wiki:P9 Other topics (Performance, Security, ...)] || {{{#!html <span style="color:gray; font-weight:bold;">Not started</span> }}} || |
