System Requirement Specification: Pay-Per-View On-Demand Movie

This document presents a system requirements specification (SRS) for a pay-per-view (PPV) on-demand movie service provided by Rapacious Monopoly Cable Company (RMCC). It outlines both functional and non-functional requirements for the system, which allows customers to book movies via an extended set-top box interface. Functional requirements include movie reservation, time slot selection, payment processing (credit card or cable bill), booking confirmation, and cancellation options. Non-functional requirements cover reliability, robustness, performance, maintainability, and usability, emphasizing data security, system stability under heavy traffic, and user-friendly interfaces. The report concludes that the system is useful but requires ongoing maintenance and improvements, particularly in server capacity and bandwidth, to enhance performance and accommodate a larger number of bookings. Desklib offers similar documents and study resources for students.

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

3SYSTEM REQUIREMENT SPECIFICATION
able to choose the desired movie and their desired time slot to make a reservation for
the movie.
 The customer should be able to choose the payment method, which are credit
card, and the other option is add the charges to the cable bill- After choosing the
desired movie and the time slot the system should be able to show a form for the
payment for the booking. There should be multiple payment options. One option
should be the credit card option and the other should be adding the required charges to
the cable bill. If the customer chooses, the pay by credit card option then the user will
have to provide the credit card details, the system should be able to validate the
information, and the required charges made accordingly.
 After the reservation of the movie the system should be able to provide a
confirmation number for the booking- After the successful payment, the system
should be able to provide a conformation booking number to the customer. The next
step would be to create a transit record to send the selected movies to the set top box
from where the booking originated. The system should be capable of storing all the
booking information and the transit records.
 The customer should be able to cancel the reservation before one hour of the
delivery time for the movie- If the user wants to cancel a reservation, for that
requirement, the system should have a cancellation window or option. The customer
should be able to cancel the booking through the cancellation display.
Non-functional requirements
Non-functional requirements [5] specifies the criteria using which the operations of a
system will be judged and is not related to specific behavior. Few examples of non-functional
requirements are performance, capacity, security, maintainability and many more. The

4SYSTEM REQUIREMENT SPECIFICATION
discussion on the reliability, robustness, performance, maintainability and usability of the Pay
per view system is done through this report.
 Reliability- The system will have to handle huge amount of movie booking from the
users. These bookings will be done through the extended set top box. The system will
also have to deal with customer’s transaction details or sensitive data like credit card
information. There should be strong encryption for these kind of data and the data
should be stored in a secure file system, to make the system more trustworthy and
reliable. There is an online transaction method which needs strong encryption and
protection [3]. The users will expect the movie to stream on their desired booking
time so, the users will have to rely on the system for this process. Any changes in the
time of streaming might result in user migration to another cable service.
 Robustness- As the system will deal with heavy traffic the system needs to be strong
and sturdy. There will be a lot of movie demands throughout the day and the system
will have eight slots each of three hours. There will be a cancellation option for the
service too and the data entry needs to be updated if there is a cancellation case. This
means the system needs to be stable and should be able to make the changes as
needed.
 Performance- The pay per view is a video demand service and the users will have the
option to choose the movie they want to watch. The performance should be
maintained by the system as any delay in the system will result in the abandonment of
the booking process. The system generates a list of transmit record, any kind of
changes to that list will hamper the whole system and the performance of the system.
There should be no or minimum number of transaction failures. There is one constrain
to the system though, the bandwidth and the server capacity are very less so the
system can take limited number of bookings. In order to improve this, the bandwidth

5SYSTEM REQUIREMENT SPECIFICATION
and the server capacity of the system should be increased so that the system can take
more number of orders.
 Maintainability- The system will need proper maintenance as the system will deal
with sensitive user data, transmit data, order details and other user database like the
set top box identification number from which the system will identify the order and to
which set top box it will have to transmit the movie to. In case of any cancellation, the
system needs to be updated. The cancellation should be done one hour before the
transmission of the movie. If the user fails to meet that criteria then the user will have
to pay the charges. The system can take limited booking because the lesser bandwidth
and the server capacity. With the increase of the server capacity and the increased
bandwidth the servers will require maintenance. Maintenance of the extended set top
box is also important as it will be the medium of transmission and booking for a
movie.
 Usability- The main user of the pay per view system will be the customers of the
Rapacious Monopoly cable company. The extended set top boxes will be the main
mode of communication between the users and the service providers. The reservation
fee is $5 and if the customer did not watch the movie then the charges are applied
during the transmission of the movie. The interface for the booking system should be
simple enough so that there is no confusion during any process from the user end. The
system should be implemented so that the cable operation company also do not face
any unfavorable situation.
Conclusion
The pay per view on demand movie booking system will provide on demand movie
service to the users. The users can choose what movie they want to watch and they can
choose the slot for the movie according to their convenience. Due to the limited bandwidth

6SYSTEM REQUIREMENT SPECIFICATION
and the limited server capacity the system can accept only limited number of bookings but,
this can be improved by increasing the capacity of the servers. The functional and non-
functional requirements are discussed in this report and it can be concluded that he system is
very useful but needs a lot of maintenance and improvements for better performance.

7SYSTEM REQUIREMENT SPECIFICATION
References
[1] Bahill, A.T. and Madni, A.M, “Discovering system requirements,” In Tradeoff Decisions
in System Design (pp. 373-457), 2017. Springer, Cham.
[2] Weinkamer, R. and Fratzl, P, “Solving conflicting functional requirements by hierarchical
structuring—Examples from biological materials,” MRS Bulletin, 41(9), pp.667-671, 2016.
[3] Oinas-Kukkonen, H. and Harjumaa, M, “Persuasive systems design: key issues, process
model and system features,” In Routledge Handbook of Policy Design (pp. 105-123), 2018.
Routledge.
[4] Singh, M., Sharma, A.K. and Saxena, R., “Formal Transformation of UML Diagram: Use
Case, Class, Sequence Diagram with Z Notation for Representing the Static and Dynamic
Perspectives of System,” In Proceedings of International Conference on ICT for Sustainable
Development(pp. 25-38), 2016. Springer, Singapore.
[5] Wang, T., Liang, P. and Lu, M, “What Aspects Do Non-Functional Requirements in App
User Reviews Describe? An Exploratory and Comparative Study,” In 2018 25th Asia-Pacific
Software Engineering Conference (APSEC) (pp. 494-503), 2018 December. IEEE.