Download as pdf or txt
Download as pdf or txt
You are on page 1of 22

Case Study

On

PVR ONLINE MOVIE TICKETING


BACHELOR OF TECHNOLOGY
in
COMPUTER SCIENCE AND ENGINEERING

By
AADITYA KHANDAL
11705679
Roll No:12
Section: k17JD

School of Computer Science and


Engineering
Lovely Professional University

DECLARATION STATEMENT

I hereby declare that the case study entitled: PVR ONLINE MOVIE
TICKET BOOKING” submitted at Lovely Professional University,
Phagwara, Punjab, is an authentic work and has not been submitted
elsewhere.

I understand that the work presented herewith is in direct compliance


with Lovely Professional University’s Policy on plagiarism, intellectual
property rights, and highest standards of moral and ethical conduct.
Therefore, to the best of my knowledge, the content of this case study
represents authentic and honest effort conducted, in its entirety, by me. I
am fully responsible for the contents of my case study report.

Signature of the Candidate


Name of the Candidate: AADITYA KHANDAL

Table of Contents
1. Introduction
1.1. Purpose
1.2. Document conventions
1.3. Intended audience and reading suggestions
1.4. Project scope

2. Overall Description
2.1. Product perspective
2.2. Product features
2.3. User class and characteristics
2.4. Operating environment
2.5. Design and implementation constraints
2.6. Assumption dependencies

2. System Features
3.1. Description and priorities
3.2. Stimulus and response sequences
3.3. Functional requirements
3.4. Client/server system

4. External Interface Requirements


4.1. User interfaces
4.2. Hardware interfaces
4.3. Software interfaces
4.4. Communication interfaces

5. Other Nonfunctional Requirements


5.1. ER-diagrams
5.2. Safety requirements
5.3. Security requirements
5.4. Software quality attributes
5.5 UML(USED CASE DIAGRAM)

6. Testing
7. Flow chart
8. Future scope and further enhancement

1. INTRODUCTION
Welcome to newly designed website cinema ticket booking is a faster,
cleaner and a tad more personal website, specially designed to make
your booking experience better. Log on, navigate and find out for
yourselves and if time permits leave your valuable feedback. Customers
may view the contents of any movie show at any time and may book
any movie ticket as needed. The program automatically calculates the
subtotal and grand total. When a visitor decides to finally book the
ticket, the order information including the buyer's name, address and
billing instruction is stored in the database securely and payment has
been made. The combo booking is also provided at the time of booking
the ticket and there’s a wonderful facility of delivering the combos at
your seat when you are watching the movie. You need to register a new
user whenever you have first visited or site then for future it will be
stored in our database permanently and you can book you movie ticket
at any time you want with this username and password.

1.1. PURPOSE

The purpose of this document is to provide the software requirement


specification report for the PVR Online Movie Ticketing.

1.2 DOCUMENT CONVENTIONS

DB Data base
DDB Distributed Data base
ER Entity relationship

1.3. INTENDED AUDIENCE AND READING SUGGESTIONS

This project is the college level project and is implementing under the
guidance of college professors. This project is useful to everyone who
book movie tickets online.
1.4. PROJECT SCOPE

The purpose of the online system is to create convenient and easy-to-use


online system for passengers, trying to book online tickets in PVR. The
system is based on a relational database with its theatre management and
reservation functions. We will have a database supporting dozens of
major cities around the world as well as hundreds of theatres by various
multiplex. Above all, we hope to provide a comfortable user experience
along with the best pricing available.

2. Overall Description
2.1. PRODUCT PERSPECTIVE

A distributed Airline data base System stores the following information


as shown below:

▪ Movie details:
It includes the originating movie seats booked/available in the PVR.

▪ Customer description:
It includes customer code, name, mail id and phone number. This
information may be used for keeping the records of customer for
any emergency or for any other kind of information.

▪ Reservation:
It includes customer code number, seat number, date of booking,
timing of the show.

2.2. PRODUCT FEATURES


The major features of PVR Online Movie Ticketing as shown in below
entity–relationship model (ER model).

2.3 USER CLASS AND CHARACTERISTICS


Users of the system should be able to retrieve movie details in the given
cities with the given dates/times of movies from the database.

Make a new ticket

o Theatre Selection
o Movie Selection
o Seat Selection
o Flexible Date/time
o Confirmation
Cancel an existing reservation
View his itinerary
The Employee should have following management functionalities:

CUSTOMER FUNCTIONS.
o Get all customers who have seats reserved on a given theatre.
o Get all theatres for a given city.
o View show schedule.
o Calculate total sales for a given show.

ADMINISTRATIVE
o Add/Delete a movie.
o Add a new theatre.
o Update fare for seats.
o Update show timings.
Each show has a limited number of available seats. There are number of
theatres in city at different dates and time.

2.4 OPERATING ENVIRONMENT


Operating environment for the PVR Online Movie Ticketing is as listed
below
o Distributed database.
o Client/Server system.
o Operating System: Windows XP.
o Data Base: SQL+ Database.
o Platform: Vb.net
2.5 DESIGN and IMPLEMENTATION CONSTRAINTS

i) The global schema, fragmentation schema, allocation schema.


ii) SQL commands for above queries/applications
iii) How the response for application 1 and 2 will be generated.
Assuming these are global queries. Explain how various fragments will
be combined to do so.
iv) Implement the database at least using a centralized database
management system.

2.6. ASSUMPTION DEPENDENCIES

Let us assume that this is a distributed PVR database system and it is


used in the following application:
o A request for booking/cancellation of tickets from any source to any
theatre or show.
o Calculation fares and calculating appropriate
o Reward points for these who booked the tickets.

3. SYSTEM FEATURES

DESCRIPTION AND PRIORITY


The Online movie ticketing maintains information on theatres, classes of
seats, shows, prices and bookings.
Of course this project has high priority because it is very difficult to
book tickets across India without theatres.

▪ STIMULUS/RESPONSE SEQUENCES

▪ Search for movies in the city.

▪ Displays a detailed list of available movies and make a


“Reservation” or Book a ticket on a particular movie.

▪ Cancel an existing movie.

▪ FUNCTIONAL REQUIREMENTS

▪ DISTRIBUTED DATA BASE:

Distributed database implies that a single application should


be able to operate transparently on data that is spread across a variety of
different databases and connected by a communication network as
shown in below figure.

▪ CLIENT/SERVER SYSTEM

A client/server system is a distributed system in which

(a) Some sites are client sites and others are serer sites.
(b) All data resides at the server sites.
(c) All applications execute at the client sites.The term client/server
refers primarily to an architecture, or logical division of responsibilities,
the client is the application (also known as the front-end), and the server
is the DBMS (also known as the back-end).

4. EXTERNAL INTERFACE REQUIREMENTS


4.1 USER INTERFACES
▪ Front-end software: Vb.net version
▪ Back-end software: SQL+
4.2 HARDWARE INTERFACES
▪ Windows XP.
▪ Browser which supports CGI, HTML & Java script.

4.3 SOFTWARE INTERFACES


Software used Description

We have chosen Windows XP operating system

Operating system for its best support.

To save the PVR records, Passengers records

Database we have chosen SQL+ database.

To implement the project we have chosen

Vb.Net language for its more interactive

VB.Net support.
4.4 COMMUNICATION INTERFACES:
This project supports all types of web browsers.
We are using simple electronic forms for the reservation forms, ticket
booking etc.

5. OTHER NONFUNCTIONAL REQUIREMENTS


PERFORMANCE REQUIREMENTS
The steps involved to perform the implementation of airline data base are as listed
below.

1)E-R DIAGRAM

E-R Diagram constitute a technique for representing the logical structure


of a database in a pictorial manner. This analysis is then used to organize
data as a relation, normalizing relation and finally obtaining a relation
database.
ENTITIES: Which specify distinct real-world items in an application.

PROPERTIES / ATTRIBUTES: Which specify properties of an entity and


relationships.

RELATIONSHIPS: Which connect entities and represent meaningful


dependencies between them.
B) NORMALIZATION:
The basic objective of normalization is to be reduce redundancy which
means that information is to be stored only once. Storing information
several times leads to wastage of storage space and increase in the total
size of the data stored.
If a Database is not properly designed it can give rise to modification
anomalies. Modification anomalies arise when data is added to, changed
or deleted from a database table. Similarly, in traditional databases as
well as improperly designed relational databases, data redundancy can
be a problem. These can be eliminated by normalizing a database.
Normalization is the process of breaking down a table into smaller
tables. So that each table deals with a single theme. There are three
different kinds of modifications of anomalies and formulated the first,
second and third normal forms (3NF) is considered sufficient for most
practical purposes. It should be considered only after a thorough analysis
and complete understanding of its implications.

5.2 SAFETY REQUIREMENTS


If there is extensive damage to a wide portion of the database due to
catastrophic failure, such as a disk crash, the recovery method restores a
past copy of the database that was backed up to archival storage
(typically tape) and reconstructs a more current state by reapplying or
redoing the operations of committed transactions from the backed up
log, up to the time of failure.

5.3 SECURITY REQUIREMENTS

Security systems need database storage just like many other


applications. However, the special requirements of the security market
mean that vendors must choose their database partner carefully.
5.4 SOFTWARE QUALITY ATTRIBUTES

▪ AVAILABILITY: The movies should be available on the specified


date and specified time as many customers are doing advance
reservations.
▪ CORRECTNESS: The movies should start from correct time and
should complete at correct time.
▪ MAINTAINABILITY: The administrators and movie in chargers
should maintain correct schedules of movies.
▪ USABILITY: The movie schedules should satisfy maximum number
of customer needs.
0-Level DFD

View
View
Online
Movie
Admin Ticketing Staff

Response Response

View Response

1-Level DFD
Users

User Table

Passwor
Request
d Generate Reports
Change

Store
Sales Details
Ticket
Confirmed Bill
generat-
Reports
or
Login

User
Online
registration Users Ticket
Process
Booking

View View MOVIES

Request

Online
Movie
Details

Add/Delete

View
FLOW CHART: View

Admin
View
5.5 UML(USED CASE DIAGRAM)

6.Testing

➢ Software testing is a critical element of software quality assurance and


represent the ultimate review of specification, design, coding.
➢ The purpose of product testing is to verify and validate the various
work products viz. units, integrated unit, final product to ensure
that they meet their requirements.
“In E-ticket System for Cinema Halls we used Black Box Testing”

VALIDATIONS

➢ No record can be saved till all the necessary entries are done.
➢ Only administrator can perform sophisticated tasks like printing of
Reports, register new member and/or delete an existing member
etc.
➢ For security purposes the E-mail of user is required in case he/she
forgets his/her password and wants to retrieve that.
System Security Measures

➢ Security prompting the user for a user id and password in our


application is a potential security threat. So credential
information is transferred from the browser to server are
encrypted.
➢ Cookies are an easy and useful way to keep user-specific
information available. However, because cookies are sent to
the browser's computer, they are vulnerable to spoofing or
other malicious use. So we follow these guidelines:
Do not store any critical information in cookies. For example, do
not store a user's password in a cookie, even temporarily.

➢ Avoid permanent cookies if possible. Consider encrypting


information in cookies. Set expiration dates on cookies to the
shortest practical time we can.

7.FLOW CHART
8.Future scope and further enhancement of the
Project

Future Scope

➢ The project E-ticket System for Cinema Hall is flexible enough to


meet the requirements of the Customers. This project also has the
scope of enhancements like:

1- Home delivery of tickets may be provided.

2 -Online Booking of Purchases of eatables (cool drinks, popcorn etc.)


can be provided.

3-Corporate booking: Multimedia support for corporate


presentation can be provided. Conference facility can be provided for
corporate meetings in the hall. This will increase the profit of cinema
halls as well as the company organizing event.

4 Group booking: Any institute/company can book the tickets for


students/clients and special discount will be provided to them

End User Support

➢ The proposed system is developed in ASP.NET and SQL Server.


➢ If organization increases users, it just has to add more machines
and install the software on it, which is in the form of exe.
Security

➢ Security features are implemented. No unauthorized access the


package, as the security is implemented through login and
password.

You might also like