Professional Documents
Culture Documents
Software Requirements Specification
Software Requirements Specification
Software Requirements Specification
0>
Software Requirements Specification Date: <dd/mmm/yy>
<Project Name>
Software Requirements Specification
Page 1
Feedback Monitoring for Hospitality Service Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.4 References
1.5 Overview
2. Overall Description
3. Specific Requirements
3.1 Functionality
3.1.1 <Functional Requirement One> 4
3.2 Usability
3.2.1 <Usability Requirement One> 5
3.3 Reliability
3.3.1 <Reliability Requirement One> 5
3.4 Performance
3.4.1 <Performance Requirement One> 6
3.5 Supportability
3.5.1 <Supportability Requirement One> 6
3.6 Design Constraints
3.6.1 <Design Constraint One> 6
3.7 On-line User Documentation and Help System Requirements
3.8 Purchased Components
3.9 Interfaces
3.9.1 User Interfaces 7
3.9.2 Hardware Interfaces 7
3.9.3 Software Interfaces 7
3.9.4 Communications Interfaces 7
Page 2
Feedback Monitoring for Hospitality Service Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
1.2 Scope
Scope for this Web app is reliable because it is saving time of users and users can get workers
online by this app. So, this app is very useful for mostly Rural and Urban areas problem.
Page 3
Feedback Monitoring for Hospitality Service Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
1.4 References
Khan, P., &Tabassum, A. (2010). Service quality and customer satisfaction of the beauty-care
service industry in Dhaka: a study on high-end women’s parlors. Journal of Business in
Developing Nations, 12, 33. Sokachaee, E. H., &Moghaddam, F. M. (2014).
The relationship between service quality and customer satisfaction: the example of CJCU library.
Journal of Information and optimization Sciences, 27(1), 193-209. Abari, A. A. F.,
Yarmohammadian, M. H., &Esteki, M. (2011).
A research study on Customer expectation and satisfaction level of Urban Clap in beauty
services: with special reference to Pune. Volume 8 Issue V, MAY/2018 ISSN NO: 2249-7455
Page 4
Feedback Monitoring for Hospitality Service Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
2. Overall Description
This section will provide the aspects of this system and the requirements. There will be below
2.4 Constraints
Regularities Policy
Regulatory Policies or mandates, limit the discretion of individual and agencies, or otherwise
compel certain types of behavior.
These policies are generally thought to be best applied when good behavior can be easily de-
fined and bad behavior can be easily regulated and punished through fine and sanctions.
Hardware Limitation
The smooth functionality of the portal mainly depends on the speed of hardware and then on
speed of the internet.
It is always advisable to be update as far as hardware is concerned. The hardware limitation
occurs if the user is still using a very low MHz processor or a RAM or less than 128Mb.This
will generally reduce the portal and also the use will waste a lot of useful time, energy and re -
source.
Page 5
Feedback Monitoring for Hospitality Service Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
We assume the user has an internet connection in order to navigate to the Current See website
and login
We depend on the correct operation between Python, Django and SQLite with the Amazon Web
Servers.
We depend on Amazon Web Services to be running at all times
Page 6
Feedback Monitoring for Hospitality Service Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
3. Specific Requirements
3.1 Functionality
3.1.1 Functional Requirement
Storage
The SQLite server has to be able to collect green button data sets
The SQLite server has to be able to output data on demand
The SQLite server has to be able to update user information
Web Interface
The user must be able to interact with the software to determine the dataset he wishes to
analyze
The user must be able to log in and out of the system
3.2 Usability
The application must be easy enough to learn so that users know how to use the product entirely on
their first try. The application must be more efficient than similar products
3.3 Reliability
System is available based on the user needs, can work properly, and do transactions efficiently
including safe data management. For invalid and malfunctioned operation, the system will restart
in order to prevent data loose as well as safe operation within 5 seconds. The system is password
protected to change things on the system.
3.4 Performance
Clicking any link on the navigation bar should take less than 1 second
Updating and saving any personal information should take less than 1 second
Displaying a different scale on any graph should take less than 3 seconds
Uploading a profile picture should take less than 5 seconds
Retrieving new and updated energy data should take less than 30 seconds
At least 1 GB Ram is used for store frequently used DATA
3.5 Supportability
The system shall allow the system administrator to add additional features. The system needs to
be cost-effective to maintain. There should be documents in requirements specification, design
and implementation and validation steps. Maintainability requirements may cover diverse levels
of documentation, such as system documentation, as well as test documentation, e.g. which test
cases and test plans will accompany the system.
Page 7
Feedback Monitoring for Hospitality Service Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
Page 8
Feedback Monitoring for Hospitality Service Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
3.10 Interfaces
3.10.1 User Interfaces
Login Page: The login page will allow users to log in to their account using their username or
email. The user will then be redirected to the home page upon successful login.
Registration Page: The registration page will provide a new user to create a Current See account
so that he or she can start using the web application. The user must enter his or her name, email,
password, and power company, in order to register with the website. An error message will be
displayed if the user does not enter in one of the fields or if one of the form fields is filled out
incorrectly.
FAQ Page: This page will provide a list of frequently asked questions that other users have
asked so that most solutions to problems can be found easily by users.
About Page: This page will provide information about the company.
Page 9