System Requirement Specification

Running head: SYSTEM REQUIREMENT SPECIFICATION
System Requirement Specification
Name of the Student
Name of the University
Author’s note:

1SYSTEM REQUIREMENT SPECIFICATION
Table of Contents
Introduction................................................................................................................................2
Functional requirements.............................................................................................................2
Non-functional requirements.....................................................................................................3
Conclusion..................................................................................................................................5
References..................................................................................................................................6

2SYSTEM REQUIREMENT SPECIFICATION
Introduction
SRS or System requirements specification is a detailed description of the software
system, which needs to be developed. SRS identifies the functional and the non-functional
requirements for the system and includes use cases to describe the user interactions with the
software [1]. This report discusses about the Pay per view operation, a movie on demand
service by the Rapacious Monopoly cable company and the system requirements
specifications of the system. Using an extended set-top box interface, the user or the customer
will be able to book a movie from the available eight slots. Again, by using the cancellation
screen the customer can cancel the movie reservation. The purpose of this SRS will be to
identify the functional and non-functional requirements of the RMCC pay per view operation
system. The bandwidth and the server capacity of the system is limited so the number of
booking the system can accommodate is also restrained.
Functional requirements
The main things or the main functions that a user expects from a system software is
refer to as the functional requirements of the system [2]. Functional requirements describes
what the system should do or simply describes the behavior of the system. Use case diagram
are used to describe the user actions.
 The Pay per view operation system should be able to make a reservation for a
movie- With the help of extended set-top boxes the customer should be able to book a
slot for a movie from the available eight slots of three hours each.
 The customer should be able to choose the movie and their desired time slot-
There should be a reservation interface for the pay per view system using which the
customer could see the list of movies on their TV screens. The customer should be