online ticket booking

1. ONLINE MOVIE TICKET
BOOKING SYSTEM

2. AGENDA
 Abstract
 Literature Survey
 Proposed Mini Project “ONLINE MOVIE TICKET
BOOKING MANAGEMENT SYSTEM”.
 High level Architecture
 Hardware and Software Requirement
 Modular Decomposition of OMTBS
 Admin Module
 User Module
 INPUT & OUTPUT Screen shots
 Conclusion with Future Enhancement
 References

3.  The main purpose of our online ticket booking system is to provide an
alternate and convenient way for a customer to buy cinema tickets.
 It is an automatic system basically made for providing the customers an
anytime and anywhere service for booking the seat in the cinema hall and to
gather information about the movies online
 The user can easily be able to know about the movies released and then make
the choice.
 Admin can modify by insert and delete data such as movie description, movie
schedule which will update the related webpage
ABSTRACT

4. LITERATURE SURVEY
 In 1969, Sweeting [5] speculated that perhaps theatres could benefit from
computerized ticketing system, similar to what airlines at the time had started to adopt.
 Langley [3] in 1980 suggested that computer-based ticket system was only feasible for
large theatre operations However, with today’s comparatively low hardware cost, the
computer has become affordable and is common in most offices
 Book My Show was started in 1999, and since then it is one of the most famous online
movie booking system. The web site mostly gained its popularity between the years
2006-2010

5.  Previously it was manual, customers have to go to the counters and stand in long
queue for ticket booking
 Time consuming
 More complex and inefficient
 Dependent of employee
 Insecurity
EXISTING SYSTEM DISADVANTAGES

6. OMTBS PROPOSED SYSTEM
 The proposed system can overcome all the limitations of existing system
 It reduces manual work and it is user friendly
 Customers can easily view details of the movie and can book tickets through
online payment without coming to theatre.
 Administrator is responsible for maintaining right information about the
movies, seat availability and many more things.

7. SOFTWARE REQUIREMENTS
PROJECT NAME OMTBS SYSTEM
LANGUAGE USED PHP5, PHP7.x
DATABASE MariaDB (HEIDI SQL), LOCAL STORAGE
USER INTERACE
DESIGN
HTML, CSS, JAVASCRIPT
WEB BROWSER GOOGLE CHROME, MICROSOFT
SOFTWARE XAMPP
HARDWARE REQUIREMENTS
Processor: x86 or x64
RAM: 512 MB (minimum), 1 GB (recommended)
Hard disk: up to 200 MB of available space may be required

8. OMTBS HIGH LEVEL ARCHITECTURE DIAGRAM

9. DECOMPOSITION OF MODULES
1.ADMIN
 This is the main module where it consist of multiple forms for admin to manage
movies such as Add, Edit, Delete and can manage show such as change in Show
Name and Show Time.
 Admin have to login with their register username and password. After login
admin can have multiple features.
 Admin can modify by insert and delete data such as movie description, movie
schedule which will update to the related webpage (webpage are dynamic page,
changing according to the data in database) and admin can check the statistic
information from the system.

10. Fig 1.2: Use case diagram for Admin module
ACTOR INVOLVED: 1. ADMIN

11. INPUT SCREENSHOTS
After login admin can add, alter or delete movie description. To add a movie
description admin have to enter movie name, cast information, small information
about movie and he has to select image for that movie. Finally, he has to enter
YouTube trailer link for that movie.
Fig 1.3: Input form for the admin to add movie description

12. After adding movie description , it will be added in movie list
Fig 1.5: Output form after adding movie description
OUTPUT SCREESHOT

13. Admin can add shows for the theatre. For that he has to choose movie name and
he has to choose the screen. Finally, he has to manage schedule such as he has to choose
the release date and the show time such as first show, second show or all shows.
Fig 1.4: Input form for the admin to add shows
INPUT SCREESHOT

14. Fig 1.7: Output form of shows added
OUTPUT SCREESHOT

15. MODULE -2
2.USERS
 In this module, The user can first Register by entering their Personal details.
 After Signup user have to login with their register username and password
 The user see all information like Upcoming Movies details, in advance ticket
booking and Theater details.
 The Users will search for the movie.
 User can book ticket by selecting theatre, show time and number of tickets.
After that he can proceed for payment

16. Fig 1.8: Use case diagram for User module
ACTORs INVOLVED: 1. MEMBER 2. VISITOR

17. User have to choose movie and then he has to select theatre, show time and number
of tickets
Fig 1.10: Show availability page and Book show
INPUT SCREESHOT

18. After booking movie ,the details of booking is added in booking history
The user can check the details in this page.
OUTPUT SCREESHOT

19. TESTING - ONLINE MOVIE TICKET BOOKING MANAGEMENT SYSTEM
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and code generation.
TESTING OBJECTIVES
To ensure that during operation the system will perform as per specification.
 To make sure that system meets the user requirements during operation
 To make sure that during the operation, incorrect input, processing and
output will be detected
 To see that when correct inputs are fed to the system the outputs are correct
 To verify that the controls incorporated in the same system as intended
 Testing is a process of executing a program with the intent of finding an error
 A good test case is one that has a high probability of finding an as yet
undiscovered error

20.  During the development of this system, unit testing was carried out by the
developers on each of the result processing modules.
 Results from the integration test of this project were satisfactory; although,
exhaustive debugging may not be realistic in a very large and complex program.
 The system was tested on different browsers and operating systems such as
Opera, Google Chrome, Safari, Mozilla Firefox, Microsoft Internet explorer,
Windows and Linux.
 The result of the test was satisfactory.
TESTING

21. CONCLUSION:
In our project with this cinema ticketing system cinema companies can satisfy
comfortable facilities to their customers. The relationship between cinema manager,
employee, and customer satisfies a good communication to complete ticketing process.
With this platform we developed, we are hoping to reduce time wasting, avoid
misunderstandings, provide easy data flow, customer pleasure, and less hard work. We
believe that we have accomplished our goals and satisfied with the code we developed
FUTURE WORK:
We think that not a single project is ever considered as complete forever because our
mind is always thinking something new and our necessities also are growing day by
day. We always want something more than what we have. Our application also, if you
see at the first glance than you find it to be complete but we want to make it still
mature and fully automatic. Some of the expansions which we have thought of are:
• We want to improve our home page, as it is the main things which attracts all
users.
• Payment facility for UPI user.

22. REFERENCES
[1] Carmack Celentano, S & Marshall, K 1998, Theatre Management, Players Press, Inc,
USA
[2] Collins, T 2003, How Theatre Managers Manage, The Scarecrow Press, Inc.
[3] Langley, S 1980, Theatre Management in America Principles and Practice, Drama Book
Publishers, New York.
[4] Reid, F 1983, Theatre Administration, A&C Black (Publishers) Ltd, London.
[5] Schneider, Re & Ford, MJ 1993, The Well-Run Theatre, Drama Book Publishers, New
York
[6] https://www.academia.edu
[7] https://www.bookmyshow.com
[8] https://www.fandango.com
[9] https://www.w3schools.com/

23. THANK
YOU!!!