A Software requirements specification

On

Leave Management System

Mentor: Submitted by:

Mrs. Sanju Choudhary Ajay Gupta (18ESKIT007)

Associate Prof.-1 Akshita Dalmia (18ESKIT010)
Apoorva Dubey (18ESKIT015)
Disha Nagori (18ESKIT025)

DEPARTMENT OF INFORMATION TECHNOLOGY

Swami Keshvanand Institute of Technology, M & G, Jaipur

 [ii]

Table of Contents

Contents
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Document Conventions..............................................................................................................1
1.3 Intended Audience and Reading Suggestions.............................................................................1
1.4 Product Scope.............................................................................................................................1
1.5 References..................................................................................................................................2
2. Overall Description..................................................................................................................3
2.1 Product Perspective....................................................................................................................3
2.2 Product Functions.......................................................................................................................3
2.3 User Classes and Characteristics................................................................................................4
2.4 Operating Environment..............................................................................................................5
2.5 Design and Implementation Constraints.....................................................................................6
2.6 User Documentation...................................................................................................................6
2.7 Assumptions and Dependencies.................................................................................................6
3. External Interface Requirements...........................................................................................7
3.1 User Interfaces............................................................................................................................7
3.2 Hardware Interfaces....................................................................................................................7
3.3 Software Interfaces.....................................................................................................................9
3.4 Communications Interfaces........................................................................................................9
4. System Features.....................................................................................................................10
4.1 Functional Requirements..........................................................................................................10
5. Other Nonfunctional Requirements.....................................................................................12
5.1 Performance Requirements.......................................................................................................12
5.2 Security Requirements..............................................................................................................12
5.3 Software Quality Attributes......................................................................................................12
6. Other Requirements..............................................................................................................14
6.1 E-R Diagram:...........................................................................................................................14
6.2 Activity Diagram......................................................................................................................16
6.2.1 User Registration Activity (SignUp):...................................................................................16
6.2.2 User login and application for leave.....................................................................................17
6.2.3 Application approval / rejection...........................................................................................18
6.3 Sequence Diagram:...................................................................................................................19
6.3.1 Users Login Sequence Diagram...........................................................................................19
6.3.2 Sequence diagram representing leave approval / rejection...................................................20
7. References:..............................................................................................................................21

Revision History
Name Date Reason For Changes Version
 Page |1

1. Introduction

1.1 Purpose
The main objective of the Project on Employee Leave Management System is to manage the
details of Employee, Leave, Company ,Payroll ,Salary. It manages all the information about
Employee, Leave Type, Salary, Employee. The project is totally built at administrative end and
thus only the administrator is guaranteed the access. The purpose of the project is to build an
application program to reduce the manual work for managing the Employee, Leave, Leave Type,
Company. It tracks all the details about the Company, Payroll, Salary.

The purpose of Employee Leave Management System is to automate the existing manual system
by the help of computerized equipments and full-fledged computer software, fulfilling their
requirements, so that their valuable data/information can be stored for a longer period with easy
accessing and manipulation of the same. The required software and hardware are easily
available and easy to work with.

The aim is to automate its existing manual system by the help of computerized equipments and
full-fledged computer software, fulfilling their requirements, so that their valuable data/information
can be stored for a longer period with easy accessing and manipulation of the same. Basically
the project describes how to manage for good performance and better services for the clients.

1.2 Document Conventions

The format of this document is referred from the standard IEEE guidelines:
• Font face: Arial II. MODULE
• Font size:
• Heading: 18
• Sub-heading: 14
• Description: 11
• Bold face and indentation is used on general topics and or specific points of interest including
the heading and sub-heading.

1.3 Intended Audience and Reading Suggestions

This document is mainly intended for project guides. The sequence for reading the document
begins with the overview sections and proceeding through the sections that are most pertaining
to each reader type.

1.4 Product Scope

Our project aims at Business process automation, i.e. we have tried to computerize various
processes of Employee Leave Management System.

 In computer system the person has to fill the various forms & number of copies of the forms can
be easily generated at a time.
 Page |2

 In computer system, it is not necessary to create the manifest but we can directly print it, which
saves our time.

 To assist the staff in capturing the effort spent on their respective working areas.

 To utilize resources in an efficient manner by increasing their productivity through automation .

 The system generates types of information that can be used for various purposes.

 It satisfy the user requirement

 Be easy to understand by the user and operator

 Be easy to operate

 Have a good user interface

 Be expandable

 Delivered on schedule within the budget .

1.5 References
As Internet is an Ocean of knowledge, we, too, has been helped by the same inter network of
system, We’ve referenced from many a sites to get Information/ for Knowledge Gathering to
understand the current scenario of the market, below are the references we have got helped
from, and we acknowledge the same:

• www.scribd.com

• downloads.intel.com

• cs.swt.edu

• Wikipedia.org

• ques10.com

• pdfcoffee.com
 Page |3

2. Overall Description

2.1 Product Perspective

It is aimed at replacing the tedious paperwork that the companies or colleges currently use. The
system will collect data and store it for fast and easy reference. The system will provide users
with a complete record of the attendance and leaves. It will also provide information about the
leave balance (availability).The system is thus helpful to reduce the time and complexity of
maintaining the records.

It may help collecting perfect management in details. In a very short time, the collection will be
obvious, simple and sensible. It will help a person to know the management of passed year
perfectly and vividly. It also helps in current all works relative to Employee Leave Management
System. It will be also reduced the cost of collecting the management & collection procedure will
go on smoothly.

Our project aims at Business process automation, i.e. we have tried to computerize various
processes of Employee Leave Management System :

 In computer system the person has to fill the various forms & number of copies of the forms can
be easily generated at a time.

 In computer system, it is not necessary to create the manifest but we can directly print it, which
saves our time.

 To assist the staff in capturing the effort spent on their respective working areas.

 To utilize resources in an efficient manner by increasing their productivity through automation .

 The system generates types of information that can be used for various purposes.

 It satisfy the user requirement

 Be easy to understand by the user and operator

 Be easy to operate

 Have a good user interface

 Be expandable

 Delivered on schedule within the budget .

2.2 Product Functions

Some major product functionalities of the system are as follows:

 Page |4

 Information about the employee/student/staff attendance.

 Check for leave availability.

 Maintain employee leave record.

 Display notices.

 Apply for leave.

 Approve or reject leave application.

2.3 User Classes and Characteristics

This Use Case Diagram is a graphic depiction of the interactions among the elements of Leave
Management System. It represents the methodology used in system analysis to identify, clarify,
and organize system requirements of Leave Management System. The main actors of Leave
Management System in this Use Case Diagram are Super Admin, System User, Manager,
Employee, who perform the different type of use cases such as Manage Leave, Manage
Company, Manage Branch, Manage Report Manage Leave, Manage Notification, Manage
Approval of Leave, Manage Users and Full Leave Management System Operations. Major
elements of the UML use case diagram of Leave Management System are shown on the picture
below

The relationships between and among the actors and the use cases of Leave Management
System:

• Super Admin Entity: Use cases of Super Admin are Manage Leave, Manage Company,
Manage Branch, Manage Report, Manage Leave, Manage Notification, Manage Approval of
Leave, Manage Users and Full Leave Management System Operations.

• System User Entity: Use cases of System User are Manage Leave, Manage Company,
Manage Branch, Manage Report, and Manage Leave Manage Notification Manage Approval of
Leave.

• Manager Entity: Use cases of Manager are Check Requests, Approve Leave Requests, and
Create Leave Reports. Employee Entity Use cases of Employee are Request for Leave, Check
Leave Balance, Check Leave Status.

• Employee Entity: Use cases of employee are Request for leave, Check Leave Balance, Check
Leave status.
 Page |5

Fig.: USE CASE DIAGRAM

2.4 Operating Environment

This software will work on all operating systems with a web browser with active internet.

Open source, HTML, Windows and Ubuntu.

 Page |6

2.5 Design and Implementation Constraints

● High performance, user friendly, security-based system, validation of users, very fast
response time.

● GUI is only in English.

● Login and password is used for the identification of users.

● Limited to HTTP/HTTPS or locally during development.

● This system is working for a single server.

2.6 User Documentation

A link is provided for the help & very easy user interface . That link has steps to use the software .

2.7 Assumptions and Dependencies

Every system requires some certain parameters to work, to work as per the requirement, our
system also requires some parameters, and we assume them as fulfilled before using this
system, which are as:

• Employee, Managers and Admin will have a username and password; else, they ’ll have to
register themselves on our website.

• This software needs user to have complete knowledge of leave management system and its
working.

• Software is dependent on access of Internet, as it is a remote application, it is necessary to

have internet access.

• Assume that all the information entered by the user will be correct. If any wrong information is
found then the system will notify an alert.

• The system is required to save the generated reports.

 Page |7

3. External Interface Requirements

3.1 User Interfaces

 Login Panel: Enter correct username and password then login and perform specific tasks
the application automatic check who is login Admin / User/ Engineer etc.

 Main Window: Main window have contain multiple options and also available public
holiday calendar the employee see which holiday up coming.

 Create Account: If new employee hire in the company then first of all create account then
employee eligible to give leaves otherwise employee not give leaves.

 View User's : If the superior want to see and modify user's account data then use view
user the multiple searching available in this window.

 Change Password: User change password with this window

 Apply Leave: This window show user remaining leave's and prevent give the greater
leaves for assumed policy.

 View Leave's: The superior watch sub-ordinates leave's here.

 View own Leave's: If the employee want to see own leave's which
Approved/Cancel/Reject see here.

 Summary Report : The superior must watch sub-ordinates leave's here

 Notification: The two kinds of notification request/Confirmation superior comes request on

Sub-ordinates show on request notification bar and after approved and reject leave show
confirmation bar.

3.2 Hardware Interfaces

4. Minimum Requirements:

Client Side
 Page |8

Processor RAM Disk Space

Intel Pentium III or
Google Chrome v84 128 MB 100 MB
AMD -800 MHz

Server Side
Processor RAM Disk Space
Intel Pentium III or
NPM v6 1 GB 3.5 GB
AMD -800 MHz
500 MB
MongoDB- v4+ Intel Pentium III or AMD -800 256 MB (Excluding Data Size)
MHz

 Recommended Requirements:

Client Side
Processor RAM Disk Space
IE10, All Intel or AMD - 1
256 MB 100 MB
Google Chrome 90 GHZ

Server Side
Processor RAM Disk Space
All Intel or AMD - 2
NPM v7 2 GB 3.5 GB
GHZ

500 MB
MongoDB All
v4.4Intel or AMD - 2 GHZ 512 MB (Excluding Data Size)
 Page |9

4.1 Software Interfaces

 Client on Internet
Web Browser (Google Chrome v84, Internet Explorer v10)

 Operating System
Microsoft Windows 7+, Linux, Ubuntu v20+, MacOSX

 Data Base Server

MongoDB atlas, supported on any OS

 Development End
NodeJS v14+, ExpressJS tools, NPM script engine for serving React 16+ application.

4.2 Communications Interfaces

This system supports Google Chrome & Mozilla Firefox web browsers.
 P a g e | 10

5. System Features

5.1 Functional Requirements

There are registered human beings inside the gadget. Some are approvers. An approver can also
be a requestor.
Following is a listing of functionalities of the system:

1. A man or woman need to be capable of

• login to the system through the primary page of the software
• change the password after logging into the system
• see his/her eligibility info (like how many days of depart he/she is eligible for and so forth.)
• see his/her depart history since the time he/she joined the company/college
• practice for depart, specifying the from and to dates, cause for taking go away, cope with for
conversation whilst on leave
• see his/her present day leave packages and the go away packages which can be submitted to
him/her for approval or cancellation.

• approve/reject the depart packages that are submitted to him/her

• withdraw his/her leave utility (which has no longer been authorised but)
• Cancel his/her depart (which has been already accredited). This will want to be approved with
the aid of his/her Superior
• get assist approximately the go away device on the way to use the exclusive features of the
system.

2. As quickly as a leave utility /cancellation request /withdrawal /approval /rejection

/password-change is made with the aid of the character, an automated electronic mail need to be
sent to the individual and his superior giving information about the movement.

3. The range of days of leave (as consistent with the assumed depart policy) have to be
mechanically credited to everybody and a notification concerning the equal be sent to them
automatically

4. An automatic depart-approval facility for depart applications which might be older than 2 weeks
need to be there. Notification approximately the automated leave approval ought to be sent to the
individual as well as his superior
The modules concerned are:

• Administration
• Employee
• Search
• Report
 P a g e | 11

• Authentication
Administrator:

In this module the Administrator has the rights to feature all the Employees and register them
inside the organization and test the information of the Employee and check the reputation of the
depart after they have taken and what kind of depart they ’ve taken, and seek is finished primarily
based on the worker and file is generated based totally on employee.
Search:

This module consists of entire search like Leave search, Type of Leave, Employee based on the
depart and starting and finishing day of leave.
Employee:

In this module worker has the rights to apply his/her username and password for login and he/she
can see the request given by means of the user and he/she can bypass the procedure to the
Business Manager and preserve the file of the clients.
Reports:-

This module consists of all of the statistics about the reviews generated with the aid of the
Employees primarily based at the Performance and by means of the go away fame.
Authentication:

This module carries all the records approximately the authenticated user. User with out his/her
username and password can’t enter into the login if he/she is handiest the authenticated user
then he/she can enter to his login.
 P a g e | 12

6. Other Nonfunctional Requirements

Non-functional requirements make up a significant part of the specification. They are important as
the client and user may well judge the product on its non-functional properties. Provided the
product meets its required amount of functionality, the non-functional properties -- how usable,
convenient, inviting and secure it is -- may be the difference between an accepted, well-liked
product, and an unused one.

6.1 Performance Requirements

Performance requirements define acceptable response times for system functionality.

 The load time for user interface screens shall take no longer than two seconds.

 The log in information shall be verified within five seconds.

 Queries shall return results within five seconds

 The system shall consume very little of primary memory.

6.2 Security Requirements

Customer Service Representatives and Managers will be able to log in to the Leave Management
System. Customer Service Representatives will have access to the leave management and
scheduling subsystems. Managers will have access to the Management subsystem as well as the
leave management and scheduling subsystems. Access to the various subsystems will be
protected by a user log in screen that requires a valid Userld.

6.3 Software Quality Attributes

5.3.1 Standards Compliance

There shall be consistency in variable names within the system. The graphical user interface shall
have a consistent look and feel.

5.3.2 Reliability

Specify the factors required to establish the required reliability of the software system at time of
delivery.
 P a g e | 13

5.3.3 Availability

The system shall be available 24*7

5.3.4 Maintainability

The Leave Management System is being developed in Java Java is an object onented
programming language and shall be easy to maintain

5.3.5 Portability

The Leave Management System shall run in any Microsoft Windows environment that contains
Java Runtime and the Microsoft Access database.
 P a g e | 14

7. Other Requirements

7.1 E-R Diagram:

This ER (Entity Relationship) Diagram represents the model of Leave Management System Entity
The entity-relationship diagram of Leave Management System shows all the visual instrument of
database tables and the relations between Branch, Leave, Company, Employee etc. It used
 P a g e | 15

structure data and to define the relationships between structured data groups of Leave
Management System functionalities. The main entities of the

Leave Management System are Company, Branch, Report, Leave, Notification and Employee

Leave Management System entities and their attributes:

 Company Entity: Attributes of company are company_id,company name, company type,

company_description, company address .

 Branch Entity: Attributes of Branch are branch id, branch name, branch type, branch_city,
branch address.

 Report Entity: Attributes of Report are report, id, report_name, report_type, report
description

 .Leave Entity: Attributes of Leave are leave_id, leave employee id leave type, leave
status, leave to leave from, leave description

 Notification Entity: Attributes of Notification are notification id, notification leave_id,

notification_title notification approval, notification leave cancellation, notification type,
notification description

 Employee Entity: Attributes of Employee are employes id, employee_name,

employee_mobile, employee_mall employee username,employee password, employee
address.

Description of Leave Management Systern Database

 The details of Company is store into the Company tables respective with all tables

 Each entity (Employee Report Notification, Branch Company) contains primary key and
unique keys.

 The entity Report Notification has binded with Company, Branch entities with foreign key

 There is one to-one and one-to-many relationships available between Notification, Leave
Employee Company

 All the entities Company Notification Report Employee are normalized and reduce
duplicacy of records

 . We have implemented indexing on each tables of Leave Management System tables for
fast query execution.
 P a g e | 16

7.2 Activity Diagram

7.2.1 User Registration Activity (SignUp):

Initially employees are made to fill all mandatory fields filled in the registration form.Once the user
clicks submit, the username is verified. If the username is already present, then the user is again
taken back, so that he can edit the invalid details.
 P a g e | 17

7.2.2 User login and application for leave

 P a g e | 18

After logging into the system, the employee can apply for a new leave by filling the application
form. He can also check his previous leave application status. While applying for leave, he will be
able to see his leave balance. If he has enough leave balance, he can submit the application to
the dept. head. Otherwise, he can contact the company head for any further help.

7.2.3 Application approval / rejection

 P a g e | 19

After logging in, the department head can view the applications. He can also view the employee ’s
profile. He will be able to check the leave balance and other criteria if they exist and accordingly
will approve or reject the applications. As this is done, the employee will receive the confirmation
mails for the approval/rejection of their applications automatically.

7.3 Sequence Diagram:

7.3.1 Users Login Sequence Diagram

 P a g e | 20

7.3.2 Sequence diagram representing leave approval / rejection

 P a g e | 21

8. References:

● Object Oriented Modeling and Design with UML-Michael Blaha, James Rambaugh.
● Software Engineering, Seventh Edition, Ian Sommerville.
● IBM Red Books.
● IBM TGMC Sample Synopsis.
 P a g e | 22

● IBM – www.ibm.in/developerworks.
● Java - www.sun.com
● Wikipedia - www.wikipedia.com
● Database Management Systems - Navathe.
● Complete Reference - J2EE - Keogh.