CONCEPTUAL DATABASE DISIGNE FOR MOVIE TICATING SYSTEM

Step 1 Build conceptual data model

Step 1.1 Identify entity types
Step 1.2 Identify relationship types
Step 1.3 Identify and associate attributes with entity or relationship types
Step 1.4 Determine attribute domains
Step 1.5 Determine candidate, primary, and alternate key attributes
Step 1.6 Consider use of enhanced modeling concepts (optional step)
Step 1.7 Check model for redundancy
Step 1.8 Validate conceptual model against user transactions
Step 1.9 Review conceptual data model with use

Step1.1

Entity name description aliases occurrence

Customer To store the details of Registered user Is the basic end user of
customer the system. Most of the
business is done
through them. The
viewer would book the
tickets of the desired
movie.
Payment employee
Booking ticket To store the details of booking Before going to book
payment any ticket, the viewer
should check the
availability. If the
desired number of seats
are available for a
movie, they can book
the tickets.
Movies To store the details of movies Every hall registered
movies with the system has the
information about
movies.
Movies are primary
concern of the system.
Admin To store the details of manager Is a super use of the
admin schema. The owner is
just like the admin.the
owner has all rights to
 view and modify the
data in the system.

Step1.2
Make
view payment
MOVIE Customer payment

update book

ADMIN BOOKING

ENTITY NAME MULTIPLICITY RELATIONSHIP MULTIPLICITY ENTITY NAME

Movie 1…….* view 1…...* customer
Movie 0……..* update 1….1 Admin
Customer 1……..1 Make payment 1….1 Payment
Customer 1……..* book 1……* Booking

Know we are going to check whether there is fun trap and chasm trap

a. Fun trap

Movie view customer book movie booking

Entities relationship entities relationship entities

M1  C1 B1
,
M2 C2 B2

M3 C3 B3
Here there is a problem at a c2 view two movies ,and also booking for two different tickets
so we have to restract the ER-diagram

Movie view customer book movie booking

M1 c1 M1

c2 M2

M3 c3 M3

b. Chasm trap
Admin update movie view customer

A1 M1 C1

A2 M3 C2

A3 M3 C3

M4 C4
 THE CHANGED TABLE IS

ENTITY NAME MULTIPLICITY RELATIONSHIP MULTIPLICITY ENTITY NAME

Movie 1…….1 view 1…...* customer
Movie 0……..* update 1….1 Admin
Customer 1……..1 Make payment 1….1 Payment
Customer 1……..1 book 1……1 Booking

Step 3

Identification of attributes for the entities

customer Movie booking admin Movie payment

Customer_id No_of_tickets_availa Admin_id Movie_id Transaction_no
ble
Customer_name Movie_name Admin_name Movie_name Custemer_id
Customer_mobile Ticket_no Admin_passw Movie_language Amount
ord
Customer_email Booking_date Admin_role Movie_hour Payment_date
Customer_addres Booking_time Movie_type payment_time
s
Ticket_id Movie_date

Identification of attributes for relationship

View book Make payment Update

Viewer id Book id Payment_id Admin id
Name Seat number Date Admin permission
Email date Booking id
address Transaction
number
Step 4

Determine attribute domains

Customer table

Filde_name description domain length null Multi-

valued
Customer_id Customer Int 11 No No
id number
Customer_name Customer Varchar 30 No No
full name
Customer_mobile Customer Varchar 11 No No
mobile
number
Customer_email Customer Varchar 30 No No
email
address
Customer_addres Customer text No Yes
s address

Movie booking table

Filde_name description Domain length null Multi-

valued
No_of_tickets_available Number of Int 11 no No
ticket
available
Movie_name Title of the Varchar 50 no No
movie
Ticket_no The Int 50 no No
number of
the tickets
Booking_date The date Date 50 no No
 when the time
you book
the ticket
Booking_time The time Date 50 no No
when you time
book the
ticket
Ticket_id Ticket id Varchar 11 no No
number

Movie table

Filde_name description domain length null Multi-

valued
Movie_id Movie id Int 11 No No
number
Movie_name Movie title Varchar 50 No No
Movie_languag Movie in Varchar 50 No No
e different
language
Movie_hour Movie Date time 50 No No
duration
Movie_type The type of Varchar 50 No No
move
Movie_date Date of Date time 50 No No
movie
released
Admin table

Filde_name description domain length null Multi-

valued
Admin_id Admin id Int 11 No No
number
Admin_name Admin full varchar 50 No Yes
name
Admin_passwor Admin Varchar 16 No No
d password
Admin_role Role of the varchar 50 no No
admin

Payment table

Filde_name description domain length null Multi-

valued
Transaction_no Transaction Int 25 no No
number
id Payment id Int 11 No No
number
Amount Cash Money 11 no No
amount
movie_houre Movie Date time 50 No No
duration
movie_type The type of Varchar 50 no No
the movie

Step 5

Entity name Primary key Candidate key Alternate key

Customer Customer _id Customer_address Customer_address
Customer _id Customer_ email
Customer_ email
Payment Id Transaction_no Transaction_no
id
Booking ticket Ticket _id Ticket _id Ticket_no
Ticket_no
Movies Movie _id Movie _id Movie_name
Movie_name
Admin Admin_id Admin_id Admin_role
Admin_role Admin_name
Admin_name
 Step 6

By generalization

NAME

ADRESS PERSON
ID

IS
A

ADMIN

CUSTOMER CUSTOMER ADMIN

MOBILE ADMIN
PASSWORE