<Project Name> Version: <1.

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>

Software Requirements Specification

1. Introduction
The problems faced in existing system is monitoring the employees and their progress work as
it is directly related to a productivity given by employees. To store the task codes and to
generate the report on that every day is also very complex to handle.
1.1 Purpose
The proposed system consists of many modules such as:
1. To develop a customizable admin for the system as it will be used by different companies.
2. To handle and monitor the employees with their everyday report generation.
3. To make a user-friendly web application using JavaScript.
1.2 Scope
In this world of growing technologies everything has been computerized. Large number of work
the Human workforce has increased. Thus, there is a need of system which can handle the data of
such as large number of Employees. This project simplifies the task of maintaining records
employee and organization because of its user-friendly nature. The objective of this project is to
provide approach towards the management of employee information

1.3 Definitions, Acronyms and Abbreviations

The document contains words and abbreviations related to computer science. The Terms and ab-
breviations are the following ones:
 Server: A program that awaits and fulfills requests from client programs in the same or
Other computers.
 Deep Learning: A machine learning method that stimulates the neural network in Human
brain.
 C: A high level general purpose programming language.
 Java: An object oriented programming languages that compose some of the tools we Use in
this project.
 Python: One of the most commonly used programming languages.
 Matlab: An environment and its embedded programming language mostly used for
 Mathematical calculations or machine learning purposes.
 Classifier: An algorithm used in Statistics and Machine Learning areas to divide the Data in
two or more classes.
 API: Application Program Interface

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

2.1 Product Perspective

Task manager is a software solution for project management. Its functionality allows the
manager to distribute personalized and group tasks, divide them into stages, and monitor the
implementation of all specified processes. Such software has been popular for a long time,
because it allows you to carry out general management and control over projects with less time
spent. There is no need to walk between tables and offices, as you can see everything on your
screen at any time. Task management software possesses a combination of many great functions
from interaction between colleagues to monitoring of the workflow.

2.2 Product Functions

Keeps track of time. Look for a task manager integrated into a time tracker. You can not only
set tasks, but also know how employees work, evaluate their productivity and used sites, see the
real workload of employees. In companies with hourly wages, this automates the calculation of
payments.
Provides detailed reporting. With this function, you can view information for a certain period,
calculate key indicators or predict the load on teams. Guaranteed technical support. You do
not know when you will need to integrate the task manager with the desired system, configure
reports or customize functions for your team. Please check the availability of technical support
and response times in advance.
Track Attendance

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.3 User Characteristics

Admin: Admin can be HR or Accountant. It is managing all employee details, employee salary,
Employee attendance and company profile and client.
Project manager: It is managing all project and its team and team task.
Employee: It is managing its attendance, task, and communicate with team.

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.

2.5 Assumptions and Dependencies

 We assume the user has or has access to a computer or laptop
 We assume the user has an internet connection in order to navigate to the CurrentSee website and
login
 We depend on the correct operation between Python+Django and mySQL with the Amazon Web
Servers
 We depend on Amazon Web Services to be running at all times

2.6 Requirements Subsets

 Hardware: -
 Minimum screen resolution: 1024*768
 Processor minimum: 500mhz Intel Core i5 workstation or equivalent
 Memory minimum :512mb recommended :2gb
 Disk space :850 MB of free disk space recommended: 1gb
 Software: -
 Front End Tool: - HTML, CSS Bootstrap4
 Back End Tool: - Python 3.8
 Frame work: Django Frame work 3.1
 Database – SQLite 3

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>

3.6 to improve the understanding of stakeholders and developers. Design Constraints

 Must run on Google Chrome and Firefox 18
 User must authenticate himself at login

3.6.1 Design Constraint

 Language: Python with Django, HTML5, CSS3
 Database: SQLite

3.7 On-line User Documentation and Help System Requirements

Online Help:
 Employee rise query regarding attendance & bug solution
Online User Documents:
 Employee attendance & project task record.

3.8 Purchased Components

This project has not required any parched components.

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.

3.9.2 Hardware Interfaces

Laptop/Desktop: The user may also access our software through a web browser on their desktop or
laptop. Under the assumption that the user is using a traditional computing environment, the user
may interact via mouse clicks and keyboard inputs.
3.9.3 Software Interfaces
SQL Server (MySQL community edition 5.x.x) Interface: The SQL tables will contain all the
information collected. It will be accessible by our software via the Django Interface. Data transferred
include timestamps, energy usage, user and account information, etc.
Windows/ Mac OS : Both Windows and Mac OS will interact with our web interface (via web
browser) to display the data to the user via a web browser.

3.9.4 Communications Interfaces

The communication will be through a network using an encrypted format. The user will be
accessing the web interface using HTTPS when accessing our software using a laptop/desktop on
a web browser. The user will interact with our system through our application.
Note : - This is the standard format of SRS whichever is applicable with your
project, you can include else just ignore.

Page 9