Software

Requirement
Specification: Film
Review System
Submitted by:
Deeksha Sinha(101236)
Divya Bindal(101240)
Durlabh Raghuwanshi(101241)
Gaurav Agarwal(101243)

Oshin Bhatt(101263)

[Type the company name]

[Type the company address]

[Type the phone number]

[Type the fax number]

[Pick the date]

 Table of Contents

1. Introduction
1.1 Purpose 1
1.2 Scope 1
1.3 Definitions, Acronyms and Abbreviations 2
1.4 References 2
1.5 Technologies to be used 2
1.6 Overview 3
2. Overall Description
2.1 Product perspective 4
2.2 Product Functions 6
2.3 User Characteristics 6
2.4 Constraints 6
2.5 Assumptions and Dependencies 6
2.6 Use Case 7
2.7 State Chart Diagram 9
3. Specific Requirements
3.1 Use Case Reports 10
3.2 Supplementary Requirements 10
 Software Requirements Specification
1. Introduction

1.1 Purpose

The Movie Review System (FRS) web site is intended to provide users
access to the reviews of the latest releases at the box office. They can
view trailers, songs of various films and give their comments and ratings
as well.
They can subscribe to the site so as to get updates about upcoming films,
can give their opinion through polls.
The purpose of the software requirements specification document is to
maintain all the functions and specifications of Movie Review System.
Besides it contains the detail description of all the requirements.

1.2 Scope

A user should be able to:

Browse the website and view the latest film reviews
Rate them on a scale of 5
Post Comments
View Upcoming film trailers, news feeds, song lyrics, etc.
Subscribe via e-mail to get updates
Create login account

1.3 Definitions, Acronyms and Abbreviations

Administrator: The one who manages and maintains computer systems

and software
Movie Review System(MRS): The project name.
 IEEE: Institute of Electrics & Electronic Engineering.
Server: The main computer on a netwok
SRS: Software Requirement Specification.
User: People who use the MRS website.
Web: The network of computers that form the internet.
SLA: Service Level Agreement or SLA is a formal written agreement
made between two parties, the service provider & the service recipient. It
defines the term of engagement - the fundamental rules that wil govern
the relationship.
HTTP: Hypertext Transfer Protocol is a transaction oriented client/server
protocol between a web browser & a Web Server.
HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL
(secure socket layer).
1.4 References

IEEE SRS Format

1.5 Technologies to be used
Programming languages:
HTML, XML: Hyper Text Markup Language and Extensible markup
Language are the predominant markup languages for web pages. It
provides a means to describe the structure of text-based information in a
document and to supplement that text with interactive forms, embedded
images, and other objects.
Php: PHP is a general-purpose server-side scripting language originally
designed for Web development to produce dynamic Web pages.
JavaScript: A client side scripting language used to create dynamic web
content and user interface.
Tools & Development Environment
AJAX: Asynchronous JavaScript and XML is a group of
interrelated web development techniques used on the client-side to
create asynchronous web applications .

Xampp: XAMPP is a free and open source cross-platform web

server solution stack package, consisting mainly of the Apache HTTP
Server, MySQL database, and interpreters for scripts written in the PHP
 Dreamweaver: Adobe Dreamweaver is a web development application
in which any web developer can write applications in HTML, PHP
and JavaScript.

1.6 Overview

The rest of this SRS is organized as follows: Section 2 gives an overall

description of the software. It gives what level of proficiency is expected
of the user, some general constraints while making the software and
some assumptions and dependencies that are assumed. Section 3 gives
specific requirements which the software is expected to deliver.
Functional requirements are given by various use cases. Some
performance requirements and design constraints are also given.

2. Overall Description
This section describes the functions of the projects and their aims. It also
includes the constraints and the requirements of the project .

2.1 Product perspective

Movie Review System provides a group of works with interface

environments. Also there is a database which will keep all the records
done by the user while using the page.

2.1.1 System Interfaces

Movie Review System is connected with a server database, thus no more

connection with other systems is needed. No system interface is needed
during the development of this project.

2.1.2 User Interfaces

The Movie Review System shall be web based that has a main user
interface. Format of main screen is standard and flexible. The system
shall be designed in a user friendly manner. Pages shall be connected
with each other in a consistent way. Operations done with the system
shall be repeatable. The design of the pages shall allow user to do this.
2.1.3 Hardware Interface
There is no need for any hardware interface for MRS.

2.1.4 Software Interfaces

1. The products that can be used for viewing:

A. Microsoft Internet Explorer
Source: Microsoft Corporation, the interface of the MRS is well
documented and can be found at http://www.microsoft.com
Purpose: The web browser specified above is required as the container of
the client software at the client site in order to execute the client site of
MRS.
Definition of the Interface: The Microsoft Internet Explorer is a software
that provides a flexible and reliable browsing experience with enhanced
Web privacy features for all users.
B. Google Chrome
Source: Google Chrome, the interface of the MRS is well documented
and can be found at http://www.google.com/chrome
Purpose: The web browser specified above is required as the container of
the client software at the client site in order to execute the client site of
MRS.
Definition of the Interface: Google Chrome is a software that provides a
flexible and reliable browsing experience with enhanced Web privacy
features for all users.
2. Name: Apache HTTP Server
Source: The Apache Software Foundation, the interface of the MRS
with the application system is well documented and can be found at
http://apache.org.
Purpose: In order to execute the client site of MRS, the web server
specified above is required as the provider of the client software at the
server site.
Definition of the interface: The Apache HTTP Server Project is an effort
to develop and maintain an open-source HTTP server for modern
operating systems including UNIX and Windows NT. The goal of this
project is to provide a secure, efficient and extensible server that provides
HTTP services in sync with the current HTTP standards.
2.1.5 Memory Constraints
There is no specific memory constraints for MRS.

2.2 Product Functions

User: Administrator
The Administrator is the super user and has complete control over all the
activities that can be performed. He can update the contents of the
website, change its layout, update links, database. He can delete
comments posted by users which are in any way derogatory.

User: External User

External user can browse the website for its contents like movie reviews,
trailers, lyrics, news feeds, celebrity profiles, etc. He can create a login
account to avail some other functionalities.

User: Registered User

The features available to a registered user are the same as a external
user, with the added functionality of .

2.3 User Characteristics

The user should have the basic computer using ability.
He should be cognitive of terms such as reviews, rating, gambling,
subscribe, etc.
2.4 Constraints
There is no maintainability of back up so availability will get affected.
Limited to HTTP/HTTPS.
No multilingual support.
2.5 Assumptions and Dependencies
The user must have the ability to use internet.
The user must have connected to the internet to use the system.
The users computer must be Windows 7 or later version platforms.
The accuracy of information of users is their sole responsibility.
2.6 Use Case

Use Case diagram of Administrator

Use Case diagram of Registered Users

 Given below is an overall picture of the system, as depicted in the above
use-case diagrams:

1. Administrator:
Database Management: Control the database and keep track of all
records of users
Update Website: Update contents, links on the website.
View all details: View the details of all users and control the whole
site.

2. User
View site: browse the site for its contents.
Post Comments, Rate: Give their reviews.
Subscribe: Subscribe to get regular updates.
Login: Sign up by creating a new id.
2.7 State Chart Diagram

State Chart Diagram of Posting comments State Chart Diagram of Rating

State Chart Diagram of Subscribe State Chart Diagram of Subscribe

3. Specific Requirements

[This section of the SRS should contain all the software requirements to
a level of detail sufficient to enable designers to design a system to
satisfy those requirements, and testers to test that the system satisfies
those requirements. When using use-case modeling, these requirements
are captured in the use cases and the applicable supplementary
specifications. If use-case modeling is not used, the outline for
supplementary specifications may be inserted directly into this section.]

3.1 Use-Case Reports

[In use-case modeling, the use cases often define the majority of the
functional requirements of the system, along with some non-functional
requirements. For each use case in the above use-case model or subset
thereof, refer to or enclose the use-case report in this section. Make sure
that each requirement is clearly labeled.]

3.2 Supplementary Requirements

[Supplementary Specifications capture requirements that are not

included in the use cases. The specific requirements from the
Supplementary Specifications which are applicable to this subsystem or
feature should be included here, refined to the necessary level of detail to
describe this subsystem or feature. These may be captured directly in
this document or refer to separate Supplementary Specifications, which
may be used as an enclosure at this point. Make sure that each
requirement is clearly labeled.]