Software Requirement Specification: Employee Tracking System

Software Requirement
Specification
for
EMPLOYEE TRACKING SYSTEM

Content
1 INTRODUCTION................................................................................................................................................1
1.1 PRODUCT SCOPE................................................................................................................................1
1.2 DEFINITIONS, ACRONYMS AND ABBREVIATIONS.......................................................................1
1.3 DOCUMENT CONVENTIONS.................................................................................................................1
2 OVERALL DESCRIPTION...............................................................................................................................2
2.1 PRODUCT PERSPECTIVE.............................................................................................................................2
2.2 PRODUCT FUNCTIONALITY..........................................................................................................................2
2.3 USERS AND CHARACTERISTICS..................................................................................................................3
2.4 OPERATING ENVIRONMENT.........................................................................................................................3
2.5 DESIGN AND IMPLEMENTATION CONSTRAINTS..........................................................................................3
2.6 USER DOCUMENTATION..............................................................................................................................4
2.7 AsSUMPTIONS AND DEPENDENCIES...............................................................................................4
3 SPECIFIC REQUIREMENTS...........................................................................................................................5
3.1 EXTERNAL INTERFACE REQUIREMENTS.........................................................................................5
3.2 FUNCTIONAL REQUIREMENTS......................................................................................................7
3.3 BEHAVIOR REQUIREMENTS......................................................................................................... 8
4 OTHER NON-FUNCTIONAL REQUIREMENTS..........................................................................................9

4.1 PERFORMANCE REQUIREMENTS.................................................................................................. 9
4.2 SAFETY AND SECURITY REQUIREMENTS....................................................................................... 9
4.3 SOFTWARE QUALITY ATTRIBUTES................................................................................................9
APPENDIX A-DATA DICTIONARY........................................................................................................................11

APPENDIX B-PROJECT LOG................................................................................................................................12
Software Requirements Specification for Employee Tracking System
Revisions .
Version Primary Description of Version Date
Author(s) Completed
01 M. Azaz This document contains the system 24/11/2017
M. Ali Khan requirements specifications for the
application "Employee Tracking
Ahsan Zubair System"
Software Requirements Specification For Employee Tracking System Page1
1 Introduction
1.1 Product Scope:
Employee Tracking System has the capacity to Monitoring Employee Activity, mark their
attendance, check organizational resource usage, their personal details and salary details.
In which organization engage in employee monitor to track performance, avoid legal
liability and address other security concerns.
1.2 Definitions, Acronyms and Abbreviations:

Term Definition
App Application
User Users of the Application
API Application Programming Interface
1.3 Document Conventions:

Formatting conventions:
Name Convention
Font Arial,12 point
Heading 1 Bold,16 point
Naming Convention:
• Terms requiring explanations are explained in "()" in front of the term.

• Abbreviations are written in Upper case letters.
• References definitions/statements are numbered as " [1]" in subscript
2 Overall Description
2.1 Product -Perspective:
2.2 Product Functionality:

 Admin can:
• Access system with admin id, password.

• Add,remove employee and employee details.
• View location,images of employee by entering employee id.
• View salary details of employee.
• View weekly employee reports.
• Receive alarm on abnormal behavior of employee.
• Change employee password.
 Employee Can:
 Access system using id,password.

 Add personal details.
 View personal details.
 HR Manager can:
• Add ,remove employee.

• View location, images of employee by entering employee id.
• View salary details of employee.
View weekly employee reports.
2.3 Users and Characteristics:

• Users: The users use the application in following way:
• App Administrator (Server): Admin will open the application and use employee id,
password in order to see location, resource usage of employee, their salary details ,
weekly reports.
• Employee Side: Employees can access the app using id, password provided to
them by admin. They can add personal details and view profile.
2.4 Operating Environment:

Hardware Platform: PC, Android device
Operating System: Windows, android os.
Versions: Windows 7, windows (8) (8.1), windows 10, android version 4.0
and onwards.
2.5 Design and Implementation Constraints:

2.5.1 Hardware Constraints:
• Memory Constraint:
At least 1GB Ram will be sufficient.
• Device Constraint:
Application is only designed for android devices.
2.5.2 Language Constraint:
We will use php/css/htm/java/ajax/ .net framework for the development.
2.5.3 Implementation Constraints:
Application will require a working internet connection and GPS service of employee mobile
device.
2.5.4 Time Constraint:
This application is our Final year project hence we have to complete it within the
prescribed framework of two semesters, 30 percent will be delivered in this semester.
2.6 User Documentation:

3 to 4 page document of user manual will be provided along with the application to let the
admin know:
 Standardization/Constraints.
 How to use the application
2.6.1 Software Interfaces:
Operating System Windows:Android os

Version Windows 7and higher:Android
4.0 and onwards
2.7 Assumptions and Dependencies:
App will require internet,GPS service of the employee device.

3 Specific Requirements
3.1 External Interface Requirements:

 User Interfaces:
App will contain the following interfaces:
• Main Screen
• Admin interface
• HR Manager interface
• Employee interface
 Hardware Interfaces:
• PC’s
• Laptops
• Android device
 Software Interfaces:
• windows Operating Systems

• Android screen.
 Communications Interfaces:
 Our Application is installed on user android device,and admin can view

employee location and resource usage during work hours.
3.2 Functional Requirements:

• Add Employee:
Description and Priority:

Admin,HR Manager can add employee using id,password.
Priority = High
Stimulus/Response Sequences
• Stimulus: Server can request for adding employee.
• Response: System acknowledges the user request and add employee details to
database.
• Remove Employee:

Admin,HR Manager can remove employee from the database..
Priority = Normal.
Stimulus/Response Sequences:
• Stimulus: Server can request to remove employee.
• Response: System acknowledges the user request and removes employee and
his/her details.
• Login:

Admin or HR Manager will generate an id and password which will help employees to login
and connect with app on android device.
Priority = High
Stimulus/Response Sequences:
• Stimulus: Server can request for Login to profile.
• Response: System acknowledges the user request and display profile page
screen.
• View location:
Admin,HR Manager can view employee location along at the spot pictures of employees.
Priority = High
• Stimulus: Server can request for employee location and pictures.
• Response: System acknowledges the user request and provides location and
pictures of employees.
• View salary:
Admin,HR Manager can view employee salary details.
Priority = Normal
• Stimulus: Server can request to show employee salary details.
• Response: System acknowledges the user request and shows the details of
employee salary to admin,hr manager.
• Mark attendance:
Admin,HR Manager can view employee attendance marked by the system.
Priority = High
• Stimulus: Server can request to show employee attendance details.
employee attendance to admin,hr manager.
• View report:
Admin,HR Manager can view employee weekly report.
Priority = Normal
• Stimulus: Server can request to show employee weekly activity details.
employee weekly activity to admin,hr manager.
3.3 Behaviour Requirements:

4 Other Non-Functional Requirements
4.1 Performance Requirements:

Minimum employee input
Quick Response Time
Efficient tracking of location and resource usage
4.2 Safety and Security:

Application isn't creating any safety or security hazards for the user because it will not be
critical in the user operating environment.
4.3 Software Quality Attributes:

Reliability:
Human Factor:
This Application will be for admin,hr managers (to oversee user activities during work
hours on their computers or any web based device) and for the employee on their
android device.
• Keep the text and icons visible enough.

• Human best visible colors will be used while designing interface.
• For notifications and warnings a sound will be conveyed.
Portability:
Operating System:
Product is being built web-based and android, all the later versions provide a backup
portability.
Robustness:
Application will be made robust by keeping the programming cost of each function
minimum. Automatic sending location and manually sending location will be efficient,
and response time of application to be within the prescribed limit.
Extendibility:
The application should be easy to extend. The code should be written in a way that
favors implementation of new functions. In order for future functions to be implemented
easily to the application.
Testability:
Test environments should be built for the application to allow testing of the applications
different functions. Application will be tested on a real device with all required features.
Response Time:
Applications response time will be kept minimum by using efficient communication

strategies. The Application will be synchronous while the application starting and
setting up time should be less than 10 seconds.
5 Appendix A-Data Dictionary
Entity Description
employeeid Id of employee.
latitude Latitude co-ordinates of employee.
longitude Longitude co-ordinates of employee.
time Time of day.
date Date.
battery Battery level of employee device.
signal strength Signal strength of network of employee

device.
gpsStatus Either enabled or disabled on employee

device.
loginTime Login time of employee.
logoutTime Logout time of employee.
loginDate Date of login.
pictureUrl url of picture taken at login time.
salary Salary of employee.
City City of employee.
address Address of employee.
postalCode Postal code of city.
password Password.
hourlyRate Hourly salary rate.
phoneNum Phone number.

6 Appendix B-Project Log
PROJECT LOG
Project Title: Employee Tracking System

________________________________________________________________________
_____
Supervised By: Muhammad Tariq Baloch

________________________________________________________________________
___
Students Names: Muhammad Ali Khan

Muhammad Azaz Manzoor
Ahsan Zubair
________________________________________________________________________
_

Software Requirement Specification: Employee Tracking System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirement Specification: Employee Tracking System

Uploaded by

Copyright:

Available Formats

Software Requirement

EMPLOYEE TRACKING SYSTEM

4 OTHER NON-FUNCTIONAL REQUIREMENTS..........................................................................................9

APPENDIX A-DATA DICTIONARY........................................................................................................................11

1.2 Definitions, Acronyms and Abbreviations:

1.3 Document Conventions:

• Terms requiring explanations are explained in "()" in front of the term.

2.2 Product Functionality:

• Access system with admin id, password.

 Access system using id,password.

• Add ,remove employee.

2.3 Users and Characteristics:

2.4 Operating Environment:

Operating System: Windows, android os.

2.5 Design and Implementation Constraints:

2.5.2 Language Constraint:

We will use php/css/htm/java/ajax/ .net framework for the development.

2.5.3 Implementation Constraints:

2.6 User Documentation:

2.6.1 Software Interfaces:

Operating System Windows:Android os

2.7 Assumptions and Dependencies:

App will require internet,GPS service of the employee device.

3.1 External Interface Requirements:

App will contain the following interfaces:

• windows Operating Systems

 Our Application is installed on user android device,and admin can view

3.2 Functional Requirements:

Description and Priority:

Description and Priority:

Description and Priority:

Admin,HR Manager can view employee salary details.

Admin,HR Manager can view employee attendance marked by the system.

Admin,HR Manager can view employee weekly report.

3.3 Behaviour Requirements:

4 Other Non-Functional Requirements

4.1 Performance Requirements:

Quick Response Time

Efficient tracking of location and resource usage

4.2 Safety and Security:

4.3 Software Quality Attributes:

• Keep the text and icons visible enough.

Applications response time will be kept minimum by using efficient communication

5 Appendix A-Data Dictionary

latitude Latitude co-ordinates of employee.

longitude Longitude co-ordinates of employee.

time Time of day.

battery Battery level of employee device.

signal strength Signal strength of network of employee

gpsStatus Either enabled or disabled on employee

loginTime Login time of employee.

logoutTime Logout time of employee.

loginDate Date of login.

pictureUrl url of picture taken at login time.

salary Salary of employee.

City City of employee.

address Address of employee.

postalCode Postal code of city.

phoneNum Phone number.

6 Appendix B-Project Log

Project Title: Employee Tracking System

Supervised By: Muhammad Tariq Baloch

Students Names: Muhammad Ali Khan