| 3 | | Trac is a '''minimalistic''' approach to '''web-based''' management of |
| 4 | | '''software projects'''. Its goal is to simplify effective tracking and |
| 5 | | handling of software issues, enhancements and overall progress. |
| 6 | | |
| 7 | | All aspects of Trac have been designed with the single goal to |
| 8 | | '''help developers write great software''' while '''staying out of the way''' |
| 9 | | and imposing as little as possible on a team's established process and |
| 10 | | culture. |
| 11 | | |
| 12 | | As all Wiki pages, this page is editable, this means that you can |
| 13 | | modify the contents of this page simply by using your |
| 14 | | web-browser. Simply click on the "Edit this page" link at the bottom |
| 15 | | of the page. WikiFormatting will give you a detailed description of |
| 16 | | available Wiki formatting commands. |
| 17 | | |
| 18 | | "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created |
| 19 | | a new Trac environment, containing a default set of wiki pages and some sample |
| 20 | | data. This newly created environment also contains |
| 21 | | [wiki:TracGuide documentation] to help you get started with your project. |
| 22 | | |
| 23 | | You can use [wiki:TracAdmin trac-admin] to configure |
| 24 | | [http://trac.edgewall.org/ Trac] to better fit your project, especially in |
| 25 | | regard to ''components'', ''versions'' and ''milestones''. |
| | 3 | 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, wedding packages, service providers, and guest lists. It also includes booking modules for church ceremonies, registrar appointments, venue reservations, and vendor scheduling. The database stores availability slots, customer profiles, reservations, pricing information, and event details, allowing efficient planning without conflicts such as double-booking. |
| | 4 | 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, hiring services, and managing timelines. The system would support both clients and administrators, 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. |
| 40 | | For a complete list of local wiki pages, see TitleIndex. |
| | 13 | Jana Trpkovska 193284 |
| | 14 | |
| | 15 | |
| | 16 | Ivan Ivanovski 212093 |
| | 17 | |
| | 18 | |
| | 19 | Course: Databases in 2025/2026/Winter |
| | 20 | |
| | 21 | |
| | 22 | Under the supervision of: Prof. Dr. Vangel V. Ajanovski |
| | 23 | |
| | 24 | |
| | 25 | |
| | 26 | == Detailed description of the project |
| | 27 | |
| | 28 | 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. |
| | 29 | |
| | 30 | |
| | 31 | **The project solves several key problems:** |
| | 32 | |
| | 33 | -lack of centralized data between different wedding service providers |
| | 34 | |
| | 35 | |
| | 36 | |
| | 37 | -risk of double-booking venues, churches, registrars, or bands |
| | 38 | |
| | 39 | |
| | 40 | |
| | 41 | -inefficient manual communication between users(In this case Groom and Bride) and Venue, Band, Church and Register bookings. |
| | 42 | |
| | 43 | |
| | 44 | |
| | 45 | -inconsistent guest management and event tracking |
| | 46 | |
| | 47 | |
| | 48 | |
| | 49 | **Types of users include:** |
| | 50 | |
| | 51 | |
| | 52 | |
| | 53 | -wedding planners in this case Users(Groom or Bride, can be both) |
| | 54 | |
| | 55 | |
| | 56 | |
| | 57 | -service providers (bands, hotels, registrars) |
| | 58 | |
| | 59 | |
| | 60 | |
| | 61 | **Difference from similar systems:** |
| | 62 | 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. |
| | 63 | |
| | 64 | The final application would be primarily web-based, with the potential to extend to mobile. |
| | 65 | == |
