SRS

On
PVR-Online Movie Ticket Booking System
Submitted by
Gutpe Sri Harsha Vardhan Reddy
Registration No: 12202079
Section: K22EM
Roll No.:12
Subject : CSE 320
BTECH
IN

Computer Science & Engineering

Under the Supervision of
Dr. Isha Batra Mam

LOVELY PROFESSIONAL UNIVERSITY

PUNJAB
April, 2023

Signature of the Faculty / Signature of the Student (with date): G.sri harsha
(01-04-2023)

1
 Software Requirements
Specification
for

< PVR-Online Movie Ticket

Booking System >

3
ACKNOWLEGMENT

I have taken efforts in this project. However, it would not have been possible
without the kind support and help of many individuals and organizations. I
would like to extend my sincere thanks to all of them.

I am highly indebted to MR ANURAG SINGH for their guidance and constant

supervision as well as for providing necessary information regarding the project
& also for their support in completing the project.

I would like to express my gratitude towards my parents & member of for

their kind co- operation and encouragement which help me in completion of
this project.

I would like to express my special gratitude and thanks to industry persons for
giving me such attention and time.

My thanks and appreciations also go to my colleague in developing the

project and people who have willingly helped me out with their abilities.

4
Table of Contents
Table of Contents ................................................................................................................ 4
1.1 Document Purpose..................................................................................................... 5
1.2 Product Scope............................................................................................................ 5
1.3 Definitions and Acronyms ......................................................................................... 5
1.4 Document Conventions ............................................................................................. 5
1.5 References and Acknowledgement ............................................................................ 6
2. Overall Description ....................................................................................................... 6
2.1 Product Description ................................................................................................... 6
2.2 Product Functionality ................................................................................................ 6
2.3 Users ......................................................................................................................... 6
2.4 Operating Environment.............................................................................................. 7
2.5 Design and Implementation Constraints ..................................................................... 7
2.6 Assumptions and Dependencies ................................................................................. 7
3. Specific Requirements ................................................................................................... 7
3.1 External Interface Requirements……………………………………………………………………………………………7

3.2 Functional Requirements ........................................................................................... 8

3.3 Behavioral Requirements ......................................................................................... 11
4. Other Nonfunctional Requirements ........................................................................... 11
4.1 Performance Requirements ...................................................................................... 11
4.2 Safety and Security Requirements ........................................................................... 12
4.3 Software Quality Attributes ..................................................................................... 12
5. DFD’s Of Zero Level, First Level, Second Level And ER Diagrams…………..12
5.1 LEVEL 0…………………………………………………………………………………………………………………………………..12

5.2 LEVEL 1…………………………………………………………………………………………………………………………………..14

5.3 LEVEL 2…………………………………………………………………………………………………………………………………..15

5.4 ER Diagram……………………………………………………………………………………………………………………………..16

Appendix A: Glossary ....................................................................................................... 18

Appendix B: Data Dictionary ........................................................................................... 18

TEST CASES…………………………………..………………………………………20

5
1. Introduction
1.1 Document Purpose

The purpose of the application is to deliver updated information of various

train running across India. It should be available for even the most novice of
computer users and run on small Spec computers. The application itself is a
complete piece of software with few dependencies on other aspects of the
environment. The application is a new website which will be given a release
number of 1.0 subject to further updating. Future release numbers will follow
the common number convention.

1.2 Product Scope

The application should be able to run on any system regardless of the

operating system or hardware; within reason. It can be accessed using a simple
internet connection on a home users desktop computer or laptop. The
application is designed for all types of users regardless of their age or
experience to perform various transactions. It must function effectively and
maintain an efficient level of service.

1.3 Definitions and Acronyms

 User- A registered individual who visits the website and owns an account
in bank.
 SQL- Abbreviation of structured query language. SQL is a standardized
query language for requesting information from a database.
 RAM- acronym for random access memory, a type of computer memory
that can be accessed randomly; that is, any byte of memory can be
accessed without touching the preceding bytes. RAM is synonymous
with main memory, the memory available to programs
 User Id – User Id must be unique and minimum 8 characters and
maximum of 15 characters.
 Password-Unique word given to each user as a secret code
 IRCTC-An authority in India that manages all about train running
everyday.

1.4 Document Conventions

Throughout the document (formatted in MS Office ‘03) font used for:

6
1.4.1 Topics are Times New Roman formatted in ‘Heading 2’ style. Font size
for headings is 18
1.4.2 Sub topics are Times New Roman formatted in ‘Heading 2’ style. Font
size for sub-topics is also 14
1.4.3 Text is Times New Roman formatted in ‘Normal’ style. Font size for text
is 12
1.4.4 Italics have been used for laying special emphasis on certain information.
1.4.5 All references to the websites used are hyperlinked in Times New Roman,
Normal + Times style and size 12.

1.5 References and Acknowledgements

 http://en.wikipedia.org/wiki/Non-functional_requirement
 http://www.irctc.com

2. Overall Description
2.1 Product Description

The product is intended to be an improvement on a previously developed

system trying to strengthen the weakness of existing online bus reservation
system. Therefore, although some features of the product will be common to
existing software, others will be unique. Speed and compatibility are two of
the intended areas to be improved allowing the application to run on
computers with small amounts of memory.

2.2 Product Functionalities

2.2.1 The application shall allow the user to lawfully and freely access his
account & perform transactions.
2.2.2 The application should inform the user which devices are connected to the
system at any one time.
2.2.3 The application will finally incorporate facilities to make it easier for the
user to access their accounts.
2.2.4 This is to provide online train information with their arrival and departure
time free of charge to anyone with internet access.

2.3 Users

The user should have basic knowledge of internet usage.

7
Operating Environment

Railway Information System shall be designed to be platform independent. The

system will be mainly designed to be used within the home, cyber cafes and
users are allowed to access all necessary tools at one place. The system will
also provide the functionality to allow the user to search a train and all its
details; therefore users should be able to be plugged into the hardware on
which the system is running. It will be supported in any web browser like
Internet Explorer 5 and above.

2.4 Design and Implementation Constraints

The database cannot be shared or passed on electronically. All rights are

reserved. Only registered users allowed. HTML, JavaScript, severs are used.
The website has been designed in English language.

2.5 Assumptions and Dependencies

The application depends upon the user having a connection to the internet in
which he/she can

Perform search for train information. When using the application it will assume
that there is enough hard disk space for the file to be saved. Full working of
railway is dependent on the availability of Internet connection.

3. Specific Requirements

3.1 External Interface Requirements

3.1.1 Hardware Interfaces

The system must allow compatible hardware devices to be connected to the

system.

8
The system shall allow transaction to be performed using some output device.
This may be through credit card, debit cards etc..
3.1.2 Software Interfaces

The system shall be compatible with all soft wares. This will allow the user of
the system to perform searching of train legally. The system shall allow
database files to be transferred to and from other applications. Thus, the
system shall incorporate a simple file transfer mechanism

3.1.3 Communications Interfaces

The system shall have an Internet connection. This will enable to perform
searching . In addition, users shall be able to use a web browser. Therefore, both
the system and devices shall use a common networking protocol. The system
shall communicate with distribution devices via a connection. This could be a
wired connection or optionally a wireless connection

3.2 Functional requirements

Use Case Name: Register

Actors: User and Administrator.

Pre Condition The new user should not have a previously owned
account.

Post Condition: The user will have registered successfully.

Scenario: 1. The User clicks on sign up.

2. The system provides the User with the
registration form.
3. The User has to fill the correct details in the form.
4. If the information is valid, User is successfully
registered.

Exception: Occurs when the user has input an invalid entry into the
form.

9
 Can also occur if the user has chosen a ID already owned
by an existing user.

Use Case Name: Login

Actors: User and Adminstator.

Pre Condition: The actor should be a registered user.

Post Condition: The user shall be shown the railways home page.

Scenario: 1. The User clicks on the link to Sign In.

2. The User enters username and password.
3. The username and password are validated by the
Account Manager.

4. If the username and password are valid then the

User is taken to his/her account.

Exception: When the user has input ID and password that do not
match.

Use Case Name: Update account

Actors: User

Pre Condition: Before the updation of the account, the user must
perform the Login.

Post Condition: The account will be updated successfully..

Scenario: 1. The user signs in..

2. The User updates the account.

10
Exception: Server is down

Use Case Name: Browse

Actors: User, Administrator

Pre Condition The User should be visiting the website

Post Condition: The User returns to the homepage of the website

Scenario: 1. Links will be provided on the home page for the

user to navigate to any part of the website.
2. The User can also browse using the link of
‘sitemap’.

Exception: Server is down.

Use Case Name: Sign Out

Actors: User, Bank

Pre Condition The User should be signed in to his/her account

Post Condition: The User returns to the homepage of the website

Scenario: 1. User/Bank clicks on the ’Sign Out’ link.

2. After successfully signing out user is taken to
the home page.

Exception: Server is down or login session has expired

11
3.3 Behavioural requirements

Login

Register
Update
Browse account
Media content
User

purchase

Server

Sign Out

Registered Unregistered

User User

4. Other Nonfunctional Requirements

4.1 Performance Requirements

The application must have a minimum processor speed so that there are some
restrictions on what type of computer can use it. However this will be as small
as possible to enable a broad range of clients to use the application. From
studies it can be seen that speed was a common issue while distributing and
performing transaction. The system must also aim to use minimum hard disk
space yet keep the quality of the available facility as high as possible

12
 4.2 Safety and security Requirements

Information of users such as IP addresses will be kept private so that third

parties cannot gain access to this personal information in order to keep within
the Data Protection Act.

4.3 Software Quality Attributes

These are a variety of constraints that might affect the user or system. This is to
enable that reliability is always at a high level; sometimes users could not
connected to the internet due to firewalls.. Another interoperability requirement
is that the system should allow any storage device to connect to the system and
enable the distribution of banking facility. The usability requirement is that
there should be a help guide within the new system so that the time that new
users can soon understand the system; however the system will be simple and
therefore self-explanatory. The system should remember the last transaction on
the system so that users can manipulate the program easily and efficiently.aqq

5. DFD’s Of Zero Level, First Level, Second Level And

ER Diagrams
5.1 Zero Level
A data-flow diagram is a way of representing a flow of data through
process or a system (usually information system. The DFD also provides
information about the outputs and inputs of each entity and the process
itself. A data-flow diagram has no control flow — there are no decision
rules and no loops. Specific operations based on the data can be
represented by a flowchart
The context diagram is an alternative name for the Level 0 DFD
Diagram for Online Movie Ticket Bookin g System. Users, the
main process, and data flow make up its parts. Also, the project
concept is demonstrated using the single process visualization .

13
DFD Level 0 shows the entities that interact with a system and
defines the border between the system and i ts environment. This
diagram also depicts the online movie booking system at a high
level.

The illustration presents the main process in a single node to

introduce the project context. This context explains how the
project works in just one look. The user feeds data into the
system and then receives the output from it.

In addition to this, you will perceive through the diagram that

there is already the presence of data flow. Though the process is
very general, the flow of data is clear. Nevertheless, just m odify
this diagram to meet the other requirements and include other
matters regarding movie ticket booking.

14
 5.2 First Level
The “detonated view” of the context diagram is Online Movie
Ticket Booking DFD Level 1. Its function is to deepen the
concept derive from the context diagram.

Specifically, level 1 shows the broader details of Online Movie

Ticket Booking System DFD Level 0. This is to clarify the paths
(flow) of data and its transformation from input to output.

The designed diagram portrays four different scenarios: customer

information management, booking records management, booking
status monitoring, and transaction management.

Firstly, the flow of data starts from the ticketing personnel and
buyers. Then the system caters to the transaction. Th is idea was
based on ticket booking processes or transactions.

You can also see the data store used or the database. The
database is also used in storing users’ data inputs. Then it serves
as the source of outputs.

15
 5.3 Second Level
Level 2 DFD for Online Movie Ticket Booking System is also
the highest abstraction of the data flow diagram. This level also
broadens the idea from the DFD level 1. It includes the sub -
processes from level 1 as well as the data that flows.

However, not all of the processes in th e project must have sub-

processes. Only provide this diagram if needed. As long as your
previous diagrams were clear and precise, this level is not
required.

16
You can add more to this and it is up to you how will you create
your data flow diagram. Also, con sider the data flow included
and be precise with your information.

5.4 ER Diagram
This ER diagram for online movie ticket booking represents the entity of the
movie ticket booking system. This ER diagram for online movie ticket booking
primarily represents data objects and their relationships. The entity-relationship
diagram of an online movie ticket booking system depicts database tables and
relationships such as movie, customer, cinema, screen, etc. The main entities of

17
the online movie ticket booking system are the movie booking website, the
customer, the movie, the Booking, the movie show, the cinema, the screen, and
so on. Each entity has a primary key as well as a unique key. Movie tables store
all movie-related data, customer table stores all customer-related data, and
movie show store all movie show-related data.

18
Appendix A: Glossary
(an alphabetical list of terms)

1. Connoisseur-A person with expert knowledge or training.

2. Compatibility-Capable of orderly, efficient integration and operation with
other elements in a system with no modification or conversion required.
3. HTML-A markup language used to structure text and multimedia documents
and to set up hypertext links between documents, used extensively on the World
Wide Web.
4. Interface- The point of interaction or communication between a computer and
any other entity, such as a printer or human operator.
5. Java scripts-JavaScript is a scripting language most often used for client-side
web development. It is a dynamic, weakly typed, prototype-based language with
first-class functions. It is easier for non-programmers to work with. The
language is best known for its use in websites (as client-side JavaScript).
6. Novice-a person who is new to the circumstances, work, etc., in which he or
she is placed; beginner.
7. Protocol- A set of standardized procedures for transmitting or storing data,
especially those used in regulating data transmission between computers or
peripherals.
8. Sophisticated- Having acquired worldly knowledge or refinement, complex
and using advanced technology
9. SRS-System Resource/Requirement Specification.

Appendix B: Data dictionary

A data dictionary is a collection of descriptions of the data objects or

items in a data model for the benefit of programmers and others
who need to refer to them

User entity

Attribute Type Description Constraint

Username Alphanumeric Name of user Primary Key

19
 Password Alphanumeric Password set by the Not less than six
user for login characters

Email Char Address of valid email

Address account of user

Age Number Age of the user 18 years and above

Name Char Full name of the user Less than 30 characters

Store entity

Attribute Type Description Constraint

Username Alphanumeric Name Store Primary Key

Password Alphanumeric Password set Not less than six

characters

Email Char Internet address

Address

Age Number Age of the Store 18 years and above

Name Char Full name of the Store Less than 30 characters

20
 Project Name: PVR Online Movie Ticket Booking System

Test Case Template

Test Case ID: PVR_01 Test Designed by: sri harsha vardhan

Test Priority (Low/Medium/High): Med Test Designed date: 29-03-2023

Module Name: PVR-Online Movie Ticket Test Executed by: sri harsha vardhan

Test Title: Verify login with valid username and password Test Execution date: 30-03-2023

Description: Test the ‘PVR-online movie ticket’ login page

Pre-conditions: User has valid username and password

Dependencies:

Step Test Steps Test Data Expected Result Actual Result Status (Pass/Fail)

User=gutpeharsha@gmail.co
1 1 Navigate to login page m User should be able to login User is navigated to Pass

User should be able to navigate to As Expected Pass

2 Provide valid username @harsha123 dashboard

3 Provide valid password Shvr123 It should be login successfully As Expected Pass

4 Click on Login button Values can be entered It should be redirected to login page As Expected Pass

Post-conditions:

User is validated with database and successfully login to account. The account session details are
logged in database.

21