DBMS PROJECT REPORT
NAME: MULTIPLEX TICKET BOOKING
GROUP MEMBERS:
TY IT BATCH: T1
PALLAVI BHARANE ..... ..............................705003
LAKSHMI CHAUDHARI............................. 705009
DEEPAL DHARIWAL ...................................705017
INTRODUCTION:
Our project basically manages the database of a multiplex, providing an interface to the user
to book movie tickets. At the front end we have used C# and at the back end SQL 2005
server. The project proceeds through a sequence of well-designed forms provided with
validations to ensure consistency, reliability and most importantly correctness of information
fed into the database.
ENTITY RELATIONSHIP DIAGRAM:
NAME
ID
RATING
U/A
MOVIE
CIP
CARD NO
G_BOOK
CREDIT_CUSTOMER
GENRE
LANGUAGE
DATE
M_S
TIME
C_S
S_BOOK
S_ID
SHOW
P_BOOK
NETBANK_CUSTOMER
NB_C
HAS
ACCT_NO
INP
SCREEN
P_TOTAL
S_TOTAL
G_TOTAL
NO
ATTIBUTES, ENTITIES, RELATIONS:
Movie information
id: The primary key for each movie
name: The name of the movie
censor: censor rating for the movie ... (U/A)
rating: critic’s rating for movie
genre: the genre of the movie
language: the language of the movie
Customer information
ip: the unique id provided to customer
mob_no:customer’s mobile no
points: the points allotted to the customer
Show information
time: time of the show
date: the date of the show
g_booked: no of seats booked in the ‘gold’ block
p_booked: no of seats booked in the ‘platinum’ block
s_booked: no of seats booked in the ‘silver’ block
id: The show id
Screen information
no: the screen no
s_capacity: the no of seats available in ‘silver’ block
g_capacity: the no of seats available in ‘gold’ block
p_capacity: the no of seats available in ‘platinum’ block
Seat information
ip: the ip of customer who has booked that seat
seat: the seat no
Credit customer information
card_no: the no of the card
card_name: the name on the card
expiry_date: the expiry date of the card
card_category: the category of card (credit/debit)
ip: the ip of customer
e-mail_id:e-mail id of customer
phone_no: phone-no of customer
points: the points allotted to that user
Net Banking customer
acc_no: the account no
bank_name: the name of the bank where account held
ip: the ip of the customer
e-mail_id: the e-mail id of the customer
phone_no: the phone no of user
points: the points allotted to the customer
Relationships:
Relationships are as shown in database diagram displayed.
SCOPE:

Our system can be implemented by means of booths (like an ATM system) placed at
various locations which the customer can access to book the tickets.

This will be extremely useful for customers who do not wish to pay the amount in
cash.

Also customers can avoid lengthy queues at the multiplexes. Besides customer has to
only access the nearest booth rather than actually going to the multiplex.

Also in a way this system can reduce the work load at the multiplex ticket counters.
IMPLEMENTATION:
 Review and Research
Firstly, after a detailed review and research of various multiplex web-sites and of
course adding our own inputs we designed the various forms in C#.
 Database creation
The next step was to create the database for the multiplex using SQL Server
Management Studio Express. (We have considered a multiplex with 3 screens with
30
Seats each with 2 screens reserved for Hindi movies and 1 screen reserved for
English movies.) Accordingly,
 we added the various data tables
 then we drew the Database Diagram linking the primary keys of related
entities and relationships.
The Database Diagram is as show
below:
 Connection
After referring the C# black book we found the code to connect the various forms to
the SQL Server.
 Coding
Once connection to the server was established began the process of coding the
various forms in C# to implement the system.
SYSTEM REQUIREMENT SPECIFICATIONS (SRS):
 Goals and Objectives
The main purpose of our ticket booking system is to provide another way for the customer to
buy cinema ticket. It is an automatic system. The goals of our system are:
o To provide a anytime various places service for the customer
o To minimize the number of staff at the ticket box
o To promote the film at the booths
o To increase the profit
o To obtain statistic information from the booking record.
 System Statement of Scope
-> General Requirements (functional)
1.
The schedule of the movies at a particular multiplex will be generated via a query
according to the date selected by the user.
2.
Each customer will be assigned a unique ip which is obtained by the concatenation
of card category, account no and show-id.
3.
A way in which the users (both customer and staff) can login to the system to
perform different operation.
4.
A way in which the customer can modify its own data.(provided by the ‘back’
button )
5.
A way in which the customer can commit order by just clicking the seat (which is
shown on the screen) and insert some card data.
6.
A way in which the staff can use the system to view the current booking status
(e.g. by DBA).
7.
The system can verify the data before transaction.
8.
The system can generate some statistic information according to booking and
ticket selling record.
->Interface Enhancements
Our web-based system needs about 9 interfaces to handle all the functions.

DBA
One of the main purposes of our system is to reduce the number of staff in the
ticket box. So, most of the job is done by the system automatically. Staff only
needs to insert new film.

Customer
To make the system more user-friendly, customer need not to enter lots of data.
An order will be commit step by step with guideline
->Major Constraints
Data concurrence
Since two or more customers may request for the same seat at the same time. So, the system
needs to remove the chance for two customer get the same seat.
Transaction
We cannot have a real bank account for the transaction. We can just simulate the process.
Compatibility
The new system need to be compatible with the existing ticket selling system(original) in the
ticket box, because the web-base system and the original system will run on the same time
and use the same database.
DESIGN AND PLANNING
We will only consider some important functions for the staff and the customer.
->Customer
The following diagram is the main page of the system; most of the customer will start using
the system from this page. This page has options for viewing movie schedule, proceeding to
book tickets, option for bulk booking and option for access to the DBA. Besides the various
movie posters provide user with information about the cast and crew of the movie.
On pressing ‘schedule’ button the following form is displayed which shows the movie
schedule for a date selected by the user.
With Home user is directed back to the Home-page and Buy leads to following form
where user selects a movie, date and time.
The continue button leads to following form which gives the customer a movie summary and
options for selecting class(i.e. platinum/gold/silver), the no of tickets to be booked.
Depending on the class selected in the previous form the other block seats are disabled (i.e.
gold and silver blocks are disabled in present case)
Also if any of the tickets are previously booked they appear unavailable (eg: seat A1 in the
above form)
The next button leads to the following form which again shows a movie summary and
provides options for customer information (e-mail id and mobile no) and payment options
(whether credit/debit card or net banking).
Validations implemented are:
1)if the ‘@’ character is missing in the text-box provided for e-mail id an ‘invalid
id’message pops up.
2)if user enters characters instead of numeric values in the textbox provided for mobile
no, an
error message is displayed. Also the no of digits in the no are limited to 10.
3)If the expiry date has already passed an error message appears and transaction does
not proceed further until valid date is entered.
4)the make payment option doesn’t proceed if ‘ agree to terms and conditions ‘clause is
left unchecked.
On successful execution user gets a message informing him of success.
Another feature that our system implements is that of of bulk-booking. when ‘bulk-booking’
option on home-page is selected following form is displayed.
1)it allows user to select the movie, date and time for bulk-booking
2)also he can book a desired block(from platinum ,gold, silver or a combination of any 2
blocks or the entire show.
3)depending on the movie and block selected total cost is displayed.
Basically there are 2 types of user: New and Registered. Registered user are given 25 pts for
every booking they make and after attaining 100 pts free tickets are offered.
Validation:
If user selects a block that has been booked a’sorry,not available’ message is shown.
The continue button leads to the following form which provides a summary of bulkbooking transaction with the total cost and an option ‘ok’ to accept the booking and proceeds
to the payment form. Also ‘back’ option provided in case user wishes to make any
modifications.
->DBA :On pressing ‘Administrator ‘ option on home page the DBA login page is displayed
which opens only on insertion of correct password. Once access is provided a report of all the
shows with the no of seats booked in each category and ordered by date is displayed.
NEED OF COMPUTERIZED SYSTEM:
A computerized system is any day preferential over manual transactions for a no of
reasons:
1)simplicity in managing data and records
2)reduction of labour use
3)reliability
4)security
5)accuracy
6)convenience
Bibliography and References:
Bibliography:
Microsoft Visual C# .NET – John Sharp & Jon Jagger
C# for Java Developers – Allen Jones & Adam Freeman
References:
1) www.e-squareindia.com
2) www.bookmyshow.com
3) www.famecinemas.com
4) www.kyazoonga.com
5) Online Tutorials for C#