1.

Introduction
1.1. The objective of the project
1. 1.1 General objective
1.1.2. Specific objectives
1.2. Description of the project
1.3. Scope of the project
2. System Description
2.1. Customer/User Profiles
2.2. Assumptions and Dependencies (If Applicable)
2.3. Functional Dependency
2.4. Normalization
3. Design
3.1 Database Design
3.1.1. E-R Diagram
3.1.2. Detail of Schemas
4. Project Snapshot and Complete code
1. Introduction
Cinema Management System Database Design is aimed to provide complete information about
the movie and schedule to the customer, according to which he/she can easily get a ticket instantly and can book a ticket
for his/her favorite movies. Admin can use the cinema management system to insert and delete data such as movie
descriptions, and movie schedules which will update the related webpage and will be accessible to the customers. Admin
can update the webpage changing according to the data in the database also admin can check the statistics information
from the system. Operate your cinema with better efficiency by automating the reservation and ticketing process to
improve profitability and manage your cinema better by having access to key data in a centralized and systematic view
and increasing customer satisfaction by giving your customers what they want when it comes to seat preference.

Some Point:-
• Contemporary multiplex movie theaters can have one or more auditoriums within a larger complex,
• Each auditorium can have a different number of seats,
• Seats are numerated with row number and seat position within a row,
• Cinema movie can have multiple screenings at different times, or it can be screened simultaneously in a different
auditorium,
• Cinema for each screening a seat can be reserved/sold only once,
• We want to track who entered each reservation/sale into the system.
1.1 Objective of the project

• The main purpose of our online ticket booking system is to provide

another way for the customer to buy a cinema management system. It is
an automatic system.
• After inserting the data into the database, staff need not to due with the
order received through the system. In fact, there is a 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 about 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.1 Objective of the project
1. 1. 1 General objective

The general objective of this project is to minimize the current problem by

developing an automated system for cinema management system program schedule
and online ticket booking reservations. To achieve a suitable system for customer
registration and showing the scheduled increase in the availability of the future will
successfully, perform the mission and vision of the organization. To increases the
performance and minimize the problems found around the organization.
1.1.2. Specific objectives

Enables the record of data effectively and efficiently

▪ Film (in detail) information
▪ On-line customer ticket reservation
▪ Select film and time, level information
▪ Admin add, delete, edit, search, and view programs and customer information.
▪ Users can take the ticket for film and select their choice of information
1.2. Description of the project

A Cinema management system is a project that allows users to check

for available seats in the theatre and can even book them at the same
time. It happens when people go to a movie and they return in
disappointment due to being houseful. Hence the project is intended to
overcome this situation by automating the manual booking system,
online. Users can make prior bookings for desired seats for their desired
show at desired time and cost. The system provides additional optional
things like food packages, discounts, etc. It also calculates all the
associated charges incurred in booking the ticket and the items. This is
an advanced booking system that makes user customize their show
according to their needs.
1.3. Scope of the project

The system proposed is mainly focused on cinema Managements System online

ticket reservations and posting information about films and entertainment on the
web.
▪ The system will provide online reservations/to users
▪ the user is able to view the cinema’s programs.
▪ Add and remove film/by Admin.
▪ Users have the ability to DBMS cinema Managements System home/to users
▪ Assign the movies/ theater date & time/by Admin
▪ Create a User account, Log in/only users
2. System Description
The cinema management system is a software application that is used
to streamline the operations of a cinema. The system is designed to
manage the cinema's inventory, ticketing, and customer data. The
system can also be used to generate reports and analytics to help the
cinema optimize its operations. The Cinema Management System is an all-in-
one solution that is capable of handling all ticket-related operations at the cinema.
The solution includes a full-fledged cinema management software suite & another
module such as a counter sales platform (full-fledged cinema ticketing system), a
web & mobile solution, APIs that can be utilized by third-party vendors across
their platforms & a backend that seamlessly integrates all these different modules
to provide real-time synchronized ticket bookings.
 2.1 Customer / User
The cinema management system should allow for the creation of customer/user profiles.
Customers/users should be able to input their personal information, including contact
details and preferences, into the system. This will allow the cinema to send targeted
communications to customers/users, as well as personalize their experience when they
visit the cinema. A customer/user profile in a cinema management system would typically
include information such as the customer's name, contact information, and payment
information. The system might also track the customer's movie preferences and viewing
history.
create table customercinema(
customer_id number(10),
customer_FName varchar(20),
customer_LName varchar(20),
Booking_ticket varchar(10),
Phone_no number(20),
Email_id varchar(20),
Password varchar(20),
Customer_Gender varchar(20),
CONSTRAINT customer PRIMARY KEY (customer_id));
 C_FNAME
CID C_LNAME

PASSWORD BOOKING
TICKET
Customer/User

EMAIL_ID
PHONE_NO

ADDRESS
Gender
2.2 Assumptions and Dependencies (If applicable)
Assumption:

The Cinema Management system database is a collection of information about

the movies and customers of a cinema. The database has the following tables:
Movies: This table stores information about the movies shown at the cinema.
Customers: This table stores information about the customers of the cinema.
Ticket_sales: This table stores information about the tickets sold by the cinema.

In the specification paper, we are told to record the address of every person
which consists of country, province/state/zone, city, street, street number, and
a list of phone numbers to the location of the address and a list of fax
numbers to the location of the address. So, I assumed to make the length of
address attribute longer.
Dependencies

This Section will state the ordering relation among work packages to
account for interdependencies among them and dependencies on
external events. Techniques such as dependency list activity network
and the critical path the method may be used to depict dependencies
among work package
2.3. Functional Dependencies
Functional dependency refers to the relation of one attribute of the database to
another. With the help of functional dependency, the quality of the data in the
database can be maintained. Functional Dependency (FD) is a constraint that
determines the relation of one attribute to another attribute in a Database
Management System (DBMS). Functional Dependency helps to maintain the quality
of data in the database. It plays a vital role to find the difference between good and
bad database design.

Advantages of Functional Dependencies

•Functional Dependency avoids data redundancy. Therefore same data do not repeat at
multiple locations in that database
•It helps you to maintain the quality of data in the database
•It helps you to define the meanings and constraints of databases
•It helps you to identify bad designs
•It helps you to find the facts regarding the database design
2.4 Normalization

In relational database design, the process of organizing data to minimize redundancy.

Normalization usually involves dividing a database into two or more tables and
defining relationships between the tables. The objective is to isolate data so that
additions, deletions, and modifications of a field can be made in just one table and then
propagated through the rest of the database via the defined relationships Normalization
is a method of organizing the data in the database which helps you to avoid data
redundancy, insertion, update & deletion anomaly. It is a process of analyzing the
relation schemas based on their different functional dependencies and primary key.
Normalization is inherent to relational database theory. It may have the effect of
duplicating the same data within the database which may result in the creation of
additional tables.
Seats SET_ID SEAT_NAME NO.OF SEAT

Admin1
ADMIN_ID ADMIN_PASSWORD

Theater TICKET_ID TICKET_NAME TICKET_LOCATION

SHOW_ID SHOW_DATE SEAT_NO PRICE TICKET_ID HALL_NO TICKET_NO

Ticket

Discount OFFER_ID MOVICE_NAME PRICE

Show S_START_TIME S_END_TIME Show_id Language

Movie Movie_id Movie_name Release_date Director Actor

Book Ticket_No Customer_ID

Customer cinema Cust_id Cust_Fna Cust_Lna Book_Tick Phone_no Email_id Password Cust_Gen
me me et der
3. Design

3.1 Database Design

We represent the main entity types of this database . For each entity types, we
provide some of the corresponding attributes. Use this information in order:-
❖ Build an Enhanced E-R diagram
❖ Transform the Enhanced E-R diagram to a relational database. Identify the
primary key(s) and the foreign key(s) for each relation.
❖ For each of the relation created, indicated its normal form. If the relation is
not in the 3NF, decompose it into 3NF relations.

1. Customer: The main attributes are identification number, name , address,

telephone number, email etc.
2. Employee: The main attributes are identification number, name ,address,
telephone number, salary etc.
3. Movie: The main attributes are identification movie number , title , year of
production, actors ,location etc.
 Data To be Managed
An Cinema Managements system generally manages data. In the case of a cinema Managements
system, the following data would be managed:-

Movies:
This data would include a listing of the movies to be shown in the cinema , details of the movies
Such as title , cast, and introduction including a short clip perhaps . All these could be assessed on
the system.
Seats:
The number and details of seats are registered on the system . This enables automated allocation or
manual choosing by user on the system. This Flexibility allows for preference in choosing a seat

Viewer Data:
The data of the viewer also need to be managed as the viewer would provide personal details
Including a passport photograph.
Payment System:
The available payment system which could be used in processing payment for a web based cinema
Managements system .
E-R Diagram

ER Diagram represents the method of Cinema Management System. The Entity

relationship diagram of the Cinema Management System shows all the visual
instruments of the database tables and the relations between Customers, Movies,
Shows, etc. It used structure data to define the relationships between structure
data groups of Cinema Management System functionalities. The main entities of
the Cinema Management System are movies, customers, booking, seats, and
shows.
 Password Offer_id Movie_name
Seat_name Admin_id
Set_id
Admin Discount
No of seats Price
has
Seats
End_time
Show_id
Show_time
worker has
has

Ticket_no Show

Theatre has
T_id Tickets Language
has

T_name has
Show_id
Location Price
Movie_id
Show data
C_FName Seat_no
Movie
C_id
Booking Booking _date M_name
Customer Actor
Emil_id Phone_no C_id Release_date
Ticket_no Director
Password Gender
 Seats
Theater seating is a style of commonly used event layout, comprised of chairs aligned in
consecutive straight rows, generally facing a single direction. It is sometimes called stadium
seating or auditorium seating.

create table seat(

set_id number(5),
seat_name varchar(10),
No_of_seats number(5),
CONSTRAINT sets PRIMARY KEY (set_id));

select * from seat

insert into seat values(101,'Ram',20);

insert into seat values(102,'Prabin',21);
insert into seat values(103,'Akash',22);
insert into seat values(104,'Sukdev',23);
insert into seat values(105,'Ashish',24);
insert into seat values(106,'Tasuwar',25);
 Admin

Create table admin1(

admin_id varchar(10),
admin_password varchar(10));

insert into admin1 values('Ram_101','RAM12@');

insert into admin1 values('Prabin_102','Prabin12@');
insert into admin1 values('Akash_103','Akash12@');
insert into admin1 values('Sukdev_101','Sukdev12@');

select * from admin1

 Theater
A theater is a building with a stage in it, on which plays, shows, and other performances
take place. They brought her to the theater where their new music was in production.
singular noun. You can refer to work in the theater such as acting or writing plays as the
theater.

create table theater(

Ticket_id number(5),
Ticket_name varchar(15),
Ticket_location varchar(10));

insert into theater values(101,'Ram','Seats_no');

insert into theater values(102,'Prabin','Seats_no');
insert into theater values(103,'Akash','Seats_no');
insert into theater values(104,'Sukdev','Seats_no');

select * from theater;

 Ticket

create table Ticket(

show_id number(5),
show_date number(10),
seat_no number(5),
Price number(5),
Ticket_id number(5),
Hall_no number(10),
Ticket_no number(5));

insert into ticket values(11011, 11-15-2022, 101,75,

001,02,1010);
insert into ticket values(11012, 11-16-2022, 102,75,
002,02,1012);
insert into ticket values(11013, 11-17-2022, 103,75,
003,02,1013);
insert into ticket values(11014, 11-18-2022, 104,75,
004,02,1014);

select * from ticket;

 Discount

create table discount(

offer_id number(5),
Movice_name varchar(10),
Price number(10));

insert into discount values(11011,'Ram setu', 50);

insert into discount values(11021,'Brahmastra', 40);
insert into discount values(11031,'Dhoom 2', 60);
insert into discount values(11041,'Dhoom', 50);

select * from discount;

 SHOW

•The time at which entertainment, such as the showing of a movie, is scheduled to start.
•The scheduled or actual time at which a show or something likened to a show begins

create table show(

show_start_time varchar(5),
show_end_time varchar(5),
Show_id number(5),
Language varchar(10));

insert into show values('09 PM', '12 PM',11011,'Hindi');

insert into show values('12 PM', '02 PM',11012,'Hindi');
insert into show values('03 PM', '06 PM',11013,'English');
insert into show values('07 PM', '10 PM',11014,'Hindi');

select * from show;

 Movie

A screen is a flat vertical surface on which pictures or words

are shown. Television sets and computers have screens, and films are shown
on a screen in cinemas
create table movice(
Movie_id number(10),
Movice_name varchar(20),
Release_date varchar(20),
Director varchar(10),
Actor varchar(10));

insert into movice values(11,'Ram Setu','Dec-

20','Abhishek','Akashy');
insert into movice values(12,'Brahmastra','Dec-
22','Ayan','Ranbir');
insert into movice values(13,'Dhoom','Dec-
23','Sanjay','Hrithik');
insert into movice values(14,'Dhoom2','Dec-
25','Sanjay','John');

select * from movice;

 Booking

A booking is a small, official piece of paper or card which shows that you
have paid to enter a place such as a theatre or a sports ground, or shows
that you have paid for a journey

create table book(

Ticket_no number(10),
Customer_id number(10));

insert into book values(1010,1111);

insert into book values(1012,1112);
insert into book values(1013,1113);
insert into book values(1014,1114);

select * from book;

 Customer

create table customercinema(

customer_id number(10),
customer_FName varchar(20),
customer_LName varchar(20),
Booking_ticket varchar(10),
Phone_no number(20),
Email_id varchar(20),
Password varchar(20),
Customer_Gender varchar(20),
CONSTRAINT customer PRIMARY KEY (customer_id));

insert into customercinema values(1111,'Ram','Gupta',1010,7622551260, '[email protected]', 'Ram12@','Male');

insert into customercinema values(1112,'Prabin','Gupta',1012,7622551211, '[email protected]', 'Prabin12@','Male');
insert into customercinema values(1113,'Tasuwar','Ali',1013,76001287612, '[email protected]',
'Tasuwar12@','Male');
insert into customercinema values(1114,'Ashish','Yadav',1014,7622577260, '[email protected]', 'Ashish12@','Male');
insert into customercinema values(1115,'Sukdev','Chaudhary',1015,7622551288, '[email protected]',
'Sukdev12@','Male');

select * from customercinema;

UPDATE customercinema SET customer_Fname = 'K21PP' WHERE customer_id = 1111;
 3. Design Ticket Show
3.1.2. Detail of Schemas show_id number(5), has
show_date number(10),
seat_no number(5), show_start_time varchar(5),
seat has show_end_time varchar(5),
Price number(5),
Ticket_id number(5), Show_id number(5),
set_id number(5), has
Language varchar(10));
Hall_no number(10),
seat_name varchar(10),
Ticket_no number(5));
No_of_seats number(5),
CONSTRAINT sets PRIMARY
KEY (set_id)
Book Offer Discount
has

Ticket_no number(10),
Customer_id number(10)); offer_id number(5),
admin1 Movice_name varchar(10),
Sells Price number(10));
admin_id varchar(10), Customer cinema
admin_password
varchar(10));
customer_id number(10), Movie
Wor
ker customer_FName varchar(20),
customer_LName varchar(20),
Booking_ticket varchar(10),
Theater
Phone_no number(20), Booking Movie_id number(10),
Email_id varchar(20), Movie_name varchar(20),
Password varchar(20), Release_date varchar(20),
Ticket_id number(5), Customer_Gender varchar(20), Director varchar(10),
Ticket_name varchar(15), CONSTRAINT customer PRIMARY KEY Actor varchar(10));
Ticket_location varchar(10)); (customer_id));