1.
Introduction
1.1 Purpose 1.2 Definitions, acronyms, abbreviations 1.3 Scope 2. Functional Requirements
2.1 Functional requirements 1 2.2 Functional requirements 2 2.3 Functional requirements 3 2.4 Functional requirements 4 2.5 Functional requirements 5
3. Nonfunctional Requirements
3.1 Performance Requirements 3.2 Safety Requirements 3.3 Security Requirements
4. Constraints
4.1 Availability 4.2 Security 4.3 Maintainability 5. Uml Diagram
1. INTRODUCTION 1.1 Purpose: This document is prepared in order to determine a software requirement specification for NETFLIX. NETFLIX is a social video streaming website on which people can watch the videos, share videos, like/dislike and comment on the videos etc. In order to gain an overview about the report, firstly, the purpose and scope of this document will be given, and the overall description of NETFLIX system is followed. In addition to these, system feature such as uploading video, watching video, sharing video, subscribe etc. are described deeply. After mentioning about the introduction of the websites, the specific requirements will be addressed for it. In the final part, functional and non-functional requirements will be addressed.
1.2 Scope: The
name of the website is NETFLIX. NETFLIX is a social video streaming
website that use by people. The aim of NETFLIX is to provide video to the users about their search and subjects. The users of NETFLIX can watch TV shows, Movies etc. They also download, add to list and like/dislike the videos. Moreover, users can also watch video of any categories such as music, Trending, Documentaries etc. By using this website people can get all the t ype of movies and shows regarding life, business, hobbies, skill etc.
2. Specific Requirement: 2.1 Functional Requirement: The functional requirements are organized in two sections First requirements of the Local User and second requirements of Standard User.
2.1.1 Requirements of the User: The requirements for the local user are organized in the following way General requirements, requirements for authorization, and requirements for a performing transaction on video.
FR1:- Watch video Input: User select and watch video. Output: Video select and play. Processing: Video is select and start star t buffered by Front end.
FR2:-Search Video Input: User can type name of video/Movie. video/Movie. Output: Name of video/movie will found or not found and displayed. Processing: Name of movie/video check by database.
FR3:- Like OR Dislike Video Input: Video can be like/dislike by User using button. Output: Video will liked or disliked and displayed. Processing: After pressing the button, database add like by user and store the like in database.
FR4:-Share video Input: User can share video in other social service website by pressing share button Output: The video will be share or not share. Processing: Details of other social website account is verified by database and and transfer/share the video page or website link
FR5:- Full Screen View Input: User can watch full screen video by pressing full screen option button Output: Video is displayed in full screen resolution Processing: after pressing button they command front end to view in full screen mode.
3. External Interface Requirement
3.1 Software Interface: The software will use hyperlink to allow the user to
open websites in their default web browser.
3.1.1
Server site requirement:
Unix/Linux operating system with 32/64bit support
SQL Database.
3.2 Operating Environment: The system will be portable. This means it will
work across different operating systems s ystems including Microsoft Windows and Mac OS and a range of Linux platforms.
Any device like desktop, laptop, Mobile, Tablet etc.
Any version of Google Chrome, Firefox, MS Edge, Safari, or Opera.
Any PlayStation, Xbox etc.
Internet connection with 1.5+ Mbps
.
4. General Constraints:
Validate Login
4.1 Validate Login Credentials:
Validate Username Validate Password
4.2 Validate Server Request:
Validate sever can handle request Validate user can access or online. Validate server down state.
4.3Availability: 4.3 Availability: The software and its resources must be available to the user at each and every point of time. time.
4.4 Security: The software must be secured enough to keep user’s details confidential. 4.5Maintainability: 4.5 Maintainability: The software must be maintained maintained properly in order to avoid inconvenience inconveni ence to the user.
