Design a Movie Ticket Booking System: Entities and Use Cases

In this article, we will explore the design of a Movie Ticket Booking System, focusing on the essential entities and use cases that are crucial for Object-Oriented Design (OOD) interviews. This system is a common scenario that tests your understanding of OOD principles, design patterns, and system architecture.

Key Entities

When designing a movie ticket booking system, we need to identify the key entities that will interact within the system. Here are the primary entities:

1. Movie
   Represents a film that is available for booking. Attributes may include:

   • Title
   • Genre
   • Duration
   • Rating
   • Showtimes

2. Theater
   Represents the physical location where movies are shown. Attributes may include:

   • Name
   • Location
   • Number of screens
   • Facilities (e.g., parking, concessions)

3. Screen
   Represents a specific screen within a theater where a movie is shown. Attributes may include:

   • Screen number
   • Seating capacity
   • Screen type (e.g., IMAX, 3D)

4. Seat
   Represents an individual seat in a screen. Attributes may include:

   • Seat number
   • Availability status (available, booked)
   • Price

5. User
   Represents a customer who books tickets. Attributes may include:

   • User ID
   • Name
   • Email
   • Payment information

6. Booking
   Represents a ticket booking made by a user. Attributes may include:

   • Booking ID
   • User ID
   • Movie ID
   • Screen ID
   • Seat numbers
   • Booking time
   • Total price

Use Cases

Understanding the use cases is essential for defining how users will interact with the system. Here are some common use cases for a movie ticket booking system:

1. Search for Movies

   • Users can search for movies based on criteria such as title, genre, or showtime.

2. View Movie Details

   • Users can view detailed information about a selected movie, including its synopsis, cast, and available showtimes.

3. Select a Theater and Screen

   • Users can choose a theater and a specific screen for the movie they wish to watch.

4. Select Seats

   • Users can view the seating layout and select available seats for their booking.

5. Make a Booking

   • Users can confirm their seat selection and proceed to payment to complete the booking.

6. View Booking History

   • Users can view their past bookings and details of each transaction.

7. Cancel a Booking

   • Users can cancel their bookings within a specified time frame and receive a refund if applicable.

Conclusion

Designing a Movie Ticket Booking System involves identifying key entities and understanding the use cases that drive user interactions. This exercise not only tests your ability to apply OOD principles but also your understanding of system design and user experience. By mastering such scenarios, you will be better prepared for technical interviews in top tech companies.