1

TABLE OF CONTENTS

SNO. TOPIC Page No.

1.. introduction
2 CONTEXT LEVEL DIAGRAM
3 DFD LEVEL 1
4 DFD LEVEL 2
5 DATA DICTIONARY
6 USE CASE DIAGRAM
7 USE CASE DESCRIPTION
8 RISK ANALYSIS
9 ER DIAGRAM
10 DATA DESIGN
11 COMPONENT LEVEL DESIGN
12 TESTING
13 References
14 ANNEXURES

SYSTEM REQUIREMENTS SPECIFICATION

1. Introduction
 3

This document gives detailed functional and non-functional requirements for the PVR:
Online Movie Ticket Booking System. This app is basically made for providing customer an
anytime and anywhere service for booking the seat in the cinema hall and to gather
information about the movies online.

1.1 Purpose and Scope

 The main purpose of our PVR:online ticket booking system is to provide another way
for the user to buy cinema ticket. It is an automatic system.
 After inserting the data to database, staff need not to due with the order receive
through the system. In fact, there is similar system on the internet, but there is no
refund method found in the existing system.
 This system is basically aimed to provide the user the complete information of the
movie, according to which the user can book the tickets and along with can order
snacks and the refund facility provides more flexibility to the system.
 The goals of our system are:
1. To provide an anytime anyplace service for the user.
2. To minimize the number of staff at the ticket box.
3. To promote the film on the internet.
4. To increase the profit to obtain statistic information from the booking
record.

1.2 ABBREVIATIONS AND ACRONYMS

 SRS-Software Requirement Specification

 DD-Data Dictionary
 DFD-Data Flow Diagram
 User- registered customer of the system.
 Admin- person who interacts with the system.

1.3 OVERVIEW
 4

This app adopts a comprehensive approach to minimize the manual work and
schedule resources, time in a cogent manner. The software controls redundancy so that no
two users can access the same seat at the same time and transactions should be independent.

2, PROJECT DESCRIPTION

2.1 Product Perspective

1. If the actor has a role of an admin then he/she would have access to accept
user’s request and make required updation in the database register, login,
change password, payment and cancel ticket.
2. If the actor has a role of user then he/she would have access to register, login,
change password, book movie ticket, order snack, payment and cancel ticket.

2.2 System Interfaces

This system does have one interface with online payment gateway of the existing
systems.

2.2.1 System Specifications

 Hardware Requirements –
 Intel Pentium and Celeron class processor
 Processor Speed – 1.2 GHz or above
 RAM - 512 MB
 HDD - 40 GB
 Monitor-14”SVGA
 Printer
 Mouse- Normal
 Keyboard- Normal

 Software Requirements –
o Front-end Tool: - Microsoft ASP.NET 2.0
 User friendly
 5

 Low Cost Solution

 GUI feature
 Better designing aspects

o Back-end Tool: - Microsoft SQL Server 2005

 Security
 Portability
 Quality
 Efficiency
 Maintainability

o Platform: - Windows platform like: 2000 professional, XP &

Vista // windows 10

2.2 Product Functions

1 Register
Input – Name , email-id , contact No. , Password
Processing – User will be registered
Output – User’s account has been created successfully
2 Login
Input – Id Name ,Password

Processing – credentials will be checked to verify the user or admin

Output – Go to Home page

3 Book Ticket
Input – Movie name , date , time , seat type , No. of tickets
Processing – credentials of movie will be checked that desired seat is available or not
.
Output – movie will be booked
4 Order Snacks
Input – Food item ,No. of Item
Processing – snack will be check that it is available or not
Output – snack will be ordered
5 Payment
Input – Card No. , CVV No.
 6

Processing – details are verified

Output – payment done successfully
6 Send Notification
Input – none
Processing – sends conformational message
7 Cancel Ticket
Input – user Id , Password , Ticket Id
Processing – cancellation process is start by checking that it fulfill cancellation
constraint
Output – Ticket will be cancelled with/without refund .

2.3 General Constraints

 User interface is only in English. No other language option is available.
 Our system is confined to only one particular cinema hall of a particular Delhi NCR.

 Internet connection is required to use the system.

 The files in which the information regarding user’s account should be secured against
malicious deformations.

 Data should not become corrupted incase of system crash or power failure.
 User should carry their mobile phones with registered mobile number.

2.4 User Characteristics

 User uses the system to fetch information about available movies, their price,
duration, date and timings and majorly to book tickets.
 Admin manages the system and keeps it up-to-date. Admin also looks over user
requirements.

 User can also give feedback of the movie watched, in the form of ratings.

 Central server of the system must be able to handle all the incoming requests
simultaneously.
 Back up of the databases in case of hardware failure, disaster, natural calamities.
 7

2.5 Assumptions and Dependencies

 Admin is created in the system already.
 Roles and tasks are predefined.
 There is a limit of booking a movie. If the hall is houseful then user cannot book the
movie at that time.
 In general it has been assumed that the user has complete knowledge of the system
that means user is not a naive user. Any data entered by him/her will be valid.
 It depends that the one should follow the international standards for the generating the
User ID &should fill the related information in the proper format.
 Password must contain atleast 10 characters according to the rule.
 Internet is must.

3. SPECIFIC REQUIREMENTS.

3.1. EXTERNAL INTERFACES. - Payment Gateway is the external

interface.

3.1.1 USER INTERFACE

 It is a login window that requires user to enter correct ID and
password, so that after authentication of data stored in the user
database is approved as a valid user so that user enter into our
application.
 If the user does not exist, then the user must register in order to access
the system functionalities. ID and password will be stored in the
database for future login purpose.
 User login to book movie tickets by selecting movie name, date,
time, venue and number of tickets required.

3.1.2. HARDWARE INTERFACE

Various interfaces for the product could be

1. Touch screen/Monitor
2. Keypad
 8

3. Continuous battery backup

3.1.3. SOFTWARE INTERFACE

1. Any operating system.

2. JavaScript is required for highly interactive environment.

3.1.4. DATABASE INTERFACE

 All databases for the software will be configured. These databases
include movie’s details database, users’ details database and admin
database.
 The users’ details database includes user ID, password and previous
and current booking details.
 The events’ details database includes information about all listed
events, their organizers, dates, timings, venue, price per ticket and
available seats.
 The organizers’ details database includes organizers’ ID, password and
previous and current listed events’ details.

3.2 FUNCTIONAL REQUIREMENTS

 New users can see the movie details but cannot book it until they are
registered in the system.
 Registered users should be able to login to the system through the first page
of the Application.
 Registered users can change the password after logging into the system.
 No reservation for movie ticket, before 2 days can be done.
 See his/her current reservations on different movies along with the details.
 9

 Able to choose the seats which are available for a certain class like silver,
gold, platinum.
 Able to order snacks at the time of movie booking.
 Along with the snacks, user can apply coupons in order to avail discount.
 Give details about the credit card for the payment like account number, CVV
number.
 A message and mail should be sent to the concerned person about the
confirmation of the ticket to the specified mobile number.
 The login Id and password should be sent to the mentioned email address if a
new account is created.
 The system should automatically show the fare for the corresponding movies
and amount of money needs to be paid for selected seats.
 User can cancel the movie ticket anytime but with a limitation, if he/she
cancels before 3 hours of show timing than 50% money is refunded back into
his/her account otherwise only ticket will be cancelled without any refund.

3.3. PERFORMANCE REQUREMENTS

3.3.1 SECURITY:-

The Online Movie Ticket System is fully accessible to only authentic user. It
requires username and password to become member of the app.

3.3.2. RELIABILITY:-

The application is highly reliable and it generates all the updated information
in correct order.

3.3.3. AVAILABILITY:-

Any information should be quickly available from any computer to the

authorized user.

3.3.4. MAINTAINABILITY:-
 10

The application is maintainable in such a manner that if any new requirements

occur then it should be easily incorporated in an individual module.

3.3.5. PORTABILITY:-

The application is not machine specific.

3.4 DESIGN CONSTRAINTS:

 Software Language Used-

The languages that can be used for coding PVR: Online Movie Ticket System are
JavaScript and HTML.

 Database Design-
In our database design, we give names to data flows, processes and data stores.
Although the names are descriptive of data, they do not give details. Our interest is to
build some details of the contents of data flow, processes and data store. A data
dictionary is a structured repository of data about data. It is a set of rigorous
definitions of all DFD data elements and structures.

3.4.1 STANDARD COMPLIANCE

Report format: All the reports produced for this project are in compliance with the
standard templates provided in the class by the advisor.

Naming Conventions: All the documents will be named using the standard
naming conventions.

3.5 DATA FLOW DIAGRAMS

3.5.1 Context Level Diagram

 11

Figure No. 3.5.1 : Context Level Diagram

 12

3.5.2 DFD Level 1 Diagram

FigureNo, 3.5.2 : DFD Level 1 Diagram

3.5.3. DFD Level 2 Diagram

Register Module:
 13

Login Module:

Book Movie Ticket Module:

 14

Order Snack Module:

 15

Payment Module:
 16

Booking Confirmation Module

Cancel Ticket Module:

 17

3.7 USECASES
3.7.1 UseCase Diagram

REGISTER

LOGIN

BOOK MOVIE
TICKET

ORDER
ADMIN SNACK USER

PAYMENT

CANCEL
TICKET

3.7.2 UseCase Description

Register

 Purpose: It allows users to get registered i.e. to create a new account in the system.
 Actors involved: User
 18

 Precondition: none
 Post condition: User successfully gets registered and the account has been created.
 Basic Flow:
1. System requests the user to login or register.
2. User clicks on register.
3. User enters his/her name, password, email id &phone number.
4. The system validates all the details entered by the user, if correct then it
creates a new account of the user.
 Alternate Flow: If in the basic flow, the user does not enter any mandatory details
or enters any invalid information, the system displays an error message asking the
user to re-enter the information. User can either return to Home page or cancel the
registering process altogether.
 Includes: None
 Extends: None

Login

 Purpose: It allows the user to use the online movie ticket booking system –“Movie
Basket “, with the help of an already existing unique id.
 Actors involved: Admin, User
 Precondition: Users must have an already existing account in the system. In case
of no prior account, user must first register themselves and then log into the system.
 Post condition:
1. On successful login, actor gets logged into the system.
2. If the actor has a role of an admin then he/she would have access to accept
user’s request and make required updation in the database register, login,
change password, payment and cancel ticket.
3. If the actor has a role of user then he/she would have access to register, login,
change password, book movie ticket, order snack, payment and cancel ticket.
 Basic Flow: 1. User or admin enters his/her id and password.
2. Then their id and password will be checked for authentication.
 19

 Alternate Flow: If the user enters an invalid id and password then the error
message will be displayed asking the user to re-enter the details or cancel the login
process.
If the user selects the latter option, the use case ends.
 Extends: None
 Includes: None

Book Movie Ticket

 Purpose: It allows user to book movie ticket online.

 Actors involved: User
 Precondition: User has to be successfully logged into the system.
 Post condition: Movie is booked for the user and all the booking details are
displayed to him/her.
 Basic Flow: User selects the movie name, date, time, language, type of seat and
number of tickets.
 Alternate Flow: if the user selects date or time or type of seat that is already
booked then error message is displayed to the user and then user can check for that
movie on the upcoming dates.
 Extends: None
 Includes: None

Order Snack

 Purpose: It allows the user to order snacks at the time of movie booking.
 Actors involved: User
 Precondition: User has to first book movie ticket.
 Post condition: Snacks has been ordered and user can get it at the time of movie
screening in the cinema hall.
 20

 Basic Flow: User selects the type of snacks. If there is any coupons/offers user can
apply it on the total amount and then can make the payment.
 Alternate Flow: If the ordered snack is out of stock then error message is
displayed to the user and user can select other item.
 Excludes: None
 Includes: None

Payment

 Purpose: Allows the user to pay the movie ticket bill and snacks bill.
 Actors involved: Admin, User
 Precondition: User has booked movie ticket and ordered some snacks.
 Post condition: After the bill is paid online then the user gets movie ticket and
snacks payment confirmation on his/her registered mobile number as well as mail is
sent on his/her registered email id.
 Basic Flow: User pays the total bill generated through credit card or debit card.
 Alternate Flow: If the user enters incorrect CVV no. or credit/debit card no. then
error message is displayed to the user to re-enter all the details.
 Includes: None
 Excludes: None

Cancel Ticket

 Purpose: Allows user to cancel movie ticket.

 Precondition: Ticket should be booked and payment has been made.
 Post condition: If the user cancels the movie ticket before 3 hours of the movie
time then only 50% refund is being transacted into user’s account and the ticket is
cancelled otherwise only ticket is cancelled without any refund.
 Basic Flow: User raises the request for the movie ticket cancellation by providing
details such as date, time and ticket id. Admin checks the details and confirms the
request.
 21

 Alternate Flow: If the user does not cancel his/her ticket before 3 hours of the
movie time then the ticket will not get cancel.
 Excludes: None
 Includes: None
 22

RISK ANALYSIS

Risk always involves two characteristics -:

Uncertainty - The risk may or may not happen; that is, there are no 100 percent probable
risks.
Loss - If the risk becomes a reality, unwanted consequences or losses will occur.

When risks are analyzed, it is important to quantify the level of uncertainty and the degree of
loss associated with each risk.

The risk components are defined in the following manner :–

 Performance Risk – The degree of uncertainty that the product will meet its
requirements and be fit for the intendeduse.
 Support Risk – The degree of uncertainty that the resultant software will be easy to
correct, adapt, and enhance.
 Schedule Risk – The degree of uncertainty that the project schedule will be
maintained and that the product will be delivered on time.
 Cost Risk – The degree of uncertainty that the product budget will be maintained.

RISK TABLE

Risks Category Probability Impact Mitigation

Server breaks Project size 40% 2 Past experience might be
down risk considered
Data loss Project size 30% 2 Take up steps to maintain
risk backup and recovery
Security Technical 20% 3 External resources
issues(payment risk might help
must be secure)
 23

Duplication of Technical 20% 1 Once a user has selected

same seat while risk the seat & is about to
booking initiate the payment the
selected seat will be
freezed & will be visible
as booked for all the
other users for a period
of 10 mins. If the user
has not made the
payment within 10 mins
then the selected seat
gets unfreezed and will
be available to all the
other users.
 24

ER DIAGRAM
 25

DATA DESIGN

A Data Design is a collection of names, definitions, and attributes about data elements that
are being used or captured in this software project. It describes the meanings and purposes of
data elements within the context of this project, and provides guidance on interpretation,
accepted meanings and representation so that user and analyst will have a common
understanding of inputs, outputs and other project components.

TESTING

Pseudo code

String foodItem , choice;

1
Int Tickets , num , movie;

While(Login_Is_Success)
2
{

cout<<” Enter movie details “;

cin>> movie _name;

cin>>date;

cin>>Time; 3
cin>>Seat_Type;

cin>>No_Of_Ticket;

movie = Is_Movie(movie _name , date , Time , Seat_Type , No_Of_Ticket);

If( ! HouseFull(movie) )
4
{ Book_Ticket( Seat_Type , No_Of_Ticket ); 5
updateTickets(_name , date , Time , Seat_Type , No_Of_Ticket);

Cout<<”Along with you want to order snack (Y|N) “;

Cin>>choice;

6
 26

While(choice ==”yes”)

Cout<<” Enter food item”;

Cin>>fooditem; 7
Cout<<”Enter quantity”;

Cin>>num;

8 9

If(check(foodItem) && quantity(num) )

Order_Snack(fooditem , num);

Update_foodstock(fooditem , num); 10
Check =”No” ;

Else

cout<<”Enter another food item “; 11

}// end of inner while loop

Go for payment 12
}

Else
13
Cout<<” Select any other movie”;

} // end of the outer while loop

14
 27

//end of program

Thank you