Movie Ticket Booking System

---

Overview

The Movie Ticket Booking System is a C++ console application designed for booking movie tickets and managing cinema operations. It offers functionality for users to search for movies, view showtimes, book seats, and allows administrators to manage movies, cinemas, halls, and shows, with robust notifications management.

---

Features

• Multiple Cinemas & Halls: Manage multiple cinemas, each with several halls.
• Movie Management:
  • Add new movies.
  • Update existing movies.
  • Delete movies.
• Show Management:
  • Add, update, and remove showtimes.
• Seat Selection & Pricing:
  • Silver, Gold, Platinum seat categories.
  • Individual seat booking and status management.
• Advanced Search:
  • Search movies by title, genre, language, or release date.
  • Display associated cinema, hall, and showtime details.
• Notifications System:
  • New movie releases, bookings, and cancellations notifications.
  • Notifications stored and marked as read after viewing.
• Admin Authentication:
  • Secure login (admin@gmail.com / manager4365).
  • Automatic data deletion after three failed attempts.

---

Prerequisites

• C++17 compiler (GCC/Clang/MSVC)
• CMake (3.15+)
• Git (for version control)

---

How to Build and Run

1. Clone Repository

git clone https://github.com/codingburgas/movie-ticket-booking-system-10th-grade-NVBalandin22.git
cd movie-ticket-booking-system

2. Build with CMake

cmake -S . -B build
cmake --build build

3. Run Application

cd build
./MovieBookingSystem # On Windows: MovieBookingSystem.exe

---

File Structure

.
├── data/
│   ├── data.txt (cinema and show data)
│   └── notifications.txt (notification data)
├── include/
│   ├── cinema.h
│   ├── functions.h
│   ├── movie.h
│   └── show.h
├── src/
│   ├── cinema.cpp
│   ├── functions.cpp
│   ├── main.cpp
│   ├── movie.cpp
│   └── show.cpp
├── CMakeLists.txt
└── README.md

---

Technologies Used

• C++17
• CMake
• Git & GitHub

---

Done by Nikita Balandin 10-V

---

Future Enhancements

• Implement graphical user interface.
• Switch data storage to database format.
• Add automated unit tests.
• Continuous Integration via GitHub Actions.