“MULTIPLEX MANAGEMENT SYSTEM”

Submitted in partial fulfillment of the requirements

for the award of the degree of

Bachelor of Computer Applications

To
Guru Gobind Singh Indraprastha University, Delhi

Guide: Submitted by:

Mr. Khalid Husain 1. Kanika Chawla (04521102009)

2. Aarti Gupta( 02221102009)

Institute of Information Technology & Management,

New Delhi – 1100 58
Batch (2009-2012)

1
 Certificate

we , kanika chawla and Aarti gupta certify that the Summer Training Project Report (BCA-355)

entitle ―MULTIPLEX MANAGEMENT SYSTEM‖ is done by us and it is an authentic work

carried out by us at Institute of Information Technology & Management. The matter embodied in

this project work has not been submitted earlier for the award of any degree or diploma to the

best of my knowledge and belief.

1. Signature of the Student 2. Signature of the student

Date:

Certified that the Project Report (BCA-355) entitled ―MULTIPLEX MANAGEMENT

SYSTEM‖

Done by the above students is completed under my guidance.

Signature of the Guide

Date:

Name of the Guide:

Designation:

Countersigned

Director

2
 ACKNOWLEDGEMENT

The making of the project ‗MULTIPLEX MANAGEMENT SYSTEM‘ involves contribution of

many people, whose invisible imprint can be felt on each and every page of this project.

We owe a great many thanks to a great many people who helped and supported us during the
writing of this summer training project. We express our gratitude to Prof S. Chaturvedi,
Director of Institute of Information Technology and Management, D-Block, Janak Puri,
New Delhi, for extending his inevitable and valuable support to us.

We humbly express a deep thank you to Mr. Khalid Husain, our Guide for the project. We
would take this opportunity to thank ma‘am for guiding and correcting various documents of
ours with attention and care. She has taken immense effort and pain to go through the project and
make necessary corrections as and when needed.

We would also thank our Institution and our faculty members without whom this project would
have been a distant reality. We also extend our heartfelt thanks to our families and well wishers.

Working under their guidance has indeed been a very fruitful experience for us.

1. kanika chawla 2. aarti gupta

(04521102009) (02221102009)

3
 TABLE OF CONTENTS

S. No. Topic Page No

1. Certificate 2

2. Acknowledgements 3

3. List of Tables 7

4. List of Figures 8

5. Chapter-1: System Introduction 9-20

1.1) Description of the organization

1.1.1 general description

1.1.2 Organizational objectives

1.1.3 Key result areas

1.1.4 Orgaisational structure

1.1.5 functions/ activities of organization

1.2) Data collection

1.2.1 table of input and output

1.2.2 storage and processing requirements

1.2.3 entities in the system

1.2.4 flow of data between entities

1.2.5 source of collection of data

A) Interview

B) Internet

4
 1.3) Project planning

1.3.1 software life cycle

1.3.2 making a table of name of task

precedence

1.3.3 gantt chart

6. Chapter-2 system analysis 21-29

2.1) Description of information system

2.1.1 functional block diagram

2.1.2 list of processes

2.1.3 list of input and output

2.1.4 list of data elements

2.1.5 catalogue of data elements

2.2) Procedures/rules/mathematical relation

Used for converting input into output

2.2.1 Decision tree/decision table or both

5
7. Chapter-3 systems requirement specification 30-48

3.1) Physical specification

3.1.1 DFD

3.1.2 ERD

3.2) Output specification

3.2.1 detailed characteristics of contents

3.2.2 list of data elements

3.3) Input specification

3.3.1 detailed characterstics of contents

3.3.2 list of data elements for each input

3.4) Validation specification

3.4.1 Description of the validation

3.5) Database specification

3.5.1 Detailed characteristics of field of each file

3.6) Processing logic

3.6.1 programme flow chart

6
 LIST OF TABLES

Table Title Page No.

2.1 Input / Output Data Description 14

2.2 Booking Table 45

2.3 Class Table 44

2.4 Collection Table 45

2.5 Movie Table 45

2.6 Ticket Table 46

2.7 Security Table 44

2.8 Theater Table 45

7
 LIST OF FIGURES

S. No. Topic Page No

1.1 Product Perspective 14

2.1 Block Diagram 23

2.2 Use Case Diagram 34

2.3 Zero Level DFD 30

2.4 One Level DFD 31

2.5 Level Two DFD 32-34

2.6 ER Diagram 36

8
 Chapter 1

(System Introduction)

9
 Chapter 1
1.1 Description Of the organization

1.1.1 General Description

A multiplex is a movie theatre complex with three screens. The largest of these complexes are
sometimes referred to as a CINEPLEX

The system is being designed to facilitate the members engaged in the booking tickets at

multiplexes. The system has a wide application in the sector of multiplexes as it can provide help

in various activities. Some of the merits of this system are:

 The system manages the whole database of the operators.

 The system helps in reducing work load & pressure upon the employees.

 The system is highly accurate and less error prone as compared to manual system.

 The system helps in a better way of management of multiplex ticket booking systems.

 The system saves lots of time and effort as compared to manual system.

 The system also helps in better storage and preservation of data and information.

 The system also helps in speedy retrieval and seeking of data with the help of queries.

 The system can develop and publish various data reports which can be used to carefully

study the whole picture.

 Overcome all the demerits of old manual system.

10
1.1.2 Organizational Objectives:
 To allow managers to reduce the work load of ticketing.
 Handling the ticket booking process.
 To manage the data of different movies.
 To control the ticket payment structure.

1.1.3 Key result areas

Key Result Areas to general areas of outputs or outcomes for which the department‘s role is
responsible.

About 80% of the department‘s work role capture in it. The remainders are usually devoted to
areas to shared responsibility

Each KRA should capture at least 5 % of work role

Sales 911.19 Mil

Income 42.81 Mil

6.84%
Net Profit Margin

Return on Equity 9.87%

2.01
Debt/Equity Ratio
Revenue/Share
16.85

Book Value/Share
5.72
Dividend Rate
1.92
Payout Ratio 225.00%

11
1.1.4 Organizational structure,

The first modern multiplex was opened in Delhi by PVR Cinemas in 1997 with technology
imported from Australia. The PVR went on to revolutionize the movie theater industry and broke
many national records in cinema exhibition in the country. Since then there has been a large
boom in multiplexes in Delhi. There are now over 20 multiplexes with more being built. Some of
these are stand alone multiplexes while others are located inside malls.

These multiplexes follow the hierarchical relationship between the owner and operator.

CHAIRMAN

CEO

GENERAL ARTISTIC
MANAGER MANAGER

MARKETING BUILDING PRODUCTION

DESIGNER
DIRECTOR MAINTANANCE MANAGER

BOX OFFICE HOUSE TECHNICAL STAGE

MANAGER MANAGER DIRECTOR MANAGER

BOX OFFICE SHOP PERFORMING ARTIST

STAFF MASTERS
ACTOR,SINGER,DANCER,
MUSICIAN

12
This multiplex ticket booking system software provides various services to the operator,

mentioned below:

 A operator account.It updates the new released movies and removes the current
movies. To allow managers to reduce the work load of ticketing.
 This software is also used for current ticket booking, advance booking and
generating the total collection amount. To manage the data of different movies.
 It also maintains the whole database of ticket To control the ticket payment structure.

1.1.5 Functions/activities of organization in reference to the information system under

study.

Multiplex Ticket Booking System:-

 Login:- The login process enters the operator information such as operator name and

password. If the operator is not registered, then the operator is not allowed to move to Next

Form. If he tries to do so an error message is displayed which says ―Wrong Operator‖.

 Movie Updating:- The operator updates the new released movies and removes the old ones.

 Ticketing:- The operator books the current available tickets for the customers, and books

advance tickets.

13
1.2 Data Collection:

1.2.1 Table of Input / output

MODULES INPUT OUTPUT

Operator operator_id, Password. Access the software
Customer Customer name, address, registration of the customers
contact no, e-mail id.
Movie Movie name, date, shows Movie seat reserved
timings.
Ticketing Ticket number , seat number, Ticket generated
movie hall number, show
timings.

1.2.2 Storage and processing requirements

Hardware

 Screen resolution of at least 800 X 600required for proper and complete viewing of screens.

Higher resolution would not be a problem

 Support for printer (dot-matrix/desk-jet/inkjet, etc. – any will do) – that is, appropriate

drivers are installed and connected printer will be required for printing of the reports.

 Standalone system or network based – not a concern, as it will be possible to run the

application on any of these.

Software

 Any window based operating system can be used (windows 95/98/2000/XP/NT/window7)

 Oracle as DBMS for database. Future release of the application will aim at upgrading oracle

10g as the DBMS.

 Visual basic 6 for coding, developing the software.

14
1.2.3 Entities in the system & their connectivity/linkages

The operator can book the ticket and can also do advance booking of the movie. On the other,

The operator can add the new movie to multiplex and can remove the same after the new movie

realise.

Processes that are performed in the software system and also tells us about the input and output

identification i.e. what is the input being given and what is the desired output.

1. Login process

 Operator will enter his/her ID and password, if valid user then he‘ll/she‘ll be logged in and

can now book tickets, update the movies, and check total collection amount.

2. Ticketing

 Operator will select the movie, date, and its timings as per customer‘s preferences. The

operator will also select the location of the seat.

3. Movie Updation

 The operator enters the new released movies and removes the old ones.

1.2.4 Flow of data between the entities

A operator account updates the new released movies and removes the current movies

This software is also used for current ticket booking, advance booking and generating the total

collection amount. It also maintains the whole database of ticket

15
1.2.5 Description of method/source of collection of data for each set of data

1.2.5.1 interview

I had survey for my project to make software on ticket booking system of multiplexes from the

operator of the Cineplex cinemas and comes to know the modules for the project:

 Ticketing: in this the operator can book the ticket and also do advance booking for the

ticket

 Movie management: in this they can update the movies.

 Collection report: in this operator can calculate the amount collected during the day.

1.2.5.2 Internet

I also use this method for the purpose of data collection. The research made, although the data
description should be factual, accurate and systematic.

1) http://www.scribd.com/doc/28843594/The-multiplex-Ltd#fullscreen:off
2) http://en.wikipedia.org/wiki

16
1.3. Project Planning:

1.3.1 Software Life Cycle Model (SDLC)

The waterfall model is a model for software development (a process for the creation of software),
which develop regularly flowing downwards (like a waterfall). The development runs through a
number of phases, namely: definition study / analysis, basic design, technical design / detailed
design, construction, testing, integration, management and maintenance. Previously, a large
software development, especially large cluttered knitting. With the advent of this new method,
the computer companies hoped to clarify in their project

The waterfall model is perfectly related to my projects, as it is the traditional way of

working in large project. The purpose of this way of working is that it divides the project into
phases. No new phase can be stared without the completion of the previous phase . which means
all the previous phases have to be appropriate for getting into the next phase. And this type of
model is good for error free working.

17
 1.3.2Precedence/order (date-wise) in which task are performed

Name of the
S NO. TOPIC / ACTIVITY DATE team member

Chapter-1: Introduction

1.1 Description of Organisation 22-6-2011 Aarti gupta

1.1.1 General description 23-6-2011 Aarti gupta

1.1.2 Organisational objectives 24-6-2011 Aarti gupta

1.1.3 Key Result Areas (KRAs) 27-6-2011 Aarti gupta

1.1.4 Organisational structure 27-6-2011 Aarti gupta

1.1.5 Functions/activities of organization in reference to the 28-6-2011 Aarti gupta

information system under study

1.2 Data Collection

1.2.1 Table of input and output 29-6-2011 Kanika chawla

1.2.2 Storage and processing requirements 1-7-2011 Kanika chawla

1.2.3 Entities in the system & their connectivity/linkages 4-7-2011 Kanika chawla

1.2.4 Flow of data between the entities 5-7-2011 Kanika chawla

1.2.5 Description of method/source of collection of data for

each set of data 6-7-2011 Kanika chawla
A) Interview
B) Internet.

1.3 Project Planning

8-7-2011
1.3.1 Software Life Cycle Model (SDLC) Kanika chawla

18
 10-7-2011
1.3.2 Making a table of Name of task Precedence/order Aarti gupta
(date-wise) in which these are performed The name of
the team member
12-7-2011
1.3.3 Gantt & other charts using MS Project Aarti gupta

Chapter-2: System Analysis

2.1 13-7-2011
Description of Information System
2.1.1 Description of the functioning of information system 13-7-2011
under study in narrative form In details. Functional Kanika chawla
‗Block Diagram
2.1.2 List of Processes included in the information system 14-7-2011
under study. Kanika chawla
2.1.3 List of Input & Output for each process identified 18-7-2011
Kanika chawla
2.1.4 List of data elements connected with each process 19-7-2011
identified Kanika chawla
2.1.5 Catalogue of data elements is to be presented in 20-7-2011
tabular form Kanika chawla

2.2 procedures/rules/mathematical relationships used

for converting input into output Aarti gupta

2.2.1 Decision tree/Decision table or both 25-7-2011 Aarti gupta

Chapter-3: Systems Requirement Specification

(SRS)
3.1 Physical Specifications
Kanika chawla
3.1.1 DFD 27-7-2011
Kanika chawla
3.1.2 ERD 29-7-2011

3.2 Output Specifications Aarti gupta

3.2.1 Detailed characteristics of contents (fields) to be 2-8-2011 Aarti gupta

included in each Output Screen and Print layouts.

3.2.2 List of data elements (comprising Field Name, Field 3-8-2011 Aarti gupta
Type, Field Size & description) for each Output

19
 presented in the tabular form.

3.3 Input Specifications

3.3.1 Detailed characteristics of contents (fields) to be 5-8-2011 Aarti gupta

included in each Input screen document.

3.3.2 2List of data elements (comprising Field Name, Field 6-8-2011 Aarti gupta
Type, Field Size & description) for each Input
presented in the tabular form .

3.4 Validation Specifications

Kanika chawla
3.4.1 Description of the validation rules to be included for 8-8-2011
input/output, wherever required

3.5 Database Specifications Aarti gupta

3.5.1 Detailed characteristic of fields of each file/table 9-8-2011

included in the database are to tabulated with Field Kanika chawla
Name, Type, and Size & Description

3.6 Processing Logic

Kanika chawla
3.6.1 1 Programme Flow Chart. 10-8-2011

20
 Chapter 2:

System Analysis

21
 2.1.1 Description of the functioning of information system under study in narrative form
in details. Functional „Block Diagram‟.

It is the study of systems — sets of interacting entities, including computer systems. This field is

closely related to operations research. It is also "an explicit formal inquiry carried out to help

someone, referred to as the decision maker, identify a better course of action and make a better

decision than he might have otherwise made.

The development of a computer-based information system often comprises the use of a systems

analyst. When a computer-based information system is developed, systems analysis (according

to the Waterfall model) would constitute the following steps:

 The development of a feasibility study, involving determining whether a project is

economically, socially, technologically and organizationally feasible.

 Conducting fact-finding measures, designed to ascertain the requirements of the system's

end-users. These typically span interviews, questionnaires, or visual observations of work

on the existing system.

 Gauging how the end-users would operate the system (in terms of general experience in

using computer hardware or software), what the system would be used for etc.

22
Block Diagram

23
2.1.2 List of Processes included in the information system under study.

1. Login process

In this process, operator can access the software by putting id and password. If id and password

is correct he/she can access the software.

2. Ticketing

In this process, the operator books the tickets for customers according to their preference. This

process also includes advance booking.

3. movie updation

24
In this process, the operator can update a movie by addition of a new release movie and deletion

of the old movies.

25
 2.1.3 List of Input & Output for each process identified

This section contains the details about all the processes that are performed in the software system

and also tells us about the input and output identification i.e. what is the input being given and

what is the desired output.

1. Login process

Input: id, password.

Process: Operator will enter his/her ID and password, if valid user then he‘ll/she‘ll be logged in

and can now book tickets, update the movies, and check total collection amount.

Output: The operator now can perform the various operations i.e. booking, cancelation, deletion

of movies.

Login
Login form Access the software
process

2. Ticketing

Input: Selecting the movie, date, show timings.

Process: Operator will select the movie, date, and its timings as per customer‘s preferences. The

operator will also select the location of the seat.

Output: This process results into generation of a movie ticket.

Generation
Ticket booking form ticketing
of movie
tickets

26
3. Movie Updation

Input: The operator updates the new released movies.

Process: The operator enters the new released movies and removes the old ones.

Output: The new movie added is now available along with its date and show timings

Movie updation
updation Updated new release
form

27
2.1.4 Catalogue of data elements is to be presented in tabular form.

INPUT/OUTPUT

NAME DATA ELEMENTS

Login  user_id

 Password.

Customer  Customer name

 address

 contact no

 e-mail id.

Movie  Movie name

 date

 shows timings.

Ticketing  Ticket number.

 Seat number

 Movie hall number

 Show timings

28
2.2 PROCEDURES/RULES/MATHEMATICAL RELATIONSHIPS USED FOR
CONVERTING INPUT INTO OUTPUT

Mathematical equations which are used in the system.

 Procedure for calculating tickets booking

( admin tax+ entertainment tax+ vat(12.5%)+ value of tickets)= actual value of

tickets

29
2.2.1 DECISION TREE

TIMINGS ACTION
TAKEN

Buy ticket at half rate

Morning show
9:00 am to 12:00pm

weekdays
9:00AM TO
12:00 PM Evening show Tickets are available at
normal rate

BUY ONE TICKET GET 1 TICKET

Vodaphone tuesday FREE ONLY FOR VODAFONE
TICKETS
CUSTOMERS
BOOKING Morning
Buy tickets at normal
show
rate

weekends

Evening show Buy tickets at double

rate

30
 Chapter -3

3.1 Physical Specifications:

3.1.1DFD

A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an

information system. DFDs can also be used for the visualization of data processing (structured

design). Following are the DFD‘s up to 2 levels for this software system.

Level Zero DFD

Ticket
Multiplex collection
Movie details Customer

operator No. of seats

Management
Report
operator
System

Level 1 DFD

31
 Enter id and
password 1.1
operator
Operator details
login

Movie Ticket
details details
1.3
1.2

Movie
updation ticketing

Movie info. Ticket info.

32
Level 2 DFD

Movie Updation Process

Operators can add/remove a movie and the changes will be made in the movie table.

33
Ticketing

Operators can Book/Cancel a seat and the changes will be made in the ticket table along with a
receipt generated

1.3.3
Produce
Generate tickets
receipts

1.3.1

Book
ticket

Ticket info
operator

1.3.2

Cancel
ticket

34
Use Case Diagrams

A use case diagram is defined by and created from a Use-case analysis. Its purpose is to present a

graphical overview of the functionality provided by a system in terms of actors, their goals

(represented as use cases), and any dependencies between those use cases.

The main purpose of a use case diagram is to show what system functions are performed for

which actor. Roles of the actors in the system can be depicted.

35
3.1.2 ERD

 SYMBOLS USED

:> ENTITIES

:> ATTRIBUTES

:> RELATIONSHIP

:> LINK

:> ONE TO ONE

RELATIONSHIP

:> ONE TO MANY

RELATIONSHIP

:> MANY TO
MANY

RELATIONSHIP

36
 M

Reserve

In

Mname
M

Mdate

Theatre
Theatre no.

total 37
3.2 Output Specifications:

3.2.1Detailed characteristics of contents (fields) to be included in each Output Screen and

Print layouts.

The Output Specifications of the Information System includes the illustration of the detailed
characteristics of contents to be included in each Output Screen and Print layouts. A Compiled
list of data element for each Output is tabulated.

OUTPUT NAME: MULTIPLEX MANAGEMENT SYSTEM FOR TICKET

BOOKING

Field Name Field Type Field Description

Size

SEAT NO number 20 Seat no. which is to be allotted.

MOVIE NAME Varchar2 15 Name of the movie

SHOW DATE date 20 Date of the show

SHOW TIME number 20 Time of the show

AMOUNT number 30 Specific amount

ENTERTAINMENT number 10 Entertainment tax paid

TAX

SERVICE TAX number 15 Service tax paid

TOTAL number 10 Total amount

38
39
3.4 Input specification

The Input Specifications of the Information System includes the illustration of the detailed
characteristics of contents to be included in each Input Screen and documents. A Compiled list of
data element for each Input is tabulated.

1. Operator Report

INPUT NAME: OPERATOR REPORT LINKED TO LOGIN PROCESS

Field Name Field Type Field Size Description

Operator ID Varchar2 15 Unique ID of operator.

Password Varchar2 20 Success or error message of login

transaction.

Visual Basic Report Layout

MULTIPLEX MANAGEMENT SYSTEM FOR TICKET BOOKING

Operator Report

Operator ID

password

40
2. Movie updation Report

INPUT NAME: ADDTION OF NEW RELEASE MOVIE

Field Name Field Type Field Size Description

INDATE date 7 Date of release of movie

OUTDATE date 7 Date of expire

MOVIENAME Varchar2 50 Name of the movie

THEATRE number On which hall movie is showing

NUMBER -

COLLECTION number Total amount collected on ths movie

Visual Basic Report Layout

MULTIPLEX MANAGEMENT SYSTEM FOR TICKET BOOKING

Movie Updation Report

Indate

Outdate

Movie Name

Theatre Number

41
Collection
3. booking ticket Details

INPUT NAME: MULTIPLEX MANAGEMENT SYSTEM FOR TICKET

BOOKING
Field Name Field Type Field Description
Size

SEAT NO. Varchar2 20 Seat no.which is to be allot.

THEATRE NO. Varchar2 15 On which theatre the movie is

movie.

SHOW DATE Varchar2 20 Date of the show

SHOW TIME Varchar2 20 Time of the show

BOOK TYPE Varchar2 30 Select the type of the booking

ticket

AMOUNT Number 20 Total amount

ENTERTAINMENTTAX Number 20 Entertainment tax paid

SERVICE TAX Number 15 Service tax paid

42
MULTIPLEX MANAGEMENT SYSTEM FOR TICKET BOOKING

Booking Report

Seat number

Theatre number

Show date

Show time

Booktype

Amount

Entertainment tax

Service tax

43
3. collection Details

INPUT NAME: MULTIPLEX MANAGEMENT SYSTEM FOR TICKET

BOOKING
Field Name Field Type Field Size Description

Movie date Varchar2 20 Movie shown

Theatre1 number 15 . Theatre number

Theatre2 number 20 Thearte number

Theatre3 number 20 Theatre number

Total number 30 Total amout

MULTIPLEX MANAGEMENT SYSTEM FOR TICKET BOOKING

Collection Report

Movie date

Theatre no.

Movie name

total

44

Entertainment tax
3.5 Database Specifications

3.5.1Detailed characteristic of fields of each file/table included in the database are to be

tabulated with Field Name, Type, and Size & Description

security table

Field Name Field Field Type Field Size constraints Description

code
Operator ID optid Varchar2 15 Cannot be more Unique ID of operator.
than 15
characters
Password pswd Varchar2 20 Cannot be less Success or error
than 10 message of login
characters transaction.

Booking table

Field Name Feild Field Type Field constrai Description

code Size nts
SEAT NUMBER. Sno. Varchar2 20 Not null Seat no. which is to be
allot.
THEATRE Threno. Varchar2 15 Not null On which theatre the
NUMBER. movie is movie.
SHOW DATE Sdate date 20 Not null Date of the show

SHOW TIME Stime date 20 Not null Time of the show

BOOK TYPE btype date 30 Not null Select the type of the
booking ticket
AMOUNT amt Number 20 Not null Total amount
ENTERTAINMENTT e.tax Number 20 Not null Entertainment tax paid
AX
SERVICE TAX s.tax Number 15 Not null Service tax paid

45
Class table

Field Field Field type Field size constraints Description

name code
class type ctype Varchar2 20 Not null Which type of class u select
rate rate number 15 Not null Rate of the class type

Collection table

Field Name Field Field Type Field Size constraints Description

code
Movie date mdate date 10 Cannot be Movie shown
more than 10
characters
Theatre1 Thre1 number 15 Not null . Theatre number
Theatre2 Thre2 number 20 Not null Theatre number

Theatre3 Thre3 number 20 Not null Theatre number

total total number 30 Not null Total amount

Movie table

Field Name Field Field Type Field Size Constraints Description

code
INDATE Indate date 7 Not null Date of release of movie

OUTDATE Outdate date 7 Not null Date of expire

MOVIENAME Mname Varchar2 50 Not null Name of the movie

THEATRE Threno. number Not null On which hall movie is

NUMBER - showing
COLLECTION Coll. number Not null Total amount collected on
- ths movie

46
Ticket table

Field Name Field Field Field Constraints Description

code Type Size
SEAT NO Sno. number 20 Not null Seat no. which is to be
allots.
MOVIE NAME Mname Varchar2 15 Not null Name of the movie

SHOW DATE sdate Date 20 Not null Date of the show

SHOW TIME stime Number 20 Not null Time of the show

AMOUNT amt Number 30 Not null Specific amount

ENTERTAINMENT e.tax number 10 Not null Entertainment tax paid

TAX
SERVICE TAX s.tax Number 15 Not null Service tax paid

TOTAL total number 10 Not null Tatal amount

Theatre table

Field Name Field Field Type Field Size Constraints Description

code
Theatre Threno. number - Not null On which hall movie is
number showing
Capacity cpcty Number - Not null Capacity of the hall

Show 1 S 1 Date 7 Not null Date of show 1

Show 2 S2 Date 7 Not null Date of show 2

Show 3 S3 Date 7 Not null Date of show 3

Show 4 S4 Date 7 Not null Date of show 4

Show 5 S5 Date 7 Not null Date of show 5

47
3.6 VALIDATION SPECIFICATION

1) Password should be in a encrypted form such as ―*****‖

2) Id should not be in the upper case.
3) Customer contact_number should not less than eight digits.
4) Ticket seat number not accept special characters. It should be in alphabetic numeric
form

48
3.7 PROGRAM FLOW CHART
Start

Login Process

Operator Login

Input Login
& password

No Successful
Login
Yes

Yes

yes
Exit

No

Movie updation Ticketing

Add movie Delete movie Book ticket Cancel

ticket

Input movie Input movie

detail details Input
Input
ticket ticket
detail Details

Movie
updating File
Ticket File

49
End