| | 1 | == Project Overview == |
| | 2 | |
| | 3 | The Room Reservation System is a database-oriented project developed as part of the Databases course. The goal of the project is to design and implement a relational database that supports the reservation of rooms such as classrooms, offices, and meeting spaces. The system allows users to reserve rooms for specific dates and time intervals while ensuring that overlapping reservations are not permitted. |
| | 4 | |
| | 5 | The project primarily focuses on database design and data management rather than on the development of complex user interfaces. Emphasis is placed on correctness, consistency, and integrity of the stored data. |
| | 6 | |
| | 7 | == Problem Statement == |
| | 8 | |
| | 9 | In many organizations, room reservations are often handled manually or using loosely structured tools, which may result in scheduling conflicts, double bookings, and inefficient resource usage. Without a centralized database, it is difficult to accurately track room availability and reservation history. |
| | 10 | |
| | 11 | This project aims to address these issues by providing a structured and reliable database solution that enforces data integrity and supports efficient reservation management. |
| | 12 | |
| | 13 | == System Users and Roles == |
| | 14 | |
| | 15 | The system supports the following user roles: |
| | 16 | |
| | 17 | * '''Regular Users''' – Users who can search for available rooms and create reservations for specific dates and time intervals. |
| | 18 | * '''Administrators''' – Users responsible for managing rooms and overseeing reservations, including adding, modifying, and canceling reservations. |
| | 19 | |
| | 20 | Each role has clearly defined permissions to ensure controlled access to system functionality. |
| | 21 | |
| | 22 | == Main Functionalities == |
| | 23 | |
| | 24 | The main functionalities of the Room Reservation System include: |
| | 25 | |
| | 26 | * Management of room information such as capacity and location. |
| | 27 | * Searching for available rooms based on date and time. |
| | 28 | * Creating reservations while preventing scheduling conflicts. |
| | 29 | * Viewing and managing existing reservations. |
| | 30 | * Administrative control over rooms and reservations. |
| | 31 | |
| | 32 | == Project Scope == |
| | 33 | |
| | 34 | The scope of this project is limited to the design and implementation of the database layer and database-driven application logic. The project does not aim to deliver a production-ready application, but rather to demonstrate correct database modeling, normalization, constraint definition, and SQL usage. |
| | 35 | |
| | 36 | == Technologies and Tools == |
| | 37 | |
| | 38 | The following technologies and tools will be used in the implementation of the project: |
| | 39 | |
| | 40 | * PostgreSQL for relational database management. |
| | 41 | * SQL for data definition and manipulation. |
| | 42 | * Trac Wiki for project documentation. |
| | 43 | * A simple prototype application (e.g., command-line interface) to demonstrate database interaction. |
| | 44 | |
| | 45 | == Project Team == |
| | 46 | |
| | 47 | This project is developed as an individual project by: |
| | 48 | |
| | 49 | * Nikola Sarafimov |
