Professional Documents
Culture Documents
Software Requirements Specification
Software Requirements Specification
0>
Software Requirements Specification Date: <dd/mmm/yy>
<Project Name>
Software Requirements Specification
Page 1
<Project Name> 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
<Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
Page 3
<Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
1.4 References
R.Anand G. Arun Kumar S.Murthy Department of CSE, Dhaanish Ahmed of Engineering,
Chennai, India , ‘Mitter – Bitter Monitoring SystemUsing Android Smartphone's'
Mohammed HayyanAlsibai, Hoon Min Siang ‘A Smart Driver Monitoring System Using An-
droidApplication and Embedded System’ 2015 IEEE International Conference on Control
System, Computing and Engineering, 27 - 29 November 2015, Penang, Malaysia 3.
https://talygen.com/EmployeeManagement
https://stayhome.ai/blog/employee-task-management-tool/
Page 4
<Project Name> 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
With Activity Tracking Software, Senior Managers can track Team member's attendance and
time off. They can manage working weeks of the members for a particular shift or a location.
They can also track in and out times of Team members.
2.4 Constraints
Regularities Policy
Page 5
<Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
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 6
<Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
3. Specific Requirements
3.1 Functionality
3.1.1 Functional Requirement
Storage
The mySQL server has to be able to collect green button data sets
The mySQL server has to be able to output data on demand
The mySQL 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
The reliability of the wearable device essentially depends on the software tools (and hardware
tools used for the system development. It is expected that, camera, sensor and other tools works
perfectly until their life time expires. If the user charges the device once a day, the time available
percent will be 43%, thus charging twice a day is recommended. If there is a problem with the
wearable device, according to its degree of damage, mean time to repair can change between 1-
10 days. The reliability of the web interface has also a crucial importance. In case the user needs
help, web interface should be 100% percent available at least 165 hours per week. If the web in-
terface crashes, it must be repaired in at most 30 minutes.
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
<Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
Page 8
<Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
3.9 Interfaces
3.9.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 CurrentSee 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.
Page 9