DBMS Mini Project (2437)

THEME PARK TICKETING SYSTEM 2023-24
CHAPTER 1
INTRODUCTION
Theme parks, operate as centres of attraction and fantasy and are expressed as ‘cathedrals
of consumption’, offering many places where visitors can consume. Furthermore, it is significant
among consumption tools with its innovative design, marketing activities, and memorable
experiences. It is a kind of modern tourism centre offering creative themes and events where
tourists can enjoy their leisure time and meet their entertainment needs. Theme parks, in addition
to offering fun activities such as cultural and artistic events, concerts, and various shows, services
such as restaurants, bars, water parks, and shopping malls, offer an authentic atmosphere with
different cultural and architectural structures.
Theme Park Ticketing System is a web-based technology which manages people and provides
ticket to the person who comes to visits and take ride in park with his/her family. This web
application provides a way to effectively control record & track the people who visit to park.
A Theme Park Ticketing system effectively manages and handles all the functioning of a park.
The software system can store the data of people tickets that came to visit in the park. The system
also maintains and calculates the price of ticket. The system needs an administrator to input the
detail of ticket like how many are adult and how many are child and print the ticket and give it to
person. The admin can also analyse the daily sales report which helps in manging sales and
marketing.
The system allows only admin to access all the data, add rides, pricing, add users and view sales
report. Whereas, the staff have access only for ticketing.
DEPARTMENT OF CSE, JVIT, BIDADI Page 1

CHAPTER 2
LITERATURE SURVEY
[1] The research review on the definition and the historical evolution of theme park
Research on the theme park abroad originated from the 1970s. China began the research in
the late 80s and prevailed in 90s. Throughout the domestic and foreign research, theme park is
substantially a kind of man-made landscape. It focuses on a specific theme and set many
entertainment contents, leisure elements and service facilities in the integrated. The form of theme
park is diverse. Meanwhile its primary purpose is making profits (Chris cooper, 1994; Xiangpin
Zhou, 1995; Jiajun Lou, 1998; Zhimin Ma, 1999; Guanzhi Dong, 2000). Theme Park is the result
of European amusement park (Brown and Church, 1987). Disneyland which opened in 1955 in
California in the United States is marked as the birth of the world's first theme park (Richard,
1987). The development of theme park in Japan started relatively the earliest in Asia (Shi Qi
ZhaoShi, 1991). There are two theories (Jiajun Lou, 1998) and the syllogism (Liming Zhang, 2007)
about the development of theme park in China. It generally has experienced the progress from the
initial single static displaying to making tourists enjoy a comprehensive participation experience
in interactive way and making theme park merge together with high technology.
Fig 2.1: Ancient Theme Park

[2] The research review on the diversity of theme park
The success of the Disneyland and universal studios is that they put the movie link
transplantation in the theme park, use high technology to realize virtual landscape and reduction
of various film scene, use advanced technology to create all sorts of virtual scene and attract
visitors of all sorts of different ages all over the world. Their common practice is to use their new
films to develop new projects. There are more than 130 new entertainments and theme
performances in Disney from 1955 to 1999. In addition, according to the needs of market
constantly they also develop new series of theme park. Theme Park in China experiences progress
from mainly transplanting and imitating of the single topic structure to multiple thematic structure
and comprehensive development. Given priority to local culture, entertainment and education as a
representative of the theme park there are the Suzhou Paradise, Yunnan Kunming Expo Garden,
Kaifeng Millennium City Park.
Fig 2.2: Diversity of Theme Park
[3] The research review on contact related to the theme park industry
In foreign countries, the development of the tourist area for urban planning and regional zoning
plays an important role. Tourism is regarded as the leading industries, or only the different
development model as an affiliated industry, in different extent influence the development of
theme parks in the future. Malcolm Cooper studied how to use the theme park to attract tourists,

the theme park by extending the existing tourism products, senior residential development within
the park, to make up for the usual expenses, these improvements for the tourism development of
Harvey Bay provides a good opportunity. Peter Dybedal mainly research the role of the theme
park for tourism development in remote, selection of Norway's four theme park as a case study (3
is located in rural areas), and a detailed description and analysis of the theme park tourist structure,
theme activity characteristics of the geographical location and the main function. The paper finally
summarizes the economic influence of theme park and think successful theme parks have a great
contribution to regional tourism.
[4] The theme park development trend and the research direction at home and abroad
With the expansion of globalization and development of the theme park, theme park in the
world has entered the homogeneity competition period, especially the construction of the Disney
theme park in the global scope. It brings many problems, such as the mimic of the same type theme
park, a lack of new idea, etc. The theme park is located and constructed according to the local
cultural tradition. Because of the difference of Chinese and western culture, the cultural and the
construction of theme park are different. The difference of research progress, living habits, values,
hard and soft facilities makes the direction of domestic and foreign theme park development also
differ. However, as one of the important development direction of tourism development, theme
park must develop toward the general trend of sustainability, ecological features, innovativeness
and cultural.
Fig 2.3: Modern Theme Park

[5] Theme Park Ticketing System
It is possible to find many types of research concerning theme parks, especially in the fields
of business and marketing. Many types of research have been conducted on the motivations of
visiting theme parks, visitor experience, visitor satisfaction, and so on. The motivational factors
for visiting Legoland Windsor Theme Park were investigated using the Grounded Theory, and it
was concluded that qualified personnel and theme park operation are the most important factors
affecting entertainment (Bakir & Baxter, 2011). In the study, in which the effects of the experience
in the theme park on customer satisfaction were examined, it was determined that the park
experience of the visitors, the food quality and variety, cleanliness, and atmosphere were the most
important criteria (Geissler & Rucks, 2011).
Several studies have focused on the satisfaction and post-purchase behavior of tourists (Bigné et
al., 2001; Grappi & Montanari, 2011; Prayag et al., 2013; Engeset & Elvekrok, 2015; Tsang et al.,
2016). In addition to the studies of post-purchase behavior, it is possible to find studies that
evaluate theme parks from different perspectives. Studies, such as evaluation of theme park
selection criteria (McClung, 1991), segmentation of theme park visitors and theme park market
(Fodness & Milner 1992), determination of park types, and visit motivations (Wong & Cheung,
1999), were conducted. Furthermore, evaluation of management (Milman, 2001), evaluation of
visitor feelings (Bigné et al., 2005), and determining theme park success factors (Pikkemaat &
Schuckert, 2007) have been studied in the literature.

CHAPTER 3
AIM AND SCOPE

3.1 Aim:
The main objective is to reduce the mistakes which creep up in manual systems. It provides good
level of security so it takes care of the user’s safety concerns as well. Admin can access the whole
list of all the rides available with their timings and fare of entry and ride ticket for both adults and
children. The customer can compare the best deals for them and take rides accordingly. When the
staff/admin enter all the details, the software helps them to find ticketing amount and the rides
chosen. The manual work is thus reduced and the chances of errors are reduced to minimum.
3.2 Scope:
✓ The proposed system will affect or interface with the person who visits in the park and
administrator.
✓ The system works and fulfills all the functionalities as per the proposed system.
✓ It will provide reduced response time against the queries made by different users.
✓ This project is based on PHP language with MYSQL database which manages people and
provides ticket to the person who comes to visits in park with his/her family.
✓ All possible features such as verification, validation, security, user friendliness etc have
been considered.

CHAPTER 4
REQUIREMENT AND SPECIFICATION

4.1 Software Requirements
Server Web logic server is used for recording data through XAMPP(Version 3.7)
Compatible operating system: Windows 10Pro
Frontend: php, Backend: Sql
Design Interface: Bootstrap Javascript, HTML, CSS
4.2 Hardware Requirements
12th Gen Intel(R) Core(TM) i7-1260P 2.10 GHz
Minimum of 256 MB RAM.
XAMPP and Server installation require up to 200MB of hard disk space and for planning purposes,
we recommend that users allocate 100MB per system for data base.
Client Compatible operating systems:
➢ Microsoft Windows 98(SE).

➢ Microsoft Windows 2000 Professional.
➢ Microsoft Windows XP Professional.
Network Requirements
User can run the HRMS on a single computer, or across a local area network (running at a min
speed of 100 MHz). For access to the server via a LAN, TCP/IP protocol is recommended.
Remote Access
It’s recommended that Microsoft Windows Terminal Services (or a similar technology) is used.

CHAPTER 5
METHODOLOGY
➢ Login Page
The page where the system users will submit their system credentials to access the data and
functionalities of the system according to their roles or permissions.
➢ Dashboard Page
The default page where the system users will be redirected after logging into the system. The
admin and staff users have a different view on this page which is the admin side displays a simple
summary while the staff user side displays only welcome greeting.
➢ New Rides Page
The page where the admin user submits the information on the new rides of the theme park.
➢ Rides List Page
The page where all the rides in the theme or amusement park are listed and managed. This page is
only visible to the admin users.
➢ New Pricing Page
The page where the admin can set up new pricing for new rides or promo tickets.
➢ Pricing List Page
The page where all ticket pricing is listed and managed by the admin. This page is only visible to
the admin users.
➢ New Ticket Page
The page where the system users generate a ticket/tickets for the customer/visitor.
➢ Ticket List Page
The page where the list of sold tickets is listed and managed.

➢ Sales Report Page
The page where the printable list of the sold tickets on a selected range of date is shown along with
the total amount of sale of the theme or amusement park.
5.1 Feasibility
Whenever we design a new system, normally the management will ask for a feasibility report of
the new system. The management wants to know the technicalities and cost involved in creation
of new system.
• Technical feasibility
• Economic feasibility
• Physical feasibility
5.1.1 Technical feasibility
Technical feasibility involves study to establish the technical capability of the system being created
to accomplish all requirements to the user. The system should be capable of handling the proposed
volume of data and provide users and operating environment to increase their efficiency.
For example, system should be capable of handling the proposed volume of data and provide users.
5.1.2 Economic feasibility
Economic feasibility involves study to establish the cost benefit analysis. Money spent on the
system must be recorded in the form of benefit from the system. The benefits are of two types:
Tangible benefits:
• Saving man labour to do tedious tasks saves time.
Intangible benefits:
• Improves the quality of organization.

5.1.3 Physical feasibility
It involves study to establish the time responses of the new system being created. For e.g., if the
new system takes more than one day to prepare crucial finance statement for the management,
wherever it was required in an hour, the system fails to provide the same.
It should be clearly established that the new system requirements in the form of time responses
would be completely met with. It may call for increase in cost. If the required cost is sacrificed
then the purpose of the new system may not be achieved even if it was found to be technically
feasible.
5.2 Object Modelling
The object model describes the structure of objects in a system. Their identity, their relationships
to other objects, their attributes, and their operations. The object model provides the essential
framework into which the dynamic and functional models can be placed.
Our goal in constructing an object model is to capture those concepts from the real world that are
important to an application. The object model is represented graphically with object diagrams
containing object classes. Classes are arranged into hierarchies sharing common structure and
behavior and are associated with other classes. Classes define the attribute values carried by each
object instance and the operations which each object performs or undergoes.
5.2.1 Identification of Object Classes
The first step in constructing an object model is to identify relevant object classes from the
application domain. Objects include physical entities, such as houses, employees, and machines,
as well as concepts, such as trajectories, seating assignments, and payment schedules. All classes
must make sense in the application domain; avoid computer implementation constructs, such as
linked lists and subroutines.

5.2.2 Identification of Attributes
Attributes are properties of individual objects. Attributes should not be objects. Use an association
to show any relationship between two objects. Adjectives often represent specific enumerated
attribute values. Attributes are less likely to be fully described in the statement of problem. The
knowledge must be drawn from the application domain and the real world to find out the attributes.
This below figure shows the identification of attributes.
Class Attributes
Login_info (Admin/Staff) Username or Email, Password, Secret code
Admin_info Dashboard, Rides, Pricing, Ticketing, Sales report,
Users
Staff_info Ticketing
User_info First name, Last name, Email, Password, Role
5.2.3 Dynamic Modelling
The dynamic model describes the aspects of a system that change over time. The dynamic model
is used to specify and implement the control aspects of a system. The dynamic model contains
state diagrams. A state diagram is a graph whose nodes are states and whose arcs are transitions
between states caused by events.
The dynamic model is insignificant for a purely static data repository. Such as a database. The
dynamic model is important for interactive systems. For most problems, logical correctness
depends on the sequences of interactions, not the exact times of interactions.
Dynamic modelling is a description of aspects of a system concerned with control, including time,
sequencing of operations, and interaction of objects.
Following steps are performed in constructing a dynamic model.
➢ Prepare scenarios of typical interaction sequences.

➢ Identify events between objects.
➢ Prepare an event trace for each scenario.

➢ Built a state diagram.

➢ Match events between objects to verify consistency.
➢ List all assumptions.
5.2.3.1 State Diagram
A state diagram relates events and states. When an event is received, the next state depends on the
current state as well as the event: A change of state caused by an event is called a transition. A
state diagram is a graph whose nodes are states and whose directed arcs are transitions labelled by
event names. A state is drawn as a rounded box containing an optional name. A transition is drawn
as an arrow from the receiving state to the target state: The label on the arrow is the name of the
event causing the transition. Figure below shows a state diagram describing the behaviour of
Theme Park Ticketing System.
5.2.4 Functional Modelling
The functional model shows how values are computed, without regard for sequencing, decisions
or object structure. The functional model shows which values depends on which other values and
the functions that relate them. The DFD are useful for showing functional dependencies. The
functions are expressed in various ways, including natural language, mathematical equations and
pseudo code. Functional Model is a description of aspects of a system that transform values using
functions, mappings, constraints and functional dependencies.
The following steps are performed in constructing a functional model.
➢ Identify input and output values.

➢ Build data flow diagram showing functional dependencies.
➢ Describe functions.
➢ Identify constraints.
➢ Specify optimization criteria.
➢ It should be logical consistent.

5.2.4.1 Data Flow Diagram
Data flow diagrams (DFD) depict information flow and the transforms that are applied as data
move from input to output. It is the starting point of design phase that functionally decomposes
the requirement specifications down to the lowest level details. Thus a DFD describes what data
flows (Logically) rather than how they are processed. So, it does not depend on hardware, software
or data structures. It is one of the most important tools used during system analysis. It is used to
model the system components such as the system process, data used by the process any external
that interact if the system and information flows in the system.
5.3 System Design

Design is the first step in the development phase for any techniques and principles for the purpose
of defining a device, a process or system in sufficient detail to permit its physical realization.
Once the software requirements have been analyzed and specified the software design involves
three technical activities - design, coding, implementation and testing that are required to build
and verify the software.
The design activities are of main importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation and its ease of maintenance are
made. These decisions have the final bearing upon reliability and maintainability of the system.
Design is the only way to accurately translate the customer’s requirements into finished software
or a system.
Design is the place where quality is fostered in development. Software design is a process through
which requirements are translated into a representation of software. Software design is conducted
in two steps. Preliminary design is concerned with the transformation of requirements into data.
Unified Modelling Language Diagrams (UML):
• The unified modelling language allows the software engineer to express an analysis model
using the modelling notation that is governed by a set of syntactic semantic and pragmatic
rules.

• A UML system is represented using five different views that describe the system from
distinctly different perspective. Each view is defined by a set of diagram, which is as
follows.
➢ User Model View:

• This view represents the system from the users perspective.
• The analysis representation describes a usage scenario from the end-users perspective.
➢ Structural model view:

• In this model the data and functionality are arrived from inside the system.
• This model view models the static structures.
➢ Behavioral Model View

• It represents the dynamic of behavioral as parts of the system, depicting the interactions of
collection between various structural elements described in the user model and structural
model view.
➢ Implementation Model View:

• In this the structural and behavioral as parts of the system are represented as they are to
be built.
➢ Environmental Model View:

In this, the structural and behavioural aspects of the environment in which the system is to be
implemented are represented.
UML is specifically constructed through two different domains they are
• UML Analysis modelling, which focuses on the user model and structural model views of
the system.
• UML design modelling, which focuses on the behavioral modelling, implementation modelling and
environmental model views.

5.3.1 Tables
5.3.1.1 Database Design

The data in the system has to be stored and retrieved from database. Designing the database is part
of system design. Data elements and data structures to be stored have been identified at analysis
stage. They are structured and put together to design the data storage and retrieval system.
A database is a collection of interrelated data stored with minimum redundancy to serve many
users quickly and efficiently. The general objective is to make database access easy, quick,
inexpensive and flexible for the user. Relationships are established between the data items and
unnecessary data items are removed. Normalization is done to get an internal consistency of data
and to have minimum redundancy and maximum stability. This ensures minimizing data storage
required, minimizing chances of data inconsistencies and optimizing for updates. The MS Access
database has been chosen for developing the relevant databases.
5.3.1.2 Table Description

Field description Name Type Size
Price id id int 11
Ride name name varchar 200
Ride id ride_id varchar 5
Adult price adult_price float
Childrens price child_price float
Created date date_created datetime
Table Name: pricing

Rides id id int 30
Ride name ride varchar 150
Ride description description text
Table Name: rides


Park id id int 30
Park name name text
Enquiry Email Id email varchar 200
Enquiry contact contact varchar 20
Park address address text
Table Name: system_settings

Ticket id id int 30
Ticket number ticket_no varchar 50
Ride id ride_id varchar 5
Ticket type type tinyint 1
Ticket id ticket_id int 30
Created date date_craeted datetime
Table Name: ticket_items

Ticket id id int 30
Ticket name name varchar 200
Number of adults no_adult int 11
Number of children no_child int 11
Adult price adult_price float
Children price child_price float
Price id pricing_id int 30
Amount amount float
Amount tendered tendered float
Table Name: ticket_list

User id id int 30
User first name firstname varchar 200
User last name lastname varchar 200
Email id email varchar 200
Password password text
Role type tinyint 1
Table Name: users
5.4 Implementation
5.4.1 ER Diagram
The ER diagram for the theme park ticketing system, the system data, and their attributes. The data
and the attributes are represented by the table, and the table shows how they are related to each
other.
We can create the ER diagram for the table just in 5 minutes. There are some steps, and with the
help of these steps, we can build the ER diagram for the theme park ticketing system project. The
steps are as below.
Step 1: We must familiarize ourselves with the entity relationship diagram cardinality and
symbols. Then we have to show the data structure for the project in the entity relationship diagram.
The symbol of the entity relationship diagram shows how they fit together. Before making the ER
diagram, we should properly know the meaning of all the symbols and how to use all of them
symbols.

Symbol of entity relationship diagram:
1. Fields: This entity shows how the different types of data are used together for a project.
The symbol is used to show how the part of the project is working.
2. Key: It is a type of technique that is used to categorize the quality of the data. There are
two types of keys available for the database. These are as follows.
o Primary key: It is a set of unique properties that are used for finding the specific
entity.
o A foreign key: It is a type of key made up of a piece of data with too many links
to other things.
Step 2: Finalize the entities included
Start making your ER Diagram by deciding on all the parts your theme park ticketing system must
have. You'll need to leave the area in your design for these rectangles to be included later.
Step 3: Add the attributes of each entity
After you've decided on the entities, think about the traits you'll need for each one. In a conceptual
ER diagram, the details of the different entities are given as attributes. Attributes are things like a
thing's traits, a many-to-many relationship, or a one-to-one relationship. Attributes with multiple
values can be given more than one value.
Step 4: Describe the relationships (cardinality) between entities and attributes
You will need the entities, their attributes, and the relationships between them to plot the
relationships between the ERD. To get the right entity relationship diagram, you will use the
information you gathered to build the data structure.

ER-DIAGRAM:
An entity-relationship diagram is a visual form of relational database. It can be used to design a

new database, or to visualize and understand an existing one. They are also often refered to as
entity relationship models or entity relationship graphs.
Fig 5.4.1: ER-Diagram

5.4.2 Schema Diagram
A database schema represents the logical configuration of all or part of a relational database. It can
exist both as a visual representation and as a set of formulas known as integrity constraints that
govern a database. These formulas are expressed in a data definition language, such as SQL. As
part of a data dictionary, a database schema indicates how the entities that make up the database
relate to one another, including tables, views, stored procedures, and more.
System_settings
id
name
email
contact
address
cover-img
Ticket_list
id
name
users no_adult
rides
no-child
id adult_price
Id firstname child_price
Ride lastname pricing_id
Description email amount
date_created password tendered
type
pricing Ticket_items
id id
name ticket_no
ride_id ride_id
adult_price type
child_price ticket_id
date_created date_created
Fig 5.4.2: Schema Diagram

5.5 Testing
Software testing techniques:
Software testing is a critical element of software quality assurance and represents the ultimate
review of specification, designing and coding.
Testing objectives:
• Testing is process of executing a program with the intent of finding an error.
• A good test case design is one that has a probability of finding an as yet undiscovered error.
• A successful test is one that uncovers an as yet undiscovered error.
These above objectives imply a dramatic change in view port.
Testing cannot show the absence of defects, it can only show that software errors are present.
There are three types of testing strategies
a. Unit Testing:
Unit testing focuses verification efforts on the smallest unit of software design module. The unit
test is always white box oriented. The tests that occur as part of unit testing are testing the module
interface, examining the local data structures, testing the boundary conditions, execution all the
independent paths and testing error-handling paths.
b. Integration Testing:
Integration testing is a systematic technique or construction the program structure while at the
same time conducting tests to uncover errors associated with interfacing. Scope of testing
summarizes the specific functional, performance, and internal design characteristics that are to be
tested. It employs top-down testing and bottom-up testing methods for this case.
c. Performance Testing:
Timing for both read and update transactions should be gathered to determine whether system
functions are being performed in an acceptable timeframe.

CHAPTER 6
RESULTS AND DISCUSSION

This project allows users to issue tickets. Admin is provided with rights to see sales report, edit
rides list, pricing and manage the users. The Theme Park Ticketing System is a simple
PHP/MySQL project that helps manages and generates the visitors' tickets in a theme or
amusement park. The system can generate a various ticket at once in different types and all of the
tickets has a unique ticket number. The theme park management or administrator can set up
different pricing for the rides, entrance, or promos that the park offers to the visitors. The system
separates the adult and child fee for every pricing setup. The administrator user has the permission
to manage all the data in the system especially the rides list and pricing list of the theme or
amusement park. The system also generates a sales report for the number of tickets sold in the
management's choice of the date range. This ticketing system also a simple calculator that helps
the staff or admin calculate the total amount to pay and change of the customer or visitor. The
ticket format is just simple, it only displays the ticket number, pax type (Adult/Child), ticket type
(e.g. "Entrance"), and the date sold.

CHAPTER 7
SOURCE CODE
CREATE TABLE `pricing` (

ìd` int(11) NOT NULL,
`name` varchar(200) NOT NULL,
`ride_id` varchar(5) NOT NULL,
àdult_price` float NOT NULL,
`child_price` float NOT NULL,
`date_created` datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
INSERT INTO `pricing` (ìd`, `name`, `ride_id`, àdult_price`, `child_price`, `date_created`)

VALUES
(1, 'Entrance', '0', 100, 80, '2020-11-30 09:27:45'),
(2, 'Ride All U Can', 'all', 500, 400, '2020-11-30 09:29:14'),
(3, 'Ride Ticket', '1', 150, 130, '2020-11-30 09:30:44'),
(4, 'Ride Ticket', '2', 150, 130, '2020-11-30 09:31:03');
CREATE TABLE `rides` (

`ride` varchar(150) NOT NULL,
`description` text NOT NULL,
INSERT INTO `rides` (ìd`, `ride`, `description`, `date_created`) VALUES

(1, 'Ride 1', 'Sample Ride 1', '2020-11-30 09:03:47'),
(2, 'Ride 2', 'Sample Ride 2', '2020-11-30 09:04:16');
CREATE TABLE `system_settings` (

`name` text NOT NULL,
èmail` varchar(200) NOT NULL,
`contact` varchar(20) NOT NULL,
àddress` text NOT NULL,
`cover_img` text NOT NULL

INSERT INTO `system_settings` (ìd`, `name`, èmail`, `contact`, àddress`, `cover_img`)

VALUES
(1, 'Theme Park Ticketing System', 'info@sample.comm', '+6948 8542 623', '2102 Caldwell
Road, Rochester, New York, 14608', '');
CREATE TABLE `ticket_items` (

`ticket_no` varchar(50) NOT NULL,
`ride_id` varchar(5) NOT NULL,
`type` tinyint(1) NOT NULL COMMENT '1=Adult,2=Child',
`ticket_id` int(30) NOT NULL,
`date_created` datetime NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp()
INSERT INTO `ticket_items` (ìd`, `ticket_no`, `ride_id`, `type`, `ticket_id`, `date_created`)

VALUES
(24, '464281140265', 'all', 2, 1, '2020-11-30 11:13:40'),
(25, '923853725245', 'all', 2, 1, '2020-11-30 11:13:40'),
(26, '745910660254', 'all', 2, 1, '2020-11-30 11:13:40'),
(27, '112398007983', '0', 2, 2, '2020-11-30 11:14:57'),
(28, '694424283587', '0', 2, 2, '2020-11-30 11:14:57'),
(29, '881923647970', '0', 2, 2, '2020-11-30 11:14:57'),
(30, '295200337001', '0', 2, 2, '2020-11-30 11:14:57'),
(31, '634386703173', '0', 2, 2, '2020-11-30 11:14:57'),
(32, '288052419703', '0', 2, 2, '2020-11-30 11:14:57'),
(33, '717927139551', '0', 2, 2, '2020-11-30 11:14:57'),
(34, '338361442836', '0', 2, 2, '2020-11-30 11:14:57'),
(35, '118710645494', '0', 2, 2, '2020-11-30 11:14:57'),
(36, '764495422944', '0', 2, 2, '2020-11-30 11:14:57'),
(37, '189977891424', '0', 2, 2, '2020-11-30 11:14:57'),
(38, '409072780821', '0', 2, 2, '2020-11-30 11:14:57'),
(39, '311889863954', '0', 2, 2, '2020-11-30 11:14:57'),
(40, '107156954800', '0', 2, 2, '2020-11-30 11:14:57'),
(41, '484347209065', '0', 2, 2, '2020-11-30 11:14:57'),
(42, '638469245972', '0', 2, 2, '2020-11-30 11:14:57'),
(43, '884095884722', '0', 2, 2, '2020-11-30 11:14:57'),
(44, '305644172130', '0', 2, 2, '2020-11-30 11:14:57'),
(45, '122929510520', '0', 2, 2, '2020-11-30 11:14:57'),
(46, '553555894924', '0', 2, 2, '2020-11-30 11:14:57'),
(49, '855647843645', 'all', 1, 3, '2020-11-30 13:03:55'),
(50, '524460479419', 'all', 1, 3, '2020-11-30 13:03:55'),
(51, '275259836175', 'all', 2, 3, '2020-11-30 13:03:55');

CREATE TABLE `ticket_list` (

`name` varchar(200) NOT NULL,
`no_adult` int(11) NOT NULL,
`no_child` int(11) NOT NULL,
àdult_price` float NOT NULL,
`child_price` float NOT NULL,
`pricing_id` int(30) NOT NULL,
àmount` float NOT NULL,
`tendered` float NOT NULL,
INSERT INTO `ticket_list` (ìd`, `name`, `no_adult`, `no_child`, àdult_price`, `child_price`,

`pricing_id`, àmount`, `tendered`, `date_created`) VALUES
(1, 'John Smith', 5, 3, 500, 400, 2, 3700, 4000, '2020-11-30 11:03:27'),
(2, 'George Wilson', 10, 20, 100, 80, 1, 2600, 3000, '2020-11-30 11:03:56'),
(3, 'Claire Blake', 2, 1, 500, 400, 2, 1400, 2000, '2020-11-30 13:02:39');
CREATE TABLE ùsers` (

`firstname` varchar(200) NOT NULL,
`lastname` varchar(200) NOT NULL,
èmail` varchar(200) NOT NULL,
`password` text NOT NULL,
`type` tinyint(1) NOT NULL DEFAULT 2 COMMENT '1 = admin, 2 = staff',
INSERT INTO ùsers` (ìd`, `firstname`, `lastname`, èmail`, `password`, `type`, `date_created`)
VALUES
(1, 'Administrator', '', 'admin@admin.com', '0192023a7bbd73250516f069df18b500', 1, '2020-11-
26 10:57:04'),
(2, 'John', 'Smith', 'jsmith@sample.com', '1254737c076cf867dc53d60a0364f38e', 2, '2020-11-30
12:00:11');
ALTER TABLE `pricing`

ADD PRIMARY KEY (ìd`);
ALTER TABLE `rides`

ALTER TABLE `system_settings`


ALTER TABLE `ticket_items`

ALTER TABLE `ticket_list`

ALTER TABLE ùsers`

ALTER TABLE `pricing`

MODIFY ìd` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;
ALTER TABLE `rides`

ALTER TABLE `system_settings`

ALTER TABLE `ticket_items`

ALTER TABLE `ticket_list`

ALTER TABLE ùsers`

COMMIT;

CHAPTER 8
SNAPSHOTS
Fig 8.1: Login Page
Fig 8.2: Admin Home Page

Fig 8.3: Staff Home Page
Fig 8.4: Adding new ride

Fig 8.5: Pricing
Fig 8.6: Ticketing

Fig 8.7: Sales Report
Fig 8.8: Adding Users

Fig 8.9: Users List
Fig 8.10: Printing Ticket

CHAPTER 9
CONCLUSION AND FUTURE WORK

The Theme Park Ticketing System was developed using HTML, PHP/MySQL, CSS, JavaScript
(jQuery/Ajax), and Bootstrap for the design. The source code is fully functional and easy to modify
or enhance. Follow the instruction below to have an actual experience using this simple project.
The project titled as Theme Park Ticketing System was deeply studied and analysed to design
the code and implement. It was done under the guidance of the experienced project guide. All the
current requirements and possibilities have been taken care during the project time.
Theme Park Ticketing System is a web-based application which manages and handles the people
ticket who visited in the park.

BIBLIOGRAPHY
[1] Guanzhi Dong. (2000). Tourism theme park management theory and practice.
Guang zhou: Guangdong Tourism Publishing House.
[2] Guo Cui, Jingfeng Chu etc. (2011). Creative tourism connotation abroad study. Journal
of Human Geography, 2011 (6) : 24-33.
[3] Richards, G. & C. Raymond. (2000). Creative tourism. ATLAS news, 2000(23):16-20.
[4] S. Anton Clave. (2010). The Global Theme Park Industry. CABI. UK.
[5] Sara Nordin. (2006). Tourism Clustering & Innovation-Paths to Economic Growth &
Development [EB/OL]. [Online] Available: http://www.etour.se,2006-12-21.
[6] Alegre, J., & Garau, J. (2010). Tourist satisfaction and dissatisfaction. Annals of
Tourism Research.
[7] For PHP
➢ https://www.w3schools.com/php/default.asp
➢ https://www.sitepoint.com/php/
➢ https://www.php.net/
[8] For MySQL
➢ http://www.mysqltutorial.org
➢ http://www.mysql.com/
[9] For XAMPP
➢ https://www.apachefriends.org/download.html

DBMS Mini Project (2437)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DBMS Mini Project (2437)

Uploaded by

Copyright:

Available Formats

THEME PARK TICKETING SYSTEM 2023-24

DEPARTMENT OF CSE, JVIT, BIDADI Page 1

Fig 2.1: Ancient Theme Park

DEPARTMENT OF CSE, JVIT, BIDADI Page 2

[2] The research review on the diversity of theme park

Fig 2.2: Diversity of Theme Park

DEPARTMENT OF CSE, JVIT, BIDADI Page 3

Fig 2.3: Modern Theme Park

DEPARTMENT OF CSE, JVIT, BIDADI Page 4

[5] Theme Park Ticketing System

DEPARTMENT OF CSE, JVIT, BIDADI Page 5

AIM AND SCOPE

DEPARTMENT OF CSE, JVIT, BIDADI Page 6

REQUIREMENT AND SPECIFICATION

Compatible operating system: Windows 10Pro

Frontend: php, Backend: Sql

Design Interface: Bootstrap Javascript, HTML, CSS

4.2 Hardware Requirements

12th Gen Intel(R) Core(TM) i7-1260P 2.10 GHz

Minimum of 256 MB RAM.

Client Compatible operating systems:

➢ Microsoft Windows 98(SE).

DEPARTMENT OF CSE, JVIT, BIDADI Page 7

➢ New Rides Page

➢ Rides List Page

➢ New Pricing Page

➢ Pricing List Page

➢ New Ticket Page

➢ Ticket List Page

DEPARTMENT OF CSE, JVIT, BIDADI Page 8

➢ Sales Report Page

5.1.1 Technical feasibility

5.1.2 Economic feasibility

DEPARTMENT OF CSE, JVIT, BIDADI Page 9

5.1.3 Physical feasibility

5.2 Object Modelling

5.2.1 Identification of Object Classes

DEPARTMENT OF CSE, JVIT, BIDADI Page 10

5.2.2 Identification of Attributes

5.2.3 Dynamic Modelling

Following steps are performed in constructing a dynamic model.

➢ Prepare scenarios of typical interaction sequences.

DEPARTMENT OF CSE, JVIT, BIDADI Page 11

➢ Built a state diagram.

5.2.3.1 State Diagram

5.2.4 Functional Modelling

The following steps are performed in constructing a functional model.

➢ Identify input and output values.

DEPARTMENT OF CSE, JVIT, BIDADI Page 12

5.2.4.1 Data Flow Diagram

5.3 System Design

Unified Modelling Language Diagrams (UML):

DEPARTMENT OF CSE, JVIT, BIDADI Page 13

➢ User Model View:

➢ Structural model view:

➢ Behavioral Model View

➢ Implementation Model View:

➢ Environmental Model View:

DEPARTMENT OF CSE, JVIT, BIDADI Page 14

5.3.1.1 Database Design

5.3.1.2 Table Description

Field description Name Type Size

DEPARTMENT OF CSE, JVIT, BIDADI Page 15