Create a class diagram for book my show

[kanmaytacker]

What?
Identify the various entities, their attributes, behaviour and relationships with other entities.

Why?

1. Helps identifying and documenting low level implementation
2. Removes uncertainty from actual implementation

How?
Fill out the worksheet here.

[ArvindGanur]

BookMyShow
-User
-Movie
-Theater
-Place

User

• Id
• Name
• Email
• Phno

Theater
-Name
-place
-NoOf-shows
-TypeOfSeats
-2Dor3D
-ShowTiming
-NoofScreening
Movie
-name
-Duration
-price
-reating

MovieNameDetails
-NamesOfAcotrs
-Role

TypeOfSeats
-Gold
-Diamond
-Platinum

PayMentGateWayEnum
-UPI
-creditcard
-OnlineBanking

[kanmaytacker]

A few improvements @ArvindGanur

1. You are missing a few entities like City, Seat, Shows.
2. You have a requirement to show the available seats. How will you achieve that?
3. Also you need track user bookings as well.

[hey-vishal]

i wasn't able to come up with whole it may have improvements

[kanmaytacker]

Great effort @hey-vishal.
A few things to add:

1. [MINOR] You are missing some secondary entities like payment, user, etc.
2. [MAJOR] How do you show the available and booked seats to the user?

[hey-vishal]

points noted... will do better next time... thanks @kanmaytacker

[shaileshexp]

[kanmaytacker]

Great work @shaileshexp.
You have all the entities. You might not need an extra booking entity since you have a ticket.
Something you have think about:
How do you show available and booked seats to the user?

[pramodpatil812]

@startuml
abstract class User {
long id
String name
}
class Customer
class Admin

class City {
int id
int name
Theatre[] theatres
}
class Theatre {
int id
String name
Hall[] halls
}
class Hall {
int id
String name
Seat[] seats
Show[] shows
}
class Seat {
int id
String number
SeatType type
}
enum SeatType {
GOLD
PLATINUM
SILVER
}
class Show {
int id
DateTime starttime
DateTime endtime
Movie movie
String language
ShowSeat[] showseats /'redundant information as we already have this information available in ShowSeat class'/
}
class Movie {
int id
String name
Genre[] genre
String[] languages
}
enum Genre {
HORROR
THRILLER
DRAMA
}
class ShowSeat {
Show show
Seat seat
SeatStatus seatStatus
}
enum SeatStatus {
AVAILABLE
BOOKED
}
class Ticket {
int id
DateTime bookingTime
Customer customer
double price
Show show
Hall hall
Seat[] bookedSeats
Payment[] payment /' multiple payments, if partial payments are allowed for a single ticket and if payment success happended after any failed payment '/
TicketStatus ticketStatus
}
enum TicketStatus {
BOOKED
CANCELLED
}
class Payment {
double amount
Ticket ticket
PaymentMode mode
PaymentStatus paymentStatus
}
enum PaymentMode {
UPI
CREDIT_CARD
NETBANKING
}
enum PaymentStatus {
SUCCESS
FAILED
}

/' Inheritance '/
Customer --|> User
Admin --|> User

/' Composition - City "is composed of" theatres. If City doesn't exists Theatre also can't exist '/
City *-- Theatre
Theatre *-- Hall
Hall *-- Seat
Hall *-- Show
@enduml

[venu123]

[ershivanikhandelwal]

[kanmaytacker]

Perfect @ershivanikhandelwal
You have all the entities you would need. You might not want separate child classes for Cash, UPI etc.

Something you have think about:
How do you show available and booked seats to the user?

[animesh799]

[vishwaraths]

[MauryaBrij]

[agarwalprerna643]

[aniketankalikar]

[nikhilreddykunta]

Class City
- String name

Class Theatre
    - String name
    - City city
    
Class Screen
    - String screenName
    - Theatre theatre
    - Movie movie
    - List<List<Seats>> seatLayout
    
Class Movie
    - String name
    - double rating
    - List<Category> category
    
enum Category{
}

Class Show
    - Timestamp time
    - Movie movie

Class Seat
    - SeatType seatType
    - BookingStatus bookingStatus
    
enum SeatType {
GOLD, PLATINUM, DIAMOND
}

enum BookingStatus{
AVAILABLE, BOOKED
}

Class Ticket
    - Screen screen
    - Movie movie
    - List<Seat> seats

Class Payment

Class Coupon
    - String code

Class Booking
    - Ticket ticket
    - Date date



   
  
    ...

[annant05]

[annant05]

classDiagram
class City{
id
name
}
class Theatre{
id
name
city_id
isOpen()
}
class Screen{
id
movies
isAvaliable()
}
class Movie{
name
timeslot_id
theatre_id
}
class User{
id
name
mobile
email
created_at
}
class Ticket{
seats
user_id
movie_id
created_at
payment_id
timeslot_id
}
class Seat{
SeatType
row
col
isAvaliable()
}
class SeatType{
name
}

class Payment{
    amount
    PaymentMode
}
class PaymentMode{
    name
}

Theatre <-- Ticket
Theatre <-- Seat  
Theatre <-- Movie
Theatre <-- Screen
Ticket <-- Seat
Ticket <-- Movie
Ticket <-- Screen
Ticket <-- User
Ticket <-- Payment
Payment <-- PaymentMode
Seat <-- SeatType
City <-- Theatre

[rahul-ydav]

classDiagram
class BookMyShow {
- AppName : String
- Owner : String
+ Cities: List
+ Search(City) City
+ Book()
}

class City {
- Name: String
- Theatres : List
}

class Theatre {
- Id : Long
- Name : String
- Screens: List
}

class Screen {
- Id : Long
- Name : String
- Seats : List
- TodayShows: List
+play(Board) BoardCell
}

class Seat{
- Id: Long
- SeatType : SeatType
- Price : float
}

class Movie {
- Name : String
- ScreenTime : Date
- Cast : String
- Shows: List
}

class Show {
- StartTime : Date
- AdTimes : Date
}

BookMyShow "1" --* "" City
City "1" -- "" Theatre
Theatre "1" -- "" Screen
Screen "1" -- "" Seat
Movie "1" -- "" Show
Screen "" --* "*" Show

[asknishant]

1.City

• id
• name

2.Threatre

• id
• name
• address
• screens

3.Screen

• id
• name
• seats

4.Seat

• id
• number
• row
• column

5.SeatInShow

• seatStatus
• show

SeatStatus(enum)
Booked, Empty, InProcess

6.Show

• id
• nam
• actors
• movie

7. Payment

• id
• PaymnetMode
• PaymentStatus

PaymentStatus(enum)
Cancelled, Done

8. Ticket

• id
• show
• seat
• theatre

[perfectprocrastinator]