Vous êtes sur la page 1sur 49

Chapter 1: INTRODUCTION

Project title: Online Cinema Ticket Booking System

1.1 Statement of project:

This project is aimed to provide the customers facility to book tickets for cinema halls
online, through which they can book tickets anytime, anywhere.

E-ticket system is basically made for providing the customer 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.

In this project, we will illustrate our system by providing DFD (Data FLOW Diagrams)
on some functions. And we will also provide some process description and data
dictionary.
Admin can use the system to insert and delete data (e.g. film description, time table)
which will update the webpage (webpage are dynamic page, changing according to the
data in database). Also, admin can check the statistic information from the system.

Page 1 of 49
OBJECTIVE OF THE PROJECT

The main purpose of our online ticket booking system is to provide another way for the
customer to buy cinema ticket. It is an automatic system.
 After inserting the data to database, staff need not to due with the order receive
through the system. In fact, there is similar system on the internet, but there is no
refund method found in the existing system.
 This system is basically aimed to provide the customer the complete information
of the movie, according to which the customer can book the tickets and the refund
facility provides more flexibility to the system.
The goals of our system are:
1 To provide anytime anyplace service for the customer.
2 To minimize the number of staff at the ticket.
3 To promote the film on the internet.
4 To increase the profit.
5 To obtain statistic information from the booking record.

Page 2 of 49
LANGUAGES USED

Why PHP?

PHP is a popular server-side scripting language for the web. Generally speaking, PHP is
used to add functionality to websites that HTML alone can't achieve. But what does this
really mean? Here are some examples.

PHP PERFORMS CALCULATIONS

PHP can perform all types of calculations, from figuring out what day it is or what day of
the week March 18, 2046, falls on, to performing all types of mathematical equations.In
PHP, math expressions are made up of operators and operands. Basic math addition,
subtraction, multiplication and division are done using mathematical operators. The large
number of math functions is part of the PHP core. No installation is required to use them.

PHP COLLECTS USER INFORMATION

Using PHP, you can let your user directly interact with the script. This can be something
really simple, like collecting the temperature from the user that they want to convert from
degrees to another format, or it can be more extensive information, like adding their
information to an address book, letting them post on a forum or participate in a survey.

PHP INTERACTS WITH MYSQL DATABASES

PHP is particularly good at interacting with MySQL databases, which opens endless
possibilities. You can write user-submitted information to a database, and you can
retrieve information from the database. This allows you to create pages on the fly using
the contents of the database.

You can even perform complex tasks like set up a login system, create a search feature,
or keep your store's product catalog and inventory online. You can also use PHP and
MySQL to set up an automated picture gallery to showcase products.

Page 3 of 49
PHP AND GD LIBRARY CREATE GRAPHICS

Use the GD Library that is bundled with PHP to create simple graphics on the fly or to
edit existing graphics.

You might want to resize images, rotate them, change them to grayscale, or make
thumbnails of them. Practical applications allow users to edit their avatars or generate
CAPTCHA verifications. You can also create dynamic graphics that are always changing
such as dynamic Twitter signatures.

PHP WORKS WITH COOKIES

Cookies are used to identify a user and store the user's preferences as given on the site so
the information doesn't have to be re-entered each time the user visits the site. The cookie
is a small file embedded on the user's computer. Using PHP, you can create, modify and
delete cookies and retrieve cookie values.

DBMS
MySQL is an open source relational database management system (RDBMS) based on
Structured Query Language (SQL).

MySQL runs on virtually all platforms, including Linux, UNIX, and Windows. Although
it can be used in a wide range of applications, MySQL is most often associated with web-
based applications and online publishing and is an important component of an open
source enterprise stack called LAMP. LAMP is a Web development platform that
uses Linux as the operating system, Apache as the Web server, MySQL as the relational
database management system and PHP as the object-oriented scripting language.
(Sometimes Perl or Python is used instead of PHP.)

MySQL, which was originally conceived by the Swedish company MySQL AB, was
acquired by Sun Microsystems in 2008 and then by Oracle when it bought Sun in

Page 4 of 49
2010. Developers can still use MySQL under the GNU General Public License (GPL),
but enterprises must obtain a commercial license from Oracle.

Offshoots of MySQL are called forks. They include:

 Drizzle – a lightweight open source database management system in


development based on MySQL 6.0.

 MariaDB – a popular community-developed "drop-in" replacement for


MySQL that uses MySQL APIs and commands.

 Percona Server with XtraDB– an enhanced version of MySQL known


for horizontal scalability.

1.2 Project Overview/specification

Administration Section:
 This section can be accessed by providing administrator password. In this section
the administrator can add the information related to movie, timings, theatres,
seats, booking, payment etc.
 In this section the administrator can delete and edit the information related to
movie, timings, theaters, seats, booking, payment etc.
Customer Section:

 Customer can view the movie ratings, casts, synopsis, facts, rates and show
timings which will help them to choose the movie.
 Customer can book the movie tickets by selecting the seats of his/her choice.
 Customer can view his/her booking history.

Page 5 of 49
Non Functional Requirements:

It consists of following parameters:-

Reliability: The system will consistently perform its intended function.

For e.g. The important information must be validated.

Efficiency: Unnecessary data will not be transmitted on the network and database server
will be properly connected.

Reusability: The system can be reused in any organization or site of the same group, by
defining the organization master definition under software license agreement.

Integrity: Only System Administrator has rights to access the database, not every user
can access all the information. Each user will be having rights to access the modules.

Page 6 of 49
1.3 Hardware Specification:

 Intel Pentium and Celeron class processor


 Processor Speed – 1.2 GHz or above
 RAM - 512 MB
 HDD - 40 GB
 Monitor-14”SVGA
 Printer –Laser Printer
 Mouse- Normal

Page 7 of 49
1.4 Software Specification:

Front-end Tool: - HTML, CSS, JavaScript

 User friendly

 Low Cost Solution

 GUI feature

 Better designing aspects

Back-end Tool: - PHP, MYSQL

 Security

 Portability

 Quality

Page 8 of 49
Chapter 2: LITERATURE SURVEY

2.1 Existing System:

Present system developed in php. In php there are some limitations.

 It is scripting language.
 It is very code complexity.
 There are server controls in php.
 It doesn’t support language interoperability
2.2 Proposed System
 We propose a system which is more reliable, entertaining and easy than the
present system.
 Our solution targets those users who do not have spare time to stand in queue for
booking tickets. We propose an easy way of ordering and paying for the tickets
without any delays and inconvenience.
 The people who book tickets are assured of a ticket before going to the theater
without their physical presence.
 Customers who book tickets will receive an instant message (m-ticket) in their
mobile phone. By splashing this m-ticket at the counter of multiplex, the customer
can get the physical ticket.
 The staff at the multiplex no longer needs complicated manual ticket availability
and tracking mechanisms for issuing tickets. The ticket information is stored
securely in a database which can be accessed any time for verification.

2.3 Feasibility Study:

After doing the project Online Movie Ticket Booking System, and analyzing all the
existing or required functionalities of the system, the next task is to do the feasibility
study for the project. All projects are feasible- given unlimited resources and infinite
time.

Page 9 of 49
Feasibility study includes consideration of all the possible ways to provide a solution to
the given problem. The proposed solution should satisfy all the user requirements and
should be flexible enough so that future changes can easily done, based on the future
upcoming requirements.

Economical Feasibility:

This is a very important aspect to be considered while developing a project. We decide


the technology based on minimum possible cost factor.

All hardware and software cost has to be borne by the organization.

Overall we have estimated that the benefits the organization is going to receive from the
proposed system will surely overcome the initial costs and the later on running cost for
system.

Technical Feasibility:

This included the study of function, performance and constraints that may affect the
ability to achieve an acceptable system. For this feasibility study, we studied complete
functionally to be provided in the system, as described in the System Requirement
Specification (SRS), and checked if everything was possible using different type of
fronted and blackened platform.

Operational Feasibility:

No doubt the proposed system is fully GUI based that is very friendly and all inputs to be
taken all self-explanatory even to a layman. Besides, a proper training has been
conducted to let know the essence of the system to the users so that they feel comfortable
with new system. As far our study is concerned the clients are comfortable and happy as
the system has cut down their loads and doing.

Page 10 of 49
Chapter 3: SYSTEM ANALYSIS AND DESIGN

3.1 Requirement specification:

Requirements analysis is done in order to understand the problem, which is to be solved.


That is very important activity for the development of database system. The requirements
and the collection analysis phase produce both data requirements and functional
requirements. The data requirements are used as a source of database design. The data
requirements should be specified in as detailed and complete form as possible.

In parallel with specifying the data requirements, it is useful to specify the known
functional requirements of the application. These consist of user-defined operations that
will be applied to the database (retrievals and updates). The functional requirements are
used as a source of application software design.

The Data-requirements are given as follows:-

User Module

User Registration
User Register with Name, A Username (for logging in later), Password, Phone
Number, E-mail address.
User Login
 User Can Book the Ticket After Log in.
 User Login with User Name and Password.
 Forgot Password use for Retrieve Password.
Check Availability
 After Login, User, Can Search Movie from Movie List.
 User Can Check Ticket Availability.
 User can also check the Movie Running Hours.

Page 11 of 49
Book Ticket

 User can book ticket by specifying username and Phone Number.


 Then Select Number of Seats to Book.
 A conformation Message will be sent to the Given Number.

Functional Requirements:
The schedule of the movies will be generated via a query according to the
data selected by the user.
 A way in which users (both customer & admin) can login to the
system to perform different operation.
 The system can verify the data before transaction.

Page 12 of 49
3.2 Flowchart:

Page 13 of 49
Fig 3.1 Use Case Diagram

Page 14 of 49
Fig 3.2 Use Case Diagram

Page 15 of 49
Fig 3.3 Activity Diagram

Page 16 of 49
Fig 3.4 Class Diagram

Page 17 of 49
ADMIN

Fig 3.5 Sequence Diagram

Page 18 of 49
MEMBER

Fig 3.6 Sequence Diagram

Page 19 of 49
ADMIN

Fig 3.7 Collaboration Diagram

Page 20 of 49
MEMBER

Fig 3.8 Collaboration Diagram

Page 21 of 49
Fig 3.9 Data Design

Page 22 of 49
3.3 Design and Test Steps / Criteria

System Design
The design of the system is the most critical factor affecting the quality of the software; it
has major impact on the later phases, particularly testing and maintenance. The output of
this phase is the design document. This document is similar to blueprint or plan for the
solution.
In this phase, a logical system is built which fulfils the given requirement. Design phase
of software development deals with the transforming the client’s requirement into a
logically working system. Normally, design is performed in the following two steps:

Primary Design Phase:

In this phase, the system is designed at block level. The blocks are created on the basis of
analysis done in the problem identification phase. Different blocks are created for
different function emphasis is put on minimizing the information flow between blocks.
Thus, all activities which require more interaction are kept in one block.

Secondary Design Phase:

In the secondary phase the detailed design of every block is performed.

The general tasks involved in the design process are the following:

1. Design various blocks for overall system processes.


2. Design smaller, compact and workable modules in each block.
3. Design various database structures.
4. Specify details of programs to achieve desired functionality.
5. Design the form of inputs, and outputs of the system.
6. Perform documentation of the design.
7. System reviews.

Page 23 of 49
User Interface Design:

User Interface Design is concerned with the dialogue between a user and the computer. It
is concerned with everything from starting the system or logging into the system to the
eventually presentation of desired inputs and outputs. The overall flow of the screens and
messages is called a dialogue.

The following steps are various guidelines for User Interface Design:

1. The system user should always be aware of what to do next.


2. The screen should be formatted so that various types of information, instruction
and messages always appear in the same general display area.
3. Message, instructions or information should be displayed long enough to allow
the system use to read them.
4. Use display attributes sparingly.
5. Default values not be allowed to proceed without correcting an error.
6. A user should never get an operating system message or fatal error.
7. The system user should never get an operating system message or fatal error.

Physical Design
Database Design
A database may be thought of as a set of related files. Related files mean that record of
one file may be associated with the records in another file.
The conventional file based systems emphasized that the application and files were built
around it. The database environment emphasizes the data independently of the
applications that use the data.
The applications are allowed to evolve around a database design such that it can adapt
to changing needs. Data becomes the central resource in the database environment.
Information systems are built around this central resource to give flexible access to
data.

Page 24 of 49
Design of Database Table
The data to be used in the system are stored in various tables. The number of tables used
& their structure are decided upon keeping in mind the logical relation in the data
available.
The database design specifies:
 The various tables to be used
 Data to store in each table
 Format of the fields & their types
 We are using database of SQL Server.
 To create the database firstly we start the SQL Server.

Project Modules
Login Module
 This module is for both type of users (customers and admin).In this module
according to the type of user (customer or admin) the further links and
operations will be provided.

Customer Module

 As soon as a visitor registers himself as a customer, the customer can now


book the movie tickets and pay for them online.

Hall Module

 This module deals with the information about the hall. There are several
multiplexes and each of them has 4 halls and according to the vacancy of seats in
the hall the booking takes place.

Booking Module
 In this module movie ticket is booked for a customer. This module contains all
the information related to booking. As soon as the customer request is complete,
all the booking details are displayed to him.

Page 25 of 49
Payment Module
 This is the most important module because it deals with the payment of the
tickets booked in the booking module. The customer can pay for the tickets
before the show by cash payment and if he wants to pay online, he can pay for
the tickets by credit card.

Gantt Chart:

 Gantt chart is also known as Time Line Charts. A Gantt chart can be developed
for the entire project or a separate chart can be developed for each function.

 A tabular form is maintained where rows indicate the tasks with


milestones and columns indicate duration (weeks/months).

 The horizontal bars that spans across columns indicate duration of the task.

Page 26 of 49
3.4 Testing
Software testing is a critical element of software quality assurance and represent the
ultimate review of specification, design, coding.
The purpose of product testing is to verify and validate the various work products viz.
units, integrated unit, final product to ensure that they meet their requirements.

Black Box Testing:

Black-box tests are used to demonstrate that software function are


operational, that input is properly accepted and output is correctly produced,
and that integrity of external information is maintained.

White Box Testing:

White-box tests are used to examine the procedural details. It checks the
logical paths by test case. It can also checks the conditions, loops used in the
software coding. It checks that loops are working correctly on defined
boundary value.

Characteristics of Testing:
Testing begins at the module level and works outward towards the integration of the
entire computer based system. Different testing techniques are appropriate at different
level of time. Testing & debugging are different activities, but debugging must be
accommodated in any testing strategy. There are different model of testing. On the basis
of testing methods. There are two types of testing.

Unit Testing For Component:



In system calendar use for the book the ticket.
In system also provide the facility for the movie information, theater
information and upcoming movie information.
In system each and every field have unique validation.

Page 27 of 49
Validations:

No record can be saved till all the necessary entries are done.
 Only administrator can perform sophisticated tasks like printing of Reports,
Register new member and/or delete an existing member etc.
 For security purposes the E-mail of user is required in case he/she forgets his/her
password and wants to retrieve that.
System Security Measures

 Security prompting the user for a user id and password in our application is a
potential security threat. So credential information is transferred from the browser
to server are encrypted.
 Cookies are an easy and useful way to keep user-specific information available.
However, because cookies are sent to the browser's computer, they are vulnerable
to spoofing or other malicious use. So we follow these guidelines:
 Do not store any critical information in cookies. For example, do not store a
user's password in a cookie, even temporarily.
 Avoid permanent cookies if possible. Consider encrypting information in
cookies. Set expiration dates on cookies to the shortest practical time we can.

Page 28 of 49
DATA STRUCTURE:
Tables in the database:

Table:
Credit Information:

User Information:

Page 29 of 49
Booking:

Location:

Page 30 of 49
Movie:

Screen:

Theatre:

Showtime:

Page 31 of 49
Chapter 4: RESULTS / OUTPUTS

Overview of User Interface


There is a common home page for admin and user from where they can login into their
system.

Screen Images
In this part some of the screen images and their functionalities are described.

Fig 4.1 Homepage

Page 32 of 49
Fig 4.2 Homepage

Fig 4.3 Homepage

Page 33 of 49
Fig 4.4 Sign Up Page

Fig 4.5 Login Page

Page 34 of 49
Fig 4.6 List of Movies Page

Fig 4.7 Movie Rates Page

Page 35 of 49
Fig 4.8 Movie Details Page

Fig 4.9 Customer Dashboard Page

Page 36 of 49
Fig 4.10 Contact Us Page

Fig 4.11 Trailers Page

Page 37 of 49
Fig 4.12 Booking Page

Fig 4.13 Booking Review Page

Page 38 of 49
Fig 4.14 Seat Selection Page

Fig 4.15 Confirmation Page

Page 39 of 49
Fig 4.16 Booking History Page

Fig 4.17 Admin Dashboard Page

Page 40 of 49
Fig 4.18 Admin Page

Fig 4.19 Admin Page

Page 41 of 49
Fig 4.20 Admin Page

Fig 4.21 Admin Page

Page 42 of 49
Fig 4.22 Admin Page

Fig 4.23 Admin Page

Page 43 of 49
Future scope and further enhancement of the Project

Future Scope

The project Online Cinema Ticket Booking System is flexible enough to meet the
requirements of the Customers. This project also has the scope of enhancements like:
1. Home delivery of tickets may be provided.
2. Online Booking of Purchases of eatables (cold drinks, popcorn etc) can be
provided.

Corporate booking:

Multimedia support for corporate presentation can be provided. Conference facility can
be provided for corporate meetings in the hall. This will increase the profit of cinema
halls as well as the company organizing event.

Group booking:

Any institute/company can book the tickets for students/clients and special discount will
be provided to them.

End User Support

 The proposed system is developed in PHP and MYSQL Server.


 If organization increases users, it just has to add more machines and install
the software on it, which is in the form of exe.

Security

Security features are implemented. No unauthorized access the package, as the security
is implemented through login and password.

Page 44 of 49
Further Enhancement of the Project

 Everything that is made has some or the other things to be added to make it
better than revolutions.
 The project “Online Cinema Ticket Booking System”, it has been tried to develop
a robust and fault free system, still enough flexibility has been provided for
further enhancements and modifications. As I mentioned earlier then the designed
forms are typically reflections of the developer, so I strongly believe that the
enhancement to be done with the project to be done with the design changes,
coding changes. But at the same time I would like to mention that since one
cannot claim himself as a master of the technology there is always some scope of
technical modifications in the project that may lead to find code redundancy
&storage space minimization.
 Since the data is retrieved from the tables where everything is based on the coding
system if the coding system is changed then the system needs to be redesigned.

Future Scope of Improvement

 More features can be added like


 Allow customers to comment on movies.
 Provide a list of upcoming movies.
 SMS notification after successful seat reservation.
 Encrypted Webpage to ensure customer privacy and transaction
security.
 More user friendly interface also in small screen devices.

Limitations
 Not suitable for large organization where number of network is very
large.
 No backup and restore utilities are incorporated.

Page 45 of 49
Chapter 5: CONCLUSION

 The project is a real time based management system. This can be practically
implemented.
 The mode of payment can be modernized and various enhancements could be
done to this process.
 The customer has the choice of choosing the seat he is comfortable with. Also the
pricing could be made dynamic in order to enhance the system.
 This project has been developed successfully and the performance system has
been found satisfactory.
 Use of this interface helps customer in having immediate information about
running movies and reserve their seat without wasting their precious time.
 User friendly Interface also for the admin to add and delete movie information.

Page 46 of 49
Chapter 6: REFERENCES

[1] Elmasri and Navathe, “Fundamentals of Database Systems”, 3/e, Addison - Wesley,
2001

[2] A Silberschaltz, H.F. Korth, and S sudarshan, “Database System Concepts”, 3/e, Tata
Mcgraw Hill, 1997

[3] Thomas M. Connolly, Carolyn E. Begg, “Database Systems & Practical Approach to
Design Implementation and Management”, 4/e, Addison – Wesley, 2005

BIBLIOGRAPHY

 https://www. mean.io//
 https://www.tutorialspoint.com/
 https://developers.google.com/
 https://stackoverflow.com/
 https://w3schools.com/

Page 47 of 49
Chapter 7: APPENDICES
LIST OF FIGURES

Figure Figure Name Page


Number Number

3.1 Use Case Diagram 14

3.2 Use Case Diagram 15

3.3 Activity Diagram 16

3.4 Class Diagram 17

3.5 Sequence Diagram (Admin) 18

3.6 Sequence Diagram (Member) 19

3.7 Collaboration Diagram (Admin) 20

3.8 Collaboration Diagram (Member) 21

4.1 Homepage 31

4.2 Homepage 32

4.3 Homepage 32

4.4 Sign Up Page 33

4.5 Login Page 33

4.6 List of Movies Page 34

4.7 Movie Rates Page 34

4.8 Movie Details Page 35

4.9 Customer Dashboard Page 35

4.10 Contact Us Page 36

Page 48 of 49
4.11 Trailers Page 36

4.12 Booking Page 37

4.13 Booking Review Page 37

4.14 Seat Selection Page 38

4.15 Confirmation Page 38

4.16 Booking History Page 39

4.17 Admin Dashboard Page 39

4.18 Admin Page 40

4.19 Admin Page 40

4.20 Admin Page 41

4.21 Admin Page 41

4.22 Admin Page 42

4.23 Admin Page 42

Page 49 of 49

Vous aimerez peut-être aussi