Use Case Diagram for Online Movie Ticket Booking System

UML Use Case diagram for Online Movie Ticket Booking System is shown below. The various participants of the same are detailed below:-

Actors:- Registered User, Visitor, Admin

The corresponding use cases for these actors are:-

• Registered User: Choose Movie, Select Time And Venue, Select Seat, Select Ticket Type,Child, Adult, Make Payment By Credit/Debit Card, Confirm Transaction, Cancel Ticket, Get Refund


• Visitor : Get Registered, Check Movie Data


• Admin : Login, Insert Movie Records, Update Movie Records, Delete Movie Records

Here we have some dependencies also like Registered User Login <<include>>Choose Movie, Select Time And Venue, Select Seat, Select Ticket Type, Make Payment By Credit/Debit Card. If a user gets login to book ticket then he has to perform all these operations in order to get ticket booked. Further, Make Payment by Debit/Credit Card <<include>> Confirm Transaction as after making payment it is necessary to confirm that transaction is completed.

Again, Login <<extend>> Cancel Ticket as user may or may not want to cancel booked ticket. Cancel Ticket <<includes>> Get Refund as if the tickets are cancelled then, refund has to be made.

Login of Admin <<includes>> Add Movie Records and <<extend>> Update movie Records and Delete Movie Records.

The Use Case UML diagram for Online Movie Ticket Booking System is shown below:-