Tribhuvan University

Faculty of Humanities and Social Sciences

“ONLINE MOVIE TICKET BOOKING SYSTEM”

A PROJECT REPORT

Submitted to:
Department of Computer Application
Kathmandu College of Central State
Soalteemode, Kathmandu

In partial fulfillment of the requirements for the Bachelors in Computer Application

Submitted by:
Jenish Tamang (6-2-528-6-2021)
Manjit Shrestha ( 6-2-528–10-2021)
March 2024

Under the Supervision of

Er. Kiran Sharma
 Tribhuvan University
Faculty of Humanities and Social Sciences
Kathmandu College of Central State

Supervisor’s Recommendation

I hereby recommend that this project prepared under my supervision by Jenish Tamang
and Manjit Shrestha entitled “Online Movie Ticket Booking System” in partial
fulfillment of the requirements for the degree of Bachelor of Computer Application is
recommended for the final evaluation.

_______________
SIGNATURE
[Link] Sharma

SUPERVISOR
BCA Department
Kathmandu College of Central State

I
 Tribhuvan University
Faculty of Humanities and Social Sciences
Kathmandu College of Central State

LETTER OF APPROVAL

This is to certify that this project prepared by Jenish Tamang and Manjit Shrestha
entitled “Online Movie Ticket Booking System” in partial fulfillment of the
requirements for the degree of Bachelor of Computer Application has been evaluated. In
our opinion it is satisfactory in the scope and quality as a project fir the required degree.

_______________ _______________
[Link] Sharma Mrs. Ambika Deoja Kunwar
Supervisor
Head of Department
Department of BCA
Department of BCA
Kathmandu College of Central State
Kathmandu College of Central State
Soalteemode, Kalimati, Kathmandu 44600
Soalteemode, Kalimati, Kathmandu 44600

_______________ _______________
Internal Examiner External Examiner

II
 ABSTRACT
In the entertainment industry, movie theaters need a strong online presence. This project
develops an Online Movie Ticket Booking System with HTML, CSS, JS for the front-end
and PHP, MYSQL for the back-end. It offers users an easy way to browse movies and
buy tickets online. The system has a user-friendly front-end and a back-end for cinema
owners to manage the website efficiently. Documentation covers design, analysis,
security, payments, and more. The focus is on creating a versatile and cost-effective
system for movie enthusiasts and cinema owners.

Keywords: Online Movie Ticket Booking System, Web application, user-friendly, Cinema
Hall

III
 ACKNOWLEDGEMENT
I extend my heartfelt gratitude to several individuals whose invaluable contributions and
guidance have played a pivotal role in the successful organization of this project. I am
sincerely thankful for their kind opinions, suggestions, and appropriate guidelines,
without which this endeavor would not have been possible.

Foremost, I express my deepest appreciation to my supervisor, Mr. Kiran Sharma for

granting me the opportunity to undertake this remarkable project on the topic of "Online
Movie Ticket Booking System” Website using PHP." His guidance has been instrumental
in enhancing my knowledge, and I am particularly grateful for his continuous feedback
and encouragement throughout the project. Without his unwavering support, the
successful completion of this project would not have been achievable, and I have gained
profound insights under his mentorship.

We would also like to express our deepest appreciation to, Mrs. Ambika Deoja Kunwar,
head of department, Kathmandu College of Central State, for her constant motivation,
support and for providing us with a suitable working environment.

Lastly, but certainly not least, I extend my thanks to all those who have consistently
offered encouragement and assistance, helping me navigate the challenges encountered
during the project's completion. Their support has been invaluable, and I am grateful for
their unwavering commitment.

Jenish Tamang (6-2-528-6-2021)

Manjit Shrestha ( 6-2-528–10-2021)

IV
 Table of Contents

SUPERVISOR'S RECOMENDATION............................................................................i
LETTER OF APPROVAL................................................................................................ii
ABSTRACT.......................................................................................................................iii
ACKNOWLEDGEMENT................................................................................................iv
LIST OF FIGURES...........................................................................................................v
LIST OF TABLES............................................................................................................vi
LIST OF ABBREVIATION............................................................................................vii
CHAPTER 1: INTRODUCTION.....................................................................................1
1.1 Introduction.............................................................................................................1
1.2 Problem Statement..................................................................................................2
1.3 Objectives................................................................................................................3
1.4 Scope and Limitations.............................................................................................3
1.4.1 Scope..............................................................................................................3
1.4.2 Limitations.....................................................................................................3
1.5 Software Requirements..........................................................................................3
1.6 Report Organization...............................................................................................4
CHAPTER 2: BACKGROUND STUDY AND LITERATURE REVIEW...............5
2.1 Background Study...................................................................................................5
2.2 Literature Review..................................................................................................6
CHAPTER 3: SYSTEM ANALYSIS AND DESIGN.....................................................7
3.1 System Analysis......................................................................................................7
3.1.1 Requirement Analysis....................................................................................8
[Link] Functional Requirements........................................................................8
[Link].1 Use-Case Diagram...........................................................................8
[Link] Non-Functional Requirements................................................................9
3.1.2 Feasibility Analysis......................................................................................10
3.1.3 Data Modeling.............................................................................................11
3.1.4 Process Modeling.........................................................................................12
3.2 System Design.......................................................................................................15
3.2.1 Architectural Design....................................................................................15
3.2.2 System Flowchart........................................................................................16
3.2.3 Database Design Schema.............................................................................19
 3.2.4 Interface Design (Interface Structure Diagrams).........................................20
CHAPTER 4: IMPLEMENTATION AND TESTING................................................21
4.1 Implementation.....................................................................................................21
4.1.1 Tools Used...................................................................................................21
[Link] Front-End Tools....................................................................................21
[Link] Back-End tools......................................................................................22
[Link] Database................................................................................................22
[Link] Server....................................................................................................22
[Link] Documentation Tools............................................................................23
4.1.2 Implementation Details of Modules............................................................23
4.2 Testing...................................................................................................................23
4.2.1 Test Cases for Unit Testing.........................................................................23
CHAPTER 5: COLCLUSION AND FUTURE RECOMMENDATION...................28
5.1 Lesson Learnt/Outcome........................................................................................28
5.2 Conclusion.............................................................................................................28
5.3 Future Recommendation.......................................................................................28
 LIST OF FIGURES

Figure 3.1:Waterfall Model..................................................................................................7

Figure 3.2:Use Case Diagram for Online Movie Ticket......................................................9
Figure 3.3:Gantt Chart of Online Movie Ticket................................................................11
Figure 3.4:ER Diagram of Online Movie Ticket..............................................................12
Figure 3.5:Context diagram of Online Movie Ticket.........................................................13
Figure 3.6:Level-1 DFD for Admin...................................................................................14
Figure 3.7:Level-1 DFD for users......................................................................................14
Figure 3.8:Architectural Design.........................................................................................15
Figure 3.9:Flowchart for Admin........................................................................................17
Figure 3.10:Flowchart for User..........................................................................................18
Figure 3.10:Home Page of Online Movie Ticket...............................................................20
Figure 3.11:Register Page of Online Movie Ticket...........................................................20
Figure 3.12:Log In Page of Online Movie Ticket..............................................................21
Figure 3.14:Movie Details of Online Movie Ticket...........................................................21
 LIST OF TABLES

Table 4.1 :Test table for Admin Login...............................................................................25

Table 4.2:Test Case for User Registration.........................................................................26
Table 4.3:Test Table for User Login..................................................................................27
Table 4.4 :Test table for User Logout................................................................................27
Table 4.5: Test table for Admin Logout.............................................................................28
Table 4.6:Test Table for CommingSoon Movies..............................................................28
Table 4.7 :Test Table for Now Showing Movies...............................................................29
Table 4.8 :Test Case for Selecting Movies and Seat..........................................................29

VI
 LIST OF ABBREVIATION

API Application Programming Interface

CSS Cascading Style Sheets
DFD Data Flow Diagram
ER Entity Relationship
GANTT Generalized Activity Normalization Time Table
HTML Hyper Text Markup Language
JS JavaScript
MySQL My Structured Query Language
PHP Hypertext Preprocessor
UI User Interface

VII
 Chapter 1: Introduction
1.1 Introduction of Proposed Project
Welcome to a world where getting tickets for your favorite movie is super easy! Our
proposed project, the Online Movie Ticket Booking System, is all about making the
process simple and quick. Picture this: just a few clicks, and you've got your movie
seats reserved. That's the vision we're working towards – a hassle-free way for
everyone who loves movies to book their tickets in advance.

The heart of our project is to create a platform that's really easy to use. We want it to
be like your friendly movie buddy, helping you pick and reserve seats effortlessly. No
more waiting in those long lines, and no need to worry about missing out on a show
because it's sold out. With our system, you can relax and focus on enjoying the movie
– that's the goal!
Think of our project as a solution to the common challenges people face when going
to the movies. Long queues and the fear of missing out on tickets will be a thing of
the past. We're putting the power in your hands, giving you the freedom to plan your
movie night without stress. The Movie Ticket Booking System is here to make sure
you have a smooth and enjoyable experience from the moment you decide to catch a
film.

So, come join us on this exciting journey! Together, we're making going to the
movies a easy task. Your feedback and support will be crucial as we work towards
creating a user-friendly platform that truly enhances your cinematic adventures. Get
ready for a future where booking movie tickets is as simple as a smile – quick, easy,
and always ready to brighten up your day at the movies!

In summary, the “Online Movie Ticket Booking System” aims to revolutionize the
way people reserve seats for their favorite films. By creating a user-friendly platform,
the project seeks to eliminate the hassles of long queues and the fear of missing out on
tickets. With just a few clicks, users can effortlessly plan their movie nights, ensuring
a smooth and enjoyable experience from start to finish. The project envisions a future
where booking movie tickets is as simple as a smile, offering convenience and ease to
all movie enthusiasts.

1
1.1 Problem Statement
In the context of Nepal, particularly in rural areas, movie enthusiasts encounter
significant hurdles accessing advanced technology and online services, resulting in
difficulties purchasing movie tickets online and often enduring long queues to obtain
physical tickets at cinema venues. Additionally, concerns about online payment
security further complicate the process, emphasizing the necessity for tailored
solutions to enhance accessibility and ease of use for all audiences. The
implementation of the Online Movie Ticket Booking System could serve as a pivotal
step towards democratizing access to entertainment and cultural experiences, ensuring
that every individual, regardless of their geographical location or technological
proficiency, can enjoy a seamless and secure ticket booking experience, thereby
enriching their movie-going ventures in Nepal.
 Access of advanced technology and online services may be limited in rural areas.
 Sometimes,paying for things online can be a bit tricky.
 We’re aware that spending money online can sometimes feel like it’s a lot.
 Have to wait in queue for a long to get a movie ticket physically.

1.2 Objectives
The project's main goal is to develop a user-friendly online movie ticket booking
platform for individuals in Nepal, simplifying the ticket booking process and
enhancing accessibility. It aims to ensure affordability, making movie experiences
accessible to all segments of the population. Additionally, the platform seeks to
maximize outreach, reaching as many people as possible across Nepal. Crucially, it
prioritizes system functionality and reliability across different regions of Nepal to
guarantee universal access. Through intuitive design and affordability, the project
aims to revolutionize the movie ticket booking experience in Nepal, catering to the
diverse needs of movie enthusiasts.
 Make booking movie tickets online a breeze for people in Nepal.
 Ensure the process is super simple and easy for everyone to use.
 Keep it affordable,so going to the movies doesn’t cost too much.
 Reach out to as many people as possible,so everyone can enjoy the convenience.
 Guarantee that the system works well for everyone.

2
1.4 Scope and Limitations
The scope and limitations of a project help to define its boundaries and provide clarity
on what the project aims to achieve and what it may not encompass.

1.4.1. Scope :

The scope for our project are as follows:

a. Save time
b. Easy to update
c. Reduce burden of queue in line physically
d. You can get all kind of movies as you want to do from every parts of Nepal

1.4.2. Limitations

The limitations of Online Movie Ticket Booking System are given below:
a. Limited support for various movie ticket purchase formats.
b. Feedback may lack detailed explanations on movie availability.
c. No offline access for booking tickets, restricting users in areas with poor internet
connectivity.

1.5. Software Requirements

The software requirements for our project are as follows:
a. JAVASCRIPT
b. MYSQL
c. Html, CSS, PHP

3
1.6. Report Organization
The report is structured into three chapters, covering all stages of application design
and development for our Online Movie Ticket Booking System. In the opening
chapter, we introduce our system, spotlighting the challenges encountered by movie
enthusiast, including long queues and ticket unavailability. Our primary objectives
involve facilitating a seamless booking experience, offering a diverse range of movie
options, and ensuring swift ticket reservations. Additionally, we delineate the system's
scope and limitations, providing readers with a comprehensive understanding of its
intended purpose and constraints.
Moving to the second chapter, we explore the background through a literature review
on existing online Online Movie Ticket Booking System. This helps us learn from
previous efforts and identify effective features in similar applications.

The third chapter focuses on the analysis and design of our system, involving a
detailed requirement analysis, feasibility studies, and the creation of visual
representations like entity relationship and data flow diagrams.

4
 Chapter 2: Background Study and Literature Review
2.1 Background Study
In recent years, the online movie ticket booking industry has undergone a remarkable
transformation, propelled by the rapid advancement of digital technology. Major
players like BookMyShow and QFX Cinemas have led the charge, revolutionizing the
way movie tickets are purchased by offering intuitive and user-friendly online
platforms. This shift towards digital booking has not only streamlined the ticketing
process but has also provided busy individuals with a convenient way to plan their
movie outings from the comfort of their homes or on the go.

With just a few clicks, users can access a wide array of movie listings, select preferred
showtimes, and reserve seats, eliminating the need to wait in long queues at the
cinema. Furthermore, the availability of recurring payment options has added an extra
layer of convenience, allowing users to set up automated payments for their movie
tickets, ensuring a hassle-free experience with each booking. Throughout the booking
process, users are prompted to provide billing and payment details, with transactions
swiftly processed online. Upon completion, users receive instant email notifications
confirming their bookings, providing them with peace of mind and assurance that
their movie tickets are secured.

This transition towards digital platforms underscores a broader trend in consumer

behavior, where efficiency and convenience are paramount considerations. As
consumers increasingly prioritize seamless experiences in their interactions with
businesses, the online movie ticket booking industry is well-positioned to continue its
growth trajectory, offering unparalleled convenience and accessibility to movie
enthusiasts worldwide.

5
2.2 Literature Review
Our research into the online movie ticketing landscape revealed a significant gap in
quality platforms catering to this domain, limiting users' access to convenient services
and raising concerns about transaction security. Existing platforms often fail to
provide satisfactory user experiences, with usability issues and a lack of essential
features leaving movie enthusiasts frustrated.

Customization and Personalization:

Audiences increasingly seek personalized movie experiences tailored to their

preferences and viewing habits. The incorporation of customization features in online
movie ticket booking systems, such as seat selection, genre preferences, and special
offers, enhances customer engagement and loyalty by catering to individual
preferences.[1]

Customer Relationship Management:

Building and nurturing customer relationships are integral to fostering loyalty and
repeat business in the entertainment industry. Leveraging customer data analysis,
personalized recommendations, and loyalty programs within online ticket booking
systems fosters stronger connections with audiences, driving engagement and
retention[2].

Payment Processing:

Seamless and secure online payment processing is essential for a frictionless ticket
booking experience. Integrating reliable payment gateways, ensuring robust data
security measures, and offering diverse payment options cater to customer
preferences, enhancing the overall booking process and reducing transactional
friction.[3]

Ticket Inventory Management:

Effective management of ticket inventory is paramount for theaters to meet audience

demands while minimizing losses due to unsold tickets or overbooking. Digital
inventory management systems offer real-time tracking, automated ticket allocation,

6
and predictive analytics, enhancing inventory optimization and streamlining ticket
distribution processes.[4]

7
 Chapter 3 Methodology
Given the project's dynamic requirements, evolving documentation, limited time, and
the team's solid grasp of agile methodologies, the Agile approach is the chosen
method for constructing the website. This iterative method allows for flexible and
incremental progression through the project phases, ensuring that the team can adapt
to changes and continuously improve the product based on feedback. The use of Agile
methodology aligns with the project's need for adaptability, providing a responsive
and collaborative framework for development.%3CmxGraphModel%3E%3Croot%3E
%3CmxCell%20id%3D%220%22%2F%3E%3CmxCell%20id%3D
%221%22%20parent%3D%220%22%2F%3E%3CmxCell%20id%3D
%222%22%20style%3D%22edgeStyle%3DorthogonalEdgeStyle%3Brounded
%3D0%3BorthogonalLoop%3D1%3BjettySize%3Dauto%3Bhtml%3D1%3B
%22%20edge%3D%221%22%20target%3D%223%22%20parent%3D%221%22%3E
%3CmxGeometry%20relative%3D%221%22%20as%3D%22geometry%22%3E
%3CmxPoint%20x%3D%22240%22%20y%3D%22120%22%20as%3D
%22targetPoint%22%2F%3E%3CmxPoint%20x%3D%22190%22%20y%3D
%2270%22%20as%3D%22sourcePoint%22%2F%3E%3CArray%20as%3D
%22points%22%3E%3CmxPoint%20x%3D%22241%22%20y%3D%2270%22%2F
%3E%3C%2FArray%3E%3C%2FmxGeometry%3E%3C%2FmxCell%3E
%3CmxCell%20id%3D%223%22%20value%3D%22System%20Design
%22%20style%3D%22rounded%3D0%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3B
%22%20vertex%3D%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x
%3D%22150%22%20y%3D%22130%22%20width%3D%22150%22%20height%3D
%2240%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell
%20id%3D%224%22%20value%3D%22Implementation%22%20style%3D
%22rounded%3D0%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3B%22%20vertex
%3D%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x%3D
%22275%22%20y%3D%22210%22%20width%3D%22150%22%20height%3D
%2240%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell
%20id%3D%225%22%20style%3D%22edgeStyle%3DorthogonalEdgeStyle
%3Brounded%3D0%3BorthogonalLoop%3D1%3BjettySize%3Dauto%3Bhtml
%3D1%3BexitX%3D1%3BexitY%3D0.5%3BexitDx%3D0%3BexitDy

8
%3D0%3BentryX%3D0.691%3BentryY%3D-0.09%3BentryDx%3D0%3BentryDy
%3D0%3BentryPerimeter%3D0%3B%22%20edge%3D%221%22%20source%3D
%226%22%20target%3D%227%22%20parent%3D%221%22%3E%3CmxGeometry
%20relative%3D%221%22%20as%3D%22geometry%22%3E%3CmxPoint%20x
%3D%22620%22%20y%3D%22370%22%20as%3D%22targetPoint%22%2F%3E
%3C%2FmxGeometry%3E%3C%2FmxCell%3E%3CmxCell%20id%3D
%226%22%20value%3D%22Testing%22%20style%3D%22rounded
%3D0%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3B%22%20vertex%3D
%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x%3D
%22400%22%20y%3D%22290%22%20width%3D%22150%22%20height%3D
%2240%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell
%20id%3D%227%22%20value%3D%22Deployment%22%20style%3D%22rounded
%3D0%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3B%22%20vertex%3D
%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x%3D
%22520%22%20y%3D%22380%22%20width%3D%22150%22%20height%3D
%2240%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell
%20id%3D%228%22%20value%3D%22maintenance%22%20style%3D%22rounded
%3D0%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3B%22%20vertex%3D
%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x%3D
%22660%22%20y%3D%22460%22%20width%3D%22150%22%20height%3D
%2240%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell
%20id%3D%229%22%20style%3D%22edgeStyle%3DorthogonalEdgeStyle
%3Brounded%3D0%3BorthogonalLoop%3D1%3BjettySize%3Dauto%3Bhtml
%3D1%3BexitX%3D1%3BexitY%3D0.5%3BexitDx%3D0%3BexitDy
%3D0%3BentryX%3D0.585%3BentryY%3D0.06%3BentryDx%3D0%3BentryDy
%3D0%3BentryPerimeter%3D0%3B%22%20edge%3D%221%22%20source%3D
%223%22%20target%3D%224%22%20parent%3D%221%22%3E%3CmxGeometry
%20relative%3D%221%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell
%3E%3CmxCell%20id%3D%2210%22%20style%3D%22edgeStyle
%3DorthogonalEdgeStyle%3Brounded%3D0%3BorthogonalLoop
%3D1%3BjettySize%3Dauto%3Bhtml%3D1%3BexitX%3D1%3BexitY
%3D0.5%3BexitDx%3D0%3BexitDy%3D0%3BentryX%3D0.579%3BentryY
%3D0.04%3BentryDx%3D0%3BentryDy%3D0%3BentryPerimeter%3D0%3B
%22%20edge%3D%221%22%20source%3D%224%22%20target%3D
9
%226%22%20parent%3D%221%22%3E%3CmxGeometry%20relative%3D
%221%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell
%20id%3D%2211%22%20style%3D%22edgeStyle%3DorthogonalEdgeStyle
%3Brounded%3D0%3BorthogonalLoop%3D1%3BjettySize%3Dauto%3Bhtml
%3D1%3BexitX%3D1%3BexitY%3D0.5%3BexitDx%3D0%3BexitDy
%3D0%3BentryX%3D0.637%3BentryY%3D-0.03%3BentryDx%3D0%3BentryDy
%3D0%3BentryPerimeter%3D0%3B%22%20edge%3D%221%22%20source%3D
%227%22%20target%3D%228%22%20parent%3D%221%22%3E%3CmxGeometry
%20relative%3D%221%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell
%3E%3CmxCell%20id%3D%2212%22%20value%3D%22%22%20style%3D
%22endArrow%3Dnone%3Bhtml%3D1%3Brounded%3D0%3B%22%20edge%3D
%221%22%20parent%3D%221%22%3E%3CmxGeometry%20width%3D
%2250%22%20height%3D%2250%22%20relative%3D%221%22%20as%3D
%22geometry%22%3E%3CmxPoint%20x%3D%22110%22%20y%3D
%22480%22%20as%3D%22sourcePoint%22%2F%3E%3CmxPoint%20x%3D
%22110%22%20y%3D%2290%22%20as%3D%22targetPoint%22%2F%3E
%3CArray%20as%3D%22points%22%2F%3E%3C%2FmxGeometry%3E%3C
%2FmxCell%3E%3CmxCell%20id%3D%2213%22%20value%3D%22%22%20style
%3D%22endArrow%3Dnone%3Bhtml%3D1%3Brounded%3D0%3B%22%20edge
%3D%221%22%20parent%3D%221%22%3E%3CmxGeometry%20width%3D
%2250%22%20height%3D%2250%22%20relative%3D%221%22%20as%3D
%22geometry%22%3E%3CmxPoint%20x%3D%22110%22%20y%3D
%22480%22%20as%3D%22sourcePoint%22%2F%3E%3CmxPoint%20x%3D
%22660%22%20y%3D%22480.29998779296875%22%20as%3D%22targetPoint
%22%2F%3E%3C%2FmxGeometry%3E%3C%2FmxCell%3E%3CmxCell%20id
%3D%2214%22%20value%3D%22%22%20style%3D%22endArrow%3Dnone
%3Bhtml%3D1%3Brounded%3D0%3B%22%20edge%3D%221%22%20parent%3D
%221%22%3E%3CmxGeometry%20width%3D%2250%22%20height%3D
%2250%22%20relative%3D%221%22%20as%3D%22geometry%22%3E
%3CmxPoint%20x%3D%22230%22%20y%3D%22480%22%20as%3D
%22sourcePoint%22%2F%3E%3CmxPoint%20x%3D%22230%22%20y%3D
%22170%22%20as%3D%22targetPoint%22%2F%3E%3C%2FmxGeometry%3E
%3C%2FmxCell%3E%3CmxCell%20id%3D%2215%22%20value%3D
%22%22%20style%3D%22endArrow%3Dnone%3Bhtml%3D1%3Brounded
10
%3D0%3B%22%20edge%3D%221%22%20parent%3D%221%22%3E
%3CmxGeometry%20width%3D%2250%22%20height%3D%2250%22%20relative
%3D%221%22%20as%3D%22geometry%22%3E%3CmxPoint%20x%3D
%22350%22%20y%3D%22480%22%20as%3D%22sourcePoint%22%2F%3E
%3CmxPoint%20x%3D%22350%22%20y%3D%22250%22%20as%3D
%22targetPoint%22%2F%3E%3C%2FmxGeometry%3E%3C%2FmxCell%3E
%3CmxCell%20id%3D%2216%22%20value%3D%22%22%20style%3D
%22endArrow%3Dnone%3Bhtml%3D1%3Brounded%3D0%3B%22%20edge%3D
%221%22%20parent%3D%221%22%3E%3CmxGeometry%20width%3D
%2250%22%20height%3D%2250%22%20relative%3D%221%22%20as%3D
%22geometry%22%3E%3CmxPoint%20x%3D%22480%22%20y%3D
%22480%22%20as%3D%22sourcePoint%22%2F%3E%3CmxPoint%20x%3D
%22480%22%20y%3D%22330%22%20as%3D%22targetPoint%22%2F%3E%3C
%2FmxGeometry%3E%3C%2FmxCell%3E%3CmxCell%20id%3D
%2217%22%20value%3D%22%22%20style%3D%22endArrow%3Dnone%3Bhtml
%3D1%3Brounded%3D0%3B%22%20edge%3D%221%22%20parent%3D
%221%22%3E%3CmxGeometry%20width%3D%2250%22%20height%3D
%2250%22%20relative%3D%221%22%20as%3D%22geometry%22%3E
%3CmxPoint%20x%3D%22600%22%20y%3D%22480%22%20as%3D
%22sourcePoint%22%2F%3E%3CmxPoint%20x%3D%22600%22%20y%3D
%22420%22%20as%3D%22targetPoint%22%2F%3E%3C%2FmxGeometry%3E
%3C%2FmxCell%3E%3C%2Froot%3E%3C%2FmxGraphMode

3.1 System Analysis

The requirements of our projects are as follows:
a. Study of Existing System : Evaluate current online movie ticket systems for user
feedback and limitations to inform the development of an enhanced platform.
b. Requirements Collection : Collaborate with stakeholders, cinema operators, and
prospective users to gather diverse and detailed requirements for the development
of the online movie ticket booking system.

11
Fig.3.1 Waterfall Model

12
3.1.1. Requirement Analysis
Identifying and understanding user needs and system specifications to guide the
development process effectively.
[Link]. Functional requirements
Functional requirements are product features or functions that developers must
implement to enable users to accomplish their tasks. They specify the specific
functionalities and capabilities that a system must possess to fulfill the needs and
objectives of its users. These requirements define what the system should do and how
it should behave in response to different inputs or events. Functional requirements
typically describe the system's features, behavior, and interactions with users and
other system components. The functional requirements of our project are as follows:
 Allows administrators to create and manage movie listings, update showtimes and
theaters, and set ticket prices, discounts, and promotions.
 Enables users to search for movies, select showtimes and seating preferences,
make secure online payments, and receive instant booking confirmation.
 Includes mechanisms for users to provide feedback on their booking experience,
and customer support channels such as FAQs, live chat support, and email
assistance.
 Ensures the system is accessible to users with disabilities and supports multiple
languages and currencies to accommodate diverse user demographics.
[Link].1. Use-case Diagram
The Online Movie Ticket System involves two key actors: the admin and the users.
The admin functions as the system's overseer, managing user accounts, movie listings,
bookings, and database maintenance. Conversely, users interact with the system to
book movie tickets, browse available films, select showtime, and complete bookings.
They can also access features such as viewing booking history and updating personal
information. User registration entails providing an email and password, while the
admin accesses the system using per-defined credentials stored securely in the
database. Overall, the system aims to deliver a seamless booking experience for users
while providing efficient management capabilities for the admin.

13
 Fig:Use-Case Diagram

[Link] Non-functional requirements

i. The system should feature an intuitive and user-friendly interface, ensuring ease
of use for all users, thereby enhancing the overall user experience.
ii. The system should respond promptly to user actions and efficiently handle
multiple concurrent users, ensuring optimal performance without degradation
even during peak usage periods.
iii. The system should demonstrate high reliability by minimizing system failures
and maintaining data integrity, thereby ensuring a seamless and trustworthy
ticket booking experience for users.

14
iv. The system should be scalable to accommodate a growing number of users,
movie listings, and booking requests without compromising performance,
ensuring a seamless ticket booking experience even as demand increases.

3.1.2 Feasibility Analysis

A feasibility study assesses the operational, technical and economic aspects of this
project. Various types of feasibility study is performed in order to develop the system
successfully.

i. Technical Feasibility

Technical feasibility considers the technical requirements of Online Movie Ticket

Booking System. The technical requirements are then compared to the technical
capability of the organization. This project is feasible on technical remarks as it can
run on any machines supporting Windows and Internet services and works on the best
software and hardware that had been used while designing the system so it would be
feasible in all technical terms of feasibility. The main tools and technologies to be
used in this system to make this project more feasible are:

Hardware Requirements: A laptop with 8 GB RAM, RYZEN 5 processor with

RADEON graphics and 256 GB SSD

Technologies: PHP, HTML, CSS, JavaScript

Software Requirements: Visual Studio Code, XAMPP Server, MS Word

ii. Operational Feasibility

Operational feasibility assesses how effectively a proposed system addresses

identified problems and opportunities, and whether it meets the requirements
identified during the scope definition and requirements analysis phases of system
development. The Online Movie Ticket Booking System is operationally feasible as it
is designed to be user-friendly and easy to operate, requiring only basic computer and
internet knowledge. The system's intuitive user interface makes it accessible to users
with minimal training, and it satisfies all the requirements identified during the
development process. Admins find the system easy to use, contributing to its
successful implementation and operation.

15
iii. Economic Feasibility

Economic Feasibility: Evaluating the economic feasibility of the project is essential to

determine its financial viability. The proposed Online Movie Ticket Booking System
is deemed feasible and economically viable based on the pre-assumed cost of system
development. Costs associated with the system are classified according to the phase in
which they occur, with system development costs being one-time expenses that will
not recur after project completion.

iv. Schedule Feasibility

The system which we had developed is completed within the scheduled time and did
not exceed the scheduled time. For this schedule, project planning is carried out by the
Gantt chart. A Gantt chart is one of the most popular and useful ways of showing
activities (tasks or events) displayed against time. It is used to show tasks or the
activities performed in contradiction to time as it is one of the graphical tools.

Figure :Gantt Chart of Online Movie Ticket Booking System

16
3.1.3 Data Modeling

Data modeling plays a pivotal role in the development of the Online Movie Ticket
Booking System as it delineates the structure and relationships of the database. The
creation of an entity-relationship (ER) diagram visually represents the system's
entities, including users, movies, theaters, bookings, and payments, along with their
associated attributes. The ER diagram illustrates the connections between these
entities through relationships, such as users making bookings, movies being shown in
theaters, and payments being linked to specific bookings. This diagram offers a
comprehensive view of the data organization and serves as a roadmap for database
design, ensuring efficient storage and retrieval of information within the system.

Fig3.4:ER Diagram for Online Movie Ticket

17
3.1.4. Process Modeling

Process modeling entails visually representing business processes or workflows. The

0-level Data Flow Diagram (DFD) provided below offers a high-level overview of the
processes and data flows within the Online Movie Ticket Booking System. This
diagram delineates the major components and their interactions, facilitating an
understanding of the overall flow of information in the system. The 0-level DFD aids
in visualizing key

processes like user registration and ticket booking, along with their associations with
entities such as users and administrators. By analyzing this diagram, insights into the
fundamental operations and data flows of the Online Movie Ticket Booking System
can be gained. Furthermore, the first-level DFD illustrates how the system is
subdivided into subsystems, each managing specific data flows to or from external
agents. These subsystems collectively provide all functionalities of the Online Movie
Ticket Booking System. Additionally, the first-level DFD identifies internal data
stores for both administrators and users, showcasing data flow between various parts
of the system. This detailed breakdown offers a more granular understanding of the
components depicted in the 0-level DFD, enhancing comprehension of the system's
architecture and operation

Figure 3.5:Context Diagram of Online Movie Ticket

18
Figure 3.1:Level-1 DFD for Admin

Figure 3.7:Level-1 DFD for Users

19
3.2 System Design
The System Design section meticulously outlines the detailed design of the Online Movie
Ticket Booking System. This phase is dedicated to translating requirements into a
meticulously structured and efficient system. The design prioritizes seamless
functionality, user-friendliness, security, and scalability. This section accentuates crucial
design aspects, including system architecture, database schema, and user interface. The
introduction furnishes an overview of the design goals, target audience, design
principles/methodologies employed, and any unique considerations pivotal for the
project's success.

3.2.1 Architectural Design

The architectural design for the Online Movie Ticket Booking System follows a three-tier
architecture consisting of the presentation layer, business logic layer, and data storage
layer.

Fig 3.8 Architectural Design

20
3.2.2 System Flowchart

The flowchart below illustrates the process flow of the Online Movie Ticket Booking
System. Users and administrators log in to the system, with users required to register if
they are not already registered. Upon successful login, users and administrators are
redirected to their respective dashboards. Administrators have access to functionalities
such as user management, exam management, and test analysis, while users can take
tests and view their results.

21
Figure 3.8: Flowchart for Users

22
Figure 3.2: Flowchart for Admin

23
3.2.3 Database Design Schemas

In our project, we're talking about how we organize the database that stores all our data.
Having a good setup for this database is super important because it helps us keep
everything organized and working smoothly. We call our database 'mtbs' for 'Movie
Ticket Booking System.'

Inside this database, we've set up several tables, kind of like spreadsheets, each with its
own job to do. There are seven of these tables. Think of each table like a different
category of information, such as movies, users, bookings, payments, and so on.

Each table has its own unique identifier called the 'id.' This helps us keep track of things.
If one table needs to refer to something in another table, it uses this 'id' like a special
code. We call this a 'foreign key.'

To show how these tables are connected, we draw lines between them on a diagram. This
helps us see how different pieces of information relate to each other, like how a booking
might be linked to a user or a movie.

24
3.2.4 Interface Design (Interface Structure Diagrams)

For the online movie ticket booking system, we've prioritized a user-friendly
interface. Our design emphasizes simplicity and clarity, ensuring easy navigation and
intuitive placement of buttons, forms, and menus. We've crafted the interface using
HTML, CSS, SASS, JavaScript, and PHP to create an attractive and responsive user
experience.

Figure 3.11: Homepage of Online Movie Ticket Booking

Figure 3.12: Log In Page of Online Movie Ticket Booking

25
 Figure 3.13: Register page of Online Movie Ticket Booking

Figure 3.14: Movie Details of Online Movie Ticket Booking

26
 CHAPTER 4: IMPLEMENTATION AND TESTING
4.1 Implementation
The implementation phase involves the conversion of the well-defined system design
into a fully functioning application. It encompasses writing the programming code,
creating databases, designing user interfaces, and integrating various functionalities to
provide a seamless user experience. This section provides an overview of the
technical aspects of the development process, including the languages, frameworks,
and tools used to build the presentation layer, business layer, and data layer. The
chapter aims to highlight the successful realization of the project's objectives and the
strategies employed to overcome challenges during development.

4.1.1 Tools Used

The various system tools that have been used in developing both the front-end and
back-end of the project are being discussed in this section.
[Link] Front-End Tools
 HTML
HTML serves as the backbone of the system, providing the essential structure for web
pages. With HTML, I've defined headers, footers, and sections to display movie
listings, showtimes, and booking forms. This ensures that users can easily navigate
through the site and find the information they need.
 CSS
CSS has been instrumental in enhancing the visual appeal of the interface. By
defining styles for various elements, such as fonts, colors, and layout, I've created a
cohesive and aesthetically pleasing design. CSS also enables responsive design,
allowing the booking system to adapt seamlessly to different devices and screen sizes.
 JavaScript
JavaScript brings dynamic functionality to the front end, making the user experience
more interactive and intuitive. Through JavaScript, I've implemented features like
real-time seat availability updates, form validations, and interactive elements such as
dropdown menus and modal dialogs. This ensures that users can easily select their
preferred movies, seats, and showtimes without any hassle.

27
[Link] Back End tools
 PHP
In my movie ticket booking project, PHP seamlessly interacts with the Apache server
to process user inputs and manage the flow of data between the front end and the
MySQL database. This ensures that user requests are handled efficiently and that the
necessary information is retrieved from or stored in the database as needed.
[Link] Database
 MYSQL
In my movie ticket booking project, MySQL serves as the backend database
management system, storing and retrieving crucial information like movie details,
showtimes, seat availability, and user bookings. This ensures that all essential data is
securely stored and readily accessible for efficient processing and retrieval when
needed.
[Link] Server
 Apache Server
In my movie ticket booking project, the Apache server ensures seamless
communication between the client-side interface and the server-side scripts. This
facilitates smooth data exchange and dynamic content generation, guaranteeing that
users can interact with the system effortlessly and receive timely updates and
responses as they navigate through the booking process.
[Link] Documentation Tools
 MS Office

This is used for writing and editing the documentation of ‘Online Movie Ticket
Booking System’.

 [Link]
This is used to generate diagrams for system analysis and design of Online Movie
Ticket Booking System . All the diagrams were drawn using this tool in order to
save time since all components are available with drag and drop functions.

28
4.1.2 Implementation Details of Modules

The proposed system consists of following modules:

 Administrator Module
This module handles all administrative tasks for the online movie ticket booking
system. Administrators can manage movies, theaters, and notices, as well as configure
system settings. They can update movie details, add theaters, and publish notices
about screenings or schedule changes. Additionally, administrators can analyze ticket
sales and movie screenings to make informed decisions. This module ensures smooth
operation of the system.
 User Module
This module handles user authentication for the online movie ticket system, enabling
functionalities like registration, login, and logout. Users can also view movie results
and notices through this module. They can select specific movie screenings by
choosing their preferred movie and class to view details and book tickets.

4.2 Testing
On the basis of software requirement specification document, testing was performed
to investigate and validate the behavior of a fully integrated software product. Before
deploying an application or website, it must be thoroughly tested. Some of the types
of testing that we did are described below:

4.2.1 Test Cases for Unit Testing

Unit testing is performed to ensure the individual units or components of the software,
such as functions, methods, or classes, work correctly and produce the expected
output. It aims to validate that each isolated unit behaves as intended and is free from
defects. We can catch bugs early in the development process, making it easier to fix
issues and prevent them from propagating to other parts of the systems.
The unit tests that were performed in this project are tabulated below:

29
 Table 4.1:Test Case for Admin Login

Test_Id Test Case Test Data Expected Actual Pass

Description Result Result /Fail
1 Admin Admin Username: Display As Pass
enters a admin@[Link] message expected
wrong **invalid
password details**
Admin Admin Username: Display As
enters a message expected Pass
[Link]
2 wrong **Invalid
Password: 123778
password details**
Admin Admin Username:
3 enters admin@[Link] Logged into As Pass
correct Password: 123 admin page expected
username
and
password

30
 Table 4.2: Test Case for User Registration

Test_Id Test Case Test Data Expected Actual Pass

Description Result Result /Fail
1 User enters Email: Proceed to As Pass
a valid admin@[Link] next step expected
email
User enters Email: Display As
an invalid jenish@[Link] message expected Pass
2 email **Invalid
details**
User enters Password: 123 Display
3 mismatched Confirm Password: message As Pass
passwords password321 passwords do expected
not match

User enters Email: Registration

4 all valid admin@[Link] successful As Pass
registration Password: 123 expected
details Confirm Password:
123

31
 Table 4.3:Test Case for User Login

Test_Id Test Case Test Data Expected Actual Pass

Description Result Result /Fail
1 User Admin Username: Display As Pass
enters a admin@[Link] message expected
wrong **invalid
username details**
User Admin Username: Display As
enters a admin@[Link] message expected Pass
2 wrong Password: 858585 **Invalid
password details**
User Admin Username:
3 enters admin@[Link] Logged into As Pass
correct Password: 123 admin page expected
username
and
password

Table 4.4:Test Case for User Logout

Test_Id Test Case Test Data Expected Actual Pass/Fail

Description Result Result
1 Click on to Click on to Logout and As
Logout Logout navigate to expecte Pass
Login Page d

32
 Table 4.5:Test Case for Admin Logout

Test_Id Test Case Test Data Expected Actual Pass/Fail

Description Result Result
1 Click on to Click on to Logout and As
Logout Logout navigate to expecte Pass
Login Page d

Table 4.6:Test case for Coming Soon Movies

33
Test_Id Test Case Test Data Expected Actual Pass/
Description Result Result Fail
Click on Display
In the "Coming "Coming Soon list of As Pass
Soon Movies" Movies" coming expected
1 section, navigate "Coming Soon soon
to view coming Movies" movies
soon movies.

In the "Coming Click on a Display As

2 Soon Movies" specific movie detailed expected Pass
section, click on informatio
a specific movie specific movie n about the
to view details. selected
specific movie movie

specific movie

specific movie

specific movie

specific movie

specific
movieClickvie

Table 4.7:Test case for Now Showing Movies

34
Test_Id Test Case Test Data Expected Actual Pass/
Description Result Result Fail
In the "Now Click on "Now Display
Playing Movies" Playing Movies" list of now As Pass
section, navigate playing expected
1 to view now Soon Movies" movies
playing movies.

In the "Now Click on a Display As

2 Playing Movies" specific movie detailed expected Pass
section, click on informatio
a specific movie information n about the
to view details. about the selected
selected movie movie

information
about the
selected movie

specific movie

specific movie

specific movie

specific movie

specific movie

specific
movieClickvie

35
Table 4.8:Test Case for Selecting Movies and Seat.

36
Test_Id Test Case Test Data Expected Actual Pass/Fail
Description Result Result
1 In the "Select Click on a Display
Movies" section, movie available As Pass
click on a movie showtimes expected
from the list. and theater
options for
the selected
movie.
2 In the "Select Select Display As
Movies" section, showtime: 7:00 available expected Pass
choose a PM, Theater: seats for the
showtime and selected
theater. showtime
and theater
3 In the "Select Select seats: Display
Seats" section, R1S1, R1S2, selected As
choose desired RAS3 seats and expected Pass
seats for booking proceed to
payment

37
 CHAPTER 5: CONCLUSION AND FUTURE
RECOMMENDATION
5.1 Lesson Learnt / Outcome

Every project makes us to learn and gain the knowledge in different aspects. From our
project, we have learned lots of problem-solving skills and learn things like improving
technical skills, understanding full software development cycle, database design and
management, problem solving, troubleshooting, documentation and communication.
Here are some potential lessons learned and outcomes of our project:
 Improves Technical Skill
During the development of our project, we likely enhanced our technical skills in
programming languages (e.g., PHP), database management (e.g., MySQL), web
development, and working with frameworks and libraries. These skills can be
valuable for future projects and career opportunities
 Understanding full software development life cycle
We gained practical experience in the entire software development cycle, from
requirements gathering and planning to implementation, testing, and deployment. This
understanding can help us to become more efficient and effective in future
development projects.
 Database Design and Management
Developing a web application with a database backend requires careful database
design and management. Because of this project, we likely learned how to create and
manage database tables, set up relationships between tables, and handle data
efficiently.
 Problem Solving and Troubleshooting
Throughout the development process, we likely encountered various challenges and
issues. Our ability to troubleshoot and find solutions to these problems has likely
improved.
 Documentation and Communication
Throughout the development process, we likely encountered various challenges and
issues. We likely learned how to document the report as well as increase our
communication skills.

38
5.2 Conclusion
In conclusion, completing this project has been a rewarding and enriching experience.
Through the process of designing and developing the Student result management
system application, I have honed my technical skills, gained a deeper understanding
of software development, and acquired valuable insights into user experience and
project management. The project's success in providing a platform for users to view
results, manage student and view Notice has reinforced the importance of thorough
testing. Moving forward, I aim to build on the lessons learned and continue to explore
new opportunities to apply my knowledge in real-world scenarios. Overall, this
project has been a significant stepping stone in my journey as a developer, and I look
forward to applying these skills in future endeavors.

5.3 Future Recommendation

In considering future recommendations, our focus remains on innovation, security,
scalability, and customer-centricity. By staying at the forefront of emerging
technologies and adapting to evolving market trends, our Online Movie Ticket
Booking System will continue to offer a cutting-edge solution, ensuring the sustained
success of our business.

We suggest exploring avenues for enhanced scalability, including the potential

transition to a cloud-based infrastructure. This shift would accommodate the growing
demands of our expanding customer base and ensure seamless performance even
during peak periods.

Remaining customer-centric is paramount. We must actively seek feedback from

users, leveraging data analytics to drive iterative improvements and deliver an
exceptional user experience consistently.

Additionally, forging partnerships and collaborations with suppliers can bolster our
supply chain, ensuring reliable inventory management and promoting sustainable
practices across the board. This proactive approach will not only benefit our business
operations but also reinforce our commitment to environmental and social
responsibility.

39
 References
[1] T. Spangler, "Online Movie Ticket Booking System," Essaysause, 2010. [Online].
Available: [Link]. [Accessed: Mar. 15, 2024].

[2] T. Tuluk and D. S. Valli, "Movie Ticket Booking System," Procedia-Social and
Behavioral Sciences, vol. 2, no. 4, pp. 13-16, Jan. 2012. [Accessed: May. 5, 2024].

[3] B. Yadav, "Tickets and Payment," Essaysuse, 2014. [Online]. Available:

[Link]. [Accessed: Feb. 20, 2024].

[4] S. Brock, "Seat Planning," Helpinneed, 2009. [Online]. Available:

[Link]. [Accessed: Apr. 5, 2024].

40
 Appendix
1. Home page

2. Coming Soon

41
3. Now Showing

4. Booking

42
5. Contact Us

43