SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

1. INTRODUCTION
SRS is a document that completely describes what the proposed software
should do without describing how the software will do it. The basic purpose of SRS
is to bridge the communication gap between the parties involved in the
development of the software SRS is the medium through which the client and the
user needs are accurately specified.

A good SRS should satisfy all the parties some thing very hard to achieve
and involves trade offs and persuasion. Another important purpose of developing
an SRS is helping the users to understand their own needs.

1.1 PURPOSE:
Main aim of developing Employee Payroll and Leave Management is to
provide an easy way not only to automate all functionalities involved managing
leaves and Payroll for the employees of Company, but also to provide full
functional reports to management of Company with the details about usage of
leave facility.

We are committed to bring the best way of management in the various forms
of EPLM. We understand that EPLM in not a product to be sold, it is a tool to
manage the inner operation of Company related to employee leave and Payroll.

1.2 SCOPE:
This Application works in Multiple PC’s installed on multiple Computers but
sharing same database by which users of different department can use it sitting at
different locations simultaneously.

But in future we can make the Application where the database will be
hosted in order to manage the all departments which will be located in different
places and by keeping domain of Application as Online.

1
1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
EPLM Employee Payroll And Leave Management
CL Casual Leave
SL Special Leave
EL Earned Leave
WO Weekly Off
SKL Sick Leave
DA Daily Allowance
SA Special Allowance
HRA House Rental Allowance
CA Convenience Allowance
EA Extra Allowance
PF Provident Fund
ESI Employee State Insurance

1.4 REFERENCES
 Programming Visual Basic .NET, Second Edition by Jesse
Liberty
 The needed requirements for this project has been obtained from the
stock by observing manual records and also gathered some of the
information by asking questions.

1.5 OVERVIEW
The following subsections provide the complete overview of the software
specifications requirements documentation for the product Employee Payroll And
Leave Management. The entire SRS is documented in view of User and the
following sub sections are arranged to give a complete outlook of the software, its
perspective, features, system requirements and users know how’s.

2
2. OVERALL DESCRIPTION
2.1. SYSTEM ENVIRONMENT

EPLM
DB

User

2.1 PRODUCT PERSPECTIVE

This software is developed specifically to cater the Technopulse employees
leave management, is totally self contained and works efficiently. It provides
simple database rather than complex ones for high requirements and it provides
good and easy graphical user interface to both new as well as experienced user of
the computer.

2.2 PRODUCT FUNCTIONS

The application functions are divided as follows
Masters:
This module helps the administrator to enter the designation and the related
description. It also helps to add the department.

Employee:
This module helps to add the details of the employee like the personal detail
and the employee detail.

Search:
This module helps to search the employee details department wise and
designation wise.

Attendance:
This module helps to different types of leave for different year. It also helps
the employee to enter their entry and exit time. Using the attendance module the
employee can also check their remaining leaves and also apply for the leave.

3
Salary:
This module helps to calculate the salary by adding the allowances and the
basic salary and by deducting the deductions based on the leaves and also the PF,
ESI. It also helps to generate the employee pay slip.

Report:
This module helps to generate the administrative reports like the Salary
Report, Attendance Report and the Employee Report which is in can be exported
to word, pdf.

2.3 USER CHARACTISTICS

Should be familiar with Computer
Should know English
Should be able to use and do according to the graphical user interface

2.4 GENERAL CONSTRAINTS

System must have windows OS installed on it.
This Application must also be installed on the system

2.5 ASSUMPTION AND DEPENDENCIES

Assumptions:
 The code should be free with compilation errors/syntax errors.
 The product must have an interface which is simple enough to
understand.
Dependencies:
 All necessary hardware and software are available for implementing
and use of the tool.
 The proposed system would be designed, developed and
implemented based on the software requirements specifications
document.
 End users should have basic knowledge of computer and we also
assure that the users will be given software training documentation
and reference material.

4
  The system is not required to save generated reports.

3. SPECIFIC REQUIREMENTS

3.1 EXTERNAL INTERFACE REQUIREMENTS

3.1.1 USER INTERFACE

The software provides good graphical interface for the front end which is self
explanatory.

3.1.2 HARDWARE INTERFACE

1) 40 GB hard disk
2) 256 MB RAM
3) Peripheral devices

3.1.3 SOFTWARE INTERFACE

Windows XP or above installed on the system.
Application Package must be installed.

3.1.4 COMMUNICATION INTERFACE

Windows Forms

3.2 FUNCTIONAL REQUIREMENTS

Masters
Designation
This sub module must accept the new Designations and allows add
designation and clear operations.
Input: The administrator must enter the designation and also enter the
description related to that designation and click on the ADD
DESIGNATION button.
Output: As soon as the user clicks ADD DESIGNATION, a message box
will be displayed “Record Inserted” and the details of the designation is
shown in data grid below

5
Department
This sub module must accept the new Departments and allows add
operation.
Input: The administrator must enter the department in the text box
and click the button ADD.
Output: As soon as the user clicks ADD it will display the message box
“Record Inserted” and the department name and the department id is
shown in data grid below.

Employee
Employee Details
This sub module accepts the personal and employee information of the
employee. It allows the ADD and EDIT operation.
Input: Here the administrator must enter all the personal details of the
employee like the code allocated to him, Full name, address, pin code,
etc... The admin must also specify his employee details like his
department (selecting the department from the combo box), designation
(selecting the designation from the combo box), basic salary, date of
join, etc... and click on the ADD or EDIT button.
Output: When the ADD button is clicked it will display the message
box “record inserted”. When the edit button is clicked it will display
“record updated”. The record will be inserted and updated as per the
user’s request.

Attendance
Leave:
Using this sub module the administrator can enter the leave type, the
number of leaves allocated for that type in different years. It contains
the ADD and UPDATE operations. Once the type of leave and the
number of leaves are entered for a particular year the same or varying
values for the same year cannot be added again but can be updated.
Input: The administrator enters the type of leave and also allocates
the number of leaves the particular year and the click on the ADD

6
 button. If the allocated leaves are to be changed then UPDATE must
be clicked.
Output: When the administrator clicks on the ADD button the
message box will be displayed as “Values Inserted”. The values which
are entered in the text box will be displayed in the data grid below. If
the values are updated then the message box displays “Values
Updated Successfully” and the updated values will be updated in the
data grid.
Attendance
As soon as the employee enters the office he should mark his
attendance. Here MARK ATTENDANCE operation is performed.
Input: Here the employee must enter his employee id and enter the
date; his entry time and his exit time and then click on the MARK
ATTENDANCE.
Output: As soon as the MARK ATTENDANCE is clicked the message
box is displayed “Attendance Marked” and the attendance for the
particular id will be entered.
Managing Leave
The employee can use this form to manage his leaves. This has the
operation MANAGE LEAVE.
Input: Here the employee enters his leave type and then enter the
number of days of leave he wants and click on the MANAGE LEAVE.
Output: The message box will be displayed as “Leave Accepted”. And
the leave entries will be entered.

Salary
Allowance:
Using this sub module the administrator can add different allowances
for each employee. It contains various operations like ADD and
UPDATE.
Input: The administrator must add the different allowances for each
employee and click on the ADD button. If he has to change the
entered details then the UPDATE must be clicked

7
 Output: The message box will be displayed as “record inserted”. All
the details entered will be shown in data grid below and if the values
are updated using the UPDATE operation then the updated values will

be displayed in the data grid.

Deduction
Using this sub module the administrator can enter various types of
deductions like PF, ESI. It contains various operations like update and
cancel.
Input: The administrator will enter the PF, ESI for the specified salary
range.
Output: The entered details will be updated and a message box will be

displayed as “Values Inserted”.

Pay Slip
Using this sub module the administrator can generate the pay slip
which is given to the employee. This pay slip contains all the details of
the employee like his name, code, basic salary, hra, da, etc… This form
contains the PRINT and GET DETAILS operation.
Input: Here the employee id is selected and the GET DETAILS is
clicked. After the complete details are obtained the PRINT button is
clicked.
Output: As soon as the GET DETAILS is clicked all the details about
the employee will be displayed like the number of leave taken, PF, ESI,

etc... When the PRINT is clicked the message box will be displayed as
“Payment record inserted successfully”.

3.3 PERFORMANCE CONSTRAINTS

Good working pc with all requirements stated above should not be
overloaded.
3.4 DESIGN CONSTRAINTS
There is no maintainability of back up so availability will get affected.

8
3.5 SYSTEM ATTRIBUTES

3.5.1RELIABILITY
This system is designed to have very simple database just to cater the exact
need of employee payroll and leave management. It is tested for all the constraints
at development stage.

3.5.2 AVAILABILITY
This system will only available till the system on which it is installed is
running.

3.5.3 SECURITY
This system is provided with authentication without which no user can
pass. So only the legitimate users are allowed to use the application. If the
legitimate users share the authentication information then the system is open to
outsiders.

3.5.4 MAINTAINABILITY
There will be no maintenance required for the software. The database is
provided by the end-user and therefore is maintained by this user.

3.5.5 PORTABILITY
The system is not portable as it is a standalone application running on
single system with no shared database.