SOFTWARE REQUIREMENT

SPECIFICATION
(SRS DOCUMENT)

for

HRM
Table of Contents
1. Introduction..............................................................................................................................4
1.1 Purpose..............................................................................................................................4
2. Requirement Identifying Technique.........................................................................................5
2.1 Use Case Diagrams....................................................................................................................5
2.1.1 HR Use Case Diagram............................................................................................................5
2.1.1 Employee Use Case Diagram.................................................................................................6
2.2 Detailed Use Cases....................................................................................................................7
2.2.1 UC-01: Login..................................................................................................................7
2.2.2 UC-02: Logout................................................................................................................7
2.2.3 UC-03: Register Employee.............................................................................................8
2.2.4 UC-04: Update Employee...............................................................................................8
2.2.5 UC-05: View Employee.................................................................................................9
2.2.6 UC-06: Delete Employee.............................................................................................10
2.2.7 UC-7: Apply for Leave................................................................................................10
2.2.8 UC-8: View Pending Leave.........................................................................................11
2.2.9 UC-9: Update Pending Leave......................................................................................11
2.2.10 UC-10: Delete Pending Leave Request.....................................................................12
2.2.11 UC-11: Approve/Disapprove Leave Request............................................................13
2.2.12 UC-12: View Leave application List.........................................................................13
2.2.14 UC-14: Mark Attendance..........................................................................................14
2.1.15 UC-15: View Attendance..........................................................................................14
2.2.16 UC-16: View Attendance List...................................................................................15
2.2.17 UC-17: View Payroll.................................................................................................15
2.2.18 UC-18: Generate PaySlip/Invoice.............................................................................16
3. Functional Requirements.......................................................................................................16
3.1.1 FR-01 Log In...........................................................................................................16
3.1.2 FR-02 Log Out.........................................................................................................17
3.1.3 FR-03 Create Employee Profile...............................................................................17
3.1.4 FR-04 View Employee Profile................................................................................17
3.1.5 FR-05 View Employees List...................................................................................18
3.1.6 FR-06 Search Employee by name...........................................................................18
3.1.7 FR-07 Search Employee by Id.................................................................................18
3.1.8 FR-08 Delete Employee..........................................................................................19
3.1.9 FR-09 Mark Attendance..........................................................................................19
3.1.10 FR-10 View Attendance List...................................................................................19
 3.1.11 FR-11 View Attendance Employees.......................................................................20
3.1.12 FR-12 View Attendance History.............................................................................20
3.1.13 FR-13 Apply for leave.............................................................................................20
3.1.14 FR-14 Submit Leave Application............................................................................21
3.1.15 FR-15 View Leave Application...............................................................................21
3.1.16 FR-16 Update Pending Application.........................................................................21
3.1.17 FR-17 Delete Pending Application..........................................................................22
3.1.18 FR-18 View Pending Application...........................................................................22
3.1.19 FR-19 Accept/Reject Pending Application.............................................................22
3.1.20 FR-20 View List of Approved Applications...........................................................23
3.1.21 FR-21 View List of Rejected Applications.............................................................23
3.1.22 FR-22 View Leave Applications History................................................................23
4. Non-Functional Requirements...............................................................................................24
4.1 Performance....................................................................................................................24
4.2 Usability..........................................................................................................................24
4.3 Maintainability................................................................................................................24
4.4 Reliability........................................................................................................................24
5. Class Diagram........................................................................................................................25
6. Activity diagram....................................................................................................................26
6.1 Fingerprint Attendance...................................................................................................26
6.2 Attendance from home....................................................................................................27
6.3 Add Appraisals................................................................................................................28
6.4 View Attendance List......................................................................................................29
6.5 Submit Leave Application..............................................................................................30
6.6 Approve/Disapprove Employee Leave...........................................................................31
6.7 Submit Claim Form.........................................................................................................32
6.8 Approve Claim................................................................................................................33
7. ERD Diagram........................................................................................................................34
8. DFD Diagrams.......................................................................................................................35
8.1 Level 1 DFD of whole system........................................................................................35
8.2 Employee Login DFD Diagram......................................................................................36
8.3 Employee Leave Application DFD Diagram..................................................................36
8.4 Appraisal DFD Diagram.................................................................................................37
8.5 Leave Approval DFD Diagram.......................................................................................37
1. Introduction

The HR Management System Project's software requirement specification is contained in this

document. For an overview, we will provide a detailed description as well as a list of
requirements that match the needs of a preliminary estimate of the company.

1.1 Purpose
The proposed system is a cloud based HRM using block chain Technology. The system will
make company and HR day to day work routine easy and more secure. The system using block
chain technology will provide data integrity, more security while transferring of sensitive
information and keeping record of employees and their pays.

The system will be efficient and will provide all kind of attendance options. Employer can view
attendance and location of the employee through geo location based attendance feature of our
app. Employees can mark their attendance through fingerprint and face recognition technology.
Furthermore, if employee is working from home then the employer can ask them to keep
checking in their time in the system at different intervals. This will show if the employee is
engaging or not with system. Furthermore instead of keeping paper files that take up valuable
space, the system electronic records of employee information, benefits, education, changes,
assessments, and requests. Electronic working will make jobs easier to complete. User can use
the features like E-Claim and E-Leave to make their work easier. The system is versatile in terms
of adding, deleting, and editing personnel records, and all information belongs to HR
management.
2. Requirement Identifying Technique

2.1 Use Case Diagrams

Following are the Use Case diagrams for the proposed System

2.1.1 HR Use Case Diagram

2.1.1 Employee Use Case Diagram
 2.2 Detailed Use Cases

2.2.1 UC-01: Login

Use Case ID: UC-01
Use Case Name: Login
Actors: HR (primary actor), Employee (primary actor), Candidate (primary Actor)
Description: User shall login to get access to his/her account in order to facilitate him/her self with the system.

Trigger: User clicks the “Login” button to sign in his/her account

Preconditions: PRE-1. User is registered in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully logged in his/her account and has access to his/her profile.

Normal Flow: 1. User clicks on the sign in button.

2. User enters his/her credentials.
3. User clicks on the login button.
Alternative Flows: N/A
Exceptions: 2a. In step 2 of normal flow, if the user enters invalid credentials.
1. System will prompt an error message to user “invalid username or password”.
2. User will enter correct credentials.
3. Use case resumes on the step 3 of normal flow.
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account.

2.2.2 UC-02: Logout

Use Case ID: UC-02
Use Case Name: Logout
Actors: HR (primary actor), Employee (primary actor), Candidate (Primary Actor)
Description: User shall logout from his/her account once he/she is finished acquiring the system resources.

Trigger: User clicks the “Logout” button to sign in his/her account

Preconditions: PRE-1. User is logged in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully logged out of his/her account.

Normal Flow: 1. User clicks on the logout button from the menu.
2. User is redirected to the Login page.
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A
Assumptions 1. User has internet connection.

2.2.3 UC-03: Register Employee

Use Case ID: UC-03
Use Case Name: Create Employee Profile
Actors: HR (primary actor), Employee (secondary actor)
Description: Registration is necessary step for using the system. In this use case HR will register/create account
of employee of the organization.
Trigger: User clicks the “Register” button.
Preconditions: PRE-1. User has a working internet connection.
PRE-2. User is logged in the system.
PRE-3. System is available to the user.
Postconditions: POST-1. HR successfully registered the employee.
POST-2. Employee account will be created.
Normal Flow: 1. User clicks on register account button.
2. User will fill out the employee information required in the form.
3. User will fill out the email address text field.
4. User will fill out the password text field.
5. User will fill out the confirm password text field.
6. User will click on the create account button
Alternative Flows: N/A
Exceptions: 3a. In step 2 of the normal flow if the user enters incorrect email address
1. System will show error message “incorrect email address”.
2. User will enter the correct email address.
3. Use case resumes on step 3 of normal flow.
3b. In step 4 of the normal flow if the password doesn’t match with password in the step 3
1. System will show error message “the passwords don’t match”
2. User will enter the correct password.
3. Use case resumes on step 5 of the normal flow
3c. In step 3 of the normal flow if the email address of employee already exists.
1. System will prompt error message to user “email address already exists”.
2. User will enter the correct email address.
3. Use case will resumes on the step 3 of the normal flow.
Business Rules N/A
Assumptions 1. User has internet connection.
2. Password must contain one upper case letter, one special case character, and one digit.

2.2.4 UC-04: Update Employee

Use Case ID: UC-04
Use Case Name: Update Employee
Actors: HR (primary actor), Employee (primary actor)
Description: HR will update the employee details (i.e. personal information, education, experience etc.) in the
system.
Trigger: User clicks the “Update Employee” button to edit the
 employee details.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
Postconditions: POST-1. HR has successfully updated the profile by editing he employee information in the
system.
Normal Flow: 1. User clicks on “Employee” button.
2. User clicks on the “Update Employee” button
3. User enters the new employee data.
4. User clicks on the “Update profile” button
5. HR and employee can view the updated data.
Alternative Flows: N/A
Exceptions: 2a. In step 3 of the normal flow if the user enters incorrect details
1. System will show error message to enter correct data.
2. User will enter the correct data.
3. Use case resumes on step 4 of normal flow.
Business Rules N/A
Assumptions 1. User has internet connection.

2.2.5 UC-05: View Employee

Use Case ID: UC-05
Use Case Name: View Employee
Actors: Employee (primary actor)
Description: Employee can view its profile created by the HR.
Trigger: User clicks on the employee profile link.
Preconditions: PRE-1. User is registered successfully.
PRE-2. User is logged in the system.
PRE-3. System is available to the user.
Postconditions: POST-1. User views his/her profile successfully.
Normal Flow: 1. User logs into his/her account.
2. User views the dashboard.
3. User clicks on the Employee profile link on the menu bar.
4. User views his/her profile.
Alternative Flows: N/A
Exceptions: 1a. In step 1 of the normal flow if the user enters incorrect credentials.
1. System will show error message to enter correct credentials.
2. User enters the correct data.
3. Use case resumes on step 2 of normal flow.
Business Rules N/A
Assumptions 1. User has internet connection.
User is an employee of the organization

2.2.6 UC-06: Delete Employee

Use Case ID: UC-06
Use Case Name: Delete Employee
Actors: HR (primary actor)
Description: HR can delete employee profile created by the HR.
Trigger: User clicks on the employee profile link.
Preconditions: PRE-1. User is registered successfully.
PRE-2. User is logged in the system.
PRE-3. System is available to the user.
Postconditions: POST-1. User deletes profile successfully.
Normal Flow: 1. User logs into employee account.
2. User views the dashboard.
3. User clicks on the Employee profile link on the menu bar.
4. User clicks the delete profile button.
5. System will prompt a message to user “Are you sure?”
6. User clicks on the “yes” button
7. User profile gets deleted successfully.
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A
Assumptions 1. User has internet connection.
2. User is an employee of the organization

2.2.7 UC-7: Apply for Leave

Use Case ID: UC-7

Use Case Name: Apply for leave
Actors: Employee (primary actor)
Description: Employee can apply for leave by filling a leave form, from employee dashboard.
Trigger: User clicks on the leave link from the menu bar.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
Postconditions: POST-1. Employee has applied for the leave successfully

Normal Flow: 1. Users logs in the system.

2. User click on Leave link on the menu bar.
3. User clicks on “Apply” button.
4. User fills out the leave application form.
5. User clicks on the “submit” button
6. Leave application is submitted successfully.
Alternative Flows: N/A
Exceptions: 2a. In step 4 of the normal flow if the user enters incorrect details.
1. System will show error message to enter correct details.
2. User enters the correct data.
3. Use case resumes on step 3 of normal flow.
2b. In step 5 of the normal flow if the user forgot to fill any required field
1. System will prompt user to fill all the required fields.
2. User fills all the fields correctly.
3. Use case resumes on the step 5 of the normal flow.
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account

2.2.8 UC-8: View Pending Leave

Use Case ID: UC-8

Use Case Name: View pending leave
Actors: Employee (primary actor), HR (primary actor)
Description: User can view the leaves that have not been accepted or rejected.
Trigger: User clicks on the “view leave” button.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
PRE-3. There are some pending leave applications available to user.
Postconditions: POST-1. User view its pending leave application successfully.
Normal Flow: 1. Users logs in the system.
2. User click on Leave link on the menu bar.
3. User clicks “pending leave” button.
4. User will be shown a list of pending leave requests.
5. User selects the pending application that he wants to view.
6. User clicks on “view leave” button.
7. User successfully view the details of the pending leave.
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account

2.2.9 UC-9: Update Pending Leave

Use Case ID: UC-9

Use Case Name: Update pending leave
Actors: Employee (primary actor)
Description: User can update the leave application form that has not been accepted or rejected.
Trigger: User clicks on the “update” button.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
PRE-3. There are some pending leave applications available to user.
Postconditions: POST-1. User update its pending leave application details successfully.
Normal Flow: 1. Users logs in the system.
2. User click on Leave link on the menu bar.
3. User clicks “pending leave” button.
4. User will be shown a list of pending leave requests.
5. User selects the pending application that he wants to update.
 6. User clicks on ‘update’ button.
7. User update the details of the pending leave.
8. User clicks on save changes button.
9. User successfully edited his/her pending leave application.
Alternative Flows: N/A
Exceptions: N/A
Business Rules User can update the leave only till the HR accepted or rejects it.
Assumptions 1. User has internet connection.
2. User has a registered account

2.2.10 UC-10: Delete Pending Leave Request.

Use Case ID: UC-10

Use Case Name: Delete Pending Leave Request
Actors: Employee (primary actor)
Description: Employee can delete its leave application request that is not yet approved or disapproved by the
HR.
Trigger: User clicks on the “Delete” button.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
PRE-3. There are some pending leave applications available to user.
Postconditions: POST-1. Employee deletes its pending leave application successfully.
Normal Flow: 1. Users logs in the system.
2. User click on Leave link on the menu bar.
3. User clicks “pending leave” button.
1. User will be shown a list of pending leave requests.
2. User selects the pending application that he wants to delete.
3. User clicks on delete button.
4. System prompts a confirmation message, “Do you want to delete?”
5. User selects the “yes” button.
6. User leave application is deleted successfully.
Alternative Flows: N/A

Exceptions: N/A
Business Rules N/A

Assumptions 1. User has internet connection.

2. User has a registered account

2.2.11 UC-11: Approve/Disapprove Leave Request.

Use Case ID: UC-11

Use Case Name: Approve/disapprove leave request
Actors: HR (primary actor), Employee (secondary actor)
Description: HR can approve and disapprove an employee leave application form.
Trigger: User clicks on the Leave link from the menu bar.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
PRE-3. There should be some pending leaves application available.
Postconditions: POST-1. Employee leave application is either approved or disapproved.
Normal Flow: 1. Users logs in the system.
2. User click on Leave link on the menu bar.
3. User clicks “pending leave” button.
4. User will be shown a list of pending leave requests.
5. User selects a leave application that he/she wants to accept.
6. User clicks on accept leave button.
7. Leave is successfully granted to the employee.
8. Employee will be notified of the leave confirmation via notification.
Alternative Flows: 6a. In step 6 of the normal flow, user can click on the “reject leave” button
1. Employee will be notified of the leave rejection via notification.
Exceptions: 4a. In step 4 of the normal flow if the user enters incorrect details.
1. System will show error message to enter correct details.
2. User enters the correct data.
3. Use case resumes on step 3 of normal flow.
5a. In step 5 of the normal flow if the user forgot to fill any required field
7. System will prompt user to fill all the required fields.
8. User fills all the fields correctly.
9. Use case resumes on the step 5 of the normal flow.
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account

2.2.12 UC-12: View Leave application List

Use Case ID: UC-12

Use Case Name: View leave application List
Actors: HR (primary actor)
Description: User can view list of all leave application form that the user has accepted or rejected.
Trigger: User clicks on the “view list” button.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
PRE-3. There are some approved/disapproved leave applications available to user.
Postconditions: POST-1. User view the list of leave applications successfully.
Normal Flow: 1. Users logs in the system.
2. User click on Leave link on the menu bar.
3. User clicks “view list” button.
4. User will be shown a list of leave applications
5. User selects an application that he wants to view.
6. User clicks on ‘view’ button.
7. User view the details of the leave application.
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account

2.2.14 UC-14: Mark Attendance

Use Case ID: UC-14

Use Case Name: Mark Attendance
Actors: Employee (primary actor)
Description: Employee can mark its attendance on daily basis.
Trigger: User clicks on the “check in” button.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
Postconditions: POST-1. Employee marks its attendance successfully.
Normal Flow: 1. Users logs in the system.
2. User opens Attendance page
3. User clicks “Check In” button.
4. System saves the check in time.
Alternative Flows: N/A
Exceptions: N/A
Business Rules User can mark attendance only in the premises of the organization.
Assumptions 1. User has internet connection.
2. User has a registered account

2.1.15 UC-15: View Attendance

Use Case ID: UC-15

Use Case Name: View Attendance
Actors: Employee (primary actor)
Description: Employee shall be able to view its attendance on the daily basis.
Trigger: User clicks on the “view attendance” button.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
Postconditions: POST-1. Employee view its attendance successfully.
Normal Flow: 1. Users logs in the system.
2. User click on the attendance link from the menu.
3. User clicks “view attendance” button.
4. User view his/her attendance successfully.
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account

2.2.16 UC-16: View Attendance List

Use Case ID: UC-16

Use Case Name: View Attendance List
Actors: HR (primary actor)
Description: HR shall be able to view attendance list of all employees on the daily basis.
Trigger: User clicks on the “view attendance” button.
Preconditions: PRE-1. User is logged in the system.
PRE-2. System is available to the user.
Postconditions: POST-1. HR view the attendance list of employees successfully.
Normal Flow: 1. Users logs in the system.
2. User click on the Attendance link from the menu.
3. User clicks on “attendance list” button.
4. User view his/her attendance successfully.
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account

2.2.17 UC-17: View Payroll

Use Case ID: UC-17

Use Case Name: View Payroll
Actors: HR, Employee
Description: In this use case user will be able to view the salary amount
Trigger: User clicks on the “view salary” button.
Preconditions: PRE-1. User is logged in the system.
Postconditions: POST-1. User view the salary details of employee(s)
Normal Flow: 1. User clicks on view salary button.
2. System displays list of salary details.
Alternative Flows: N/A

Exceptions: N/A
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account

2.2.18 UC-18: Generate PaySlip/Invoice

Use Case ID: UC-43
Use Case Name: Generate PaySlip/Invoice
Actors: HR (primary actor), Employee (primary)
Description: In this use case users shall be able to generate salary payslip/Invoice of the salary
Trigger: User clicks on the “Generate payslip” button.
Preconditions: PRE-1. User is logged in the system.
Postconditions: POST-1. System generates the payslip of salary for user to print.
Normal Flow: 1. User clicks on view salary.
2. System displays salary records
3. User clicks on generate button.
4. System generates the payslip
Alternative Flows: 3a. In step 3 of the normal flow if there is no record available
1. System displays message there is no record available.
2. System displays the view salary page.
Exceptions: N/A
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account

3. Functional Requirements
3.1.1 FR-01 Log In

Identifier FR-01
Title Log in
Requirement The user shall be able to login the system by the role specified to him
Source Client/supervisor.
Rationale In order for user to have access to the system.
Business Rule (if required) User has been signed up successfully
Dependencies FR-02
Priority High

3.1.2 FR-02 Log Out

Identifier FR-02
Title Log Out
Requirement The user shall be able to logout the system once logged in.
Source Client/supervisor.
 Rationale User is logged out, once he is done using the system.
Business Rule (if N/A
required)
Dependencies FR-01
Priority High

3.1.3 FR-03 Create Employee Profile

Identifier FR-03
Title Create Employee Profile
Requirement HR shall be able to create an employee successfully in the organization.
Source Client/supervisor.
Rationale HR can add new employee so that their information is stored and easily accessible.
Business Rule (if Only HR can create employee profile.
required)
Dependencies FR-01
Priority High

3.1.4 FR-04 View Employee Profile

Identifier FR-04
Title View Employee Profile
Requirement Employee shall be able to view the profile created by HR
Source Client/supervisor.
Rationale Employee can view their profile (personal, educational information etc.)
Business Rule (if Employee can only view the profile but cannot edit or delete it
required)
Dependencies FR-01
Priority Medium

3.1.5 FR-05 View Employees List

Identifier FR-05
Title View Employees List
Requirement HR shall be able to view list all of employees.
 Source Client/supervisor.
Rationale In order to see the total number of employees and also to see their complete profile
by selecting a data.
Business Rule (if Only HR can view list of all employees
required)
Dependencies FR-03
Priority Low

3.1.6 FR-06 Search Employee by name

Identifier FR-06
Title Search Employee by name
Requirement HR shall be able to search a particular employee by their name
Source Client/supervisor.
Rationale In order to quickly search for an employee from the long list.
Business Rule (if Only HR can perform this task
required)
Dependencies FR-05
Priority Low

3.1.7 FR-07 Search Employee by Id

Identifier FR-07
Title Search Employee by Id
Requirement HR shall be able to search a particular employee by their ID
Source Client/supervisor.
Rationale In order to quickly search for an employee.
Business Rule (if Only HR can perform this task
required)
Dependencies FR-05
Priority Medium

3.1.8 FR-08 Delete Employee

 Identifier FR-08
Title Delete Employee
Requirement HR shall be able to search a particular employee by their ID
Source Client/supervisor.
Rationale In order to quickly search for an employee.
Business Rule (if Only HR can perform this task
required)
Dependencies FR-05
Priority High

3.1.9 FR-09 Mark Attendance

Identifier FR-09
Title Mark Attendance
Requirement Employee shall be able to mark attendance by logging in the system.
Source Client/supervisor.
Rationale In order to mark attendance.
Business Rule (if Employee can mark attendance only inside the premises of the organization
required)
Dependencies FR-01
Priority High

3.1.10 FR-10 View Attendance List

Identifier FR-10
Title View Attendance List
Requirement HR shall be able to view the attendance list of employees.
Source Client/supervisor.
Rationale In order to view the total number of employees that are present.
Business Rule (if Only HR can perform this task
required)
Dependencies FR-09
Priority Medium
3.1.11 FR-11 View Attendance Employees

Identifier FR-11
Title View Attendance Employees
Requirement HR shall be able to view the number of employees along with their names, who are
absent.
Source Client/supervisor.
Rationale In order to view the number of employees which are absent.
Business Rule (if Only HR can perform this task
required)
Dependencies FR-09
Priority High

3.1.12 FR-12 View Attendance History

Identifier FR-12
Title View Attendance History
Requirement HR shall be able to view the attendance history of employees.
Source Client/supervisor.
Rationale In order to view the employee attendance history.
Business Rule (if Only HR can perform this task
required)
Dependencies FR-11
Priority Medium

3.1.13 FR-13 Apply for leave

Identifier FR-13
Title Apply for Leave
Requirement Employee shall be to apply for a leave when needed.
Source Client/supervisor.
Rationale In order to avail a leave.
Business Rule (if Employee must have leaves available.
required)
Dependencies FR-01
Priority High
3.1.14 FR-14 Submit Leave Application

Identifier FR-14
Title Submit Leave Application
Requirement Employee shall be to submit the leave application to HR
Source Client/supervisor.
Rationale In order to avail a leave.
Business Rule (if Employee must have leaves available to apply.
required)
Dependencies FR-13
Priority High

3.1.15 FR-15 View Leave Application

Identifier FR-15
Title View Leave Application
Requirement Employee shall be to view the pending leave application that has neither been
accepted or rejected by the HR.
Source Client/supervisor.
Rationale In order to view the pending leave application.
Business Rule (if Employee must have applied for the leave
required)
Dependencies FR-13
Priority Medium

3.1.16 FR-16 Update Pending Application

Identifier FR-16
Title Edit Pending Application
Requirement Employee shall be able to edit the pending application.
Source Client/supervisor.
Rationale In order to edit the pending leave application.
Business Rule (if Employee must have already applied for the leave.
required)
Dependencies FR-13, FR-14
Priority Low
3.1.17 FR-17 Delete Pending Application

Identifier FR-17
Title Delete Pending Application
Requirement Employee shall be to delete the pending leave application that has neither been
accepted or rejected.
Source Client/supervisor.
Rationale In order to delete the pending leave application.
Business Rule (if Employee must have already applied for the leave.
required)
Dependencies FR-13, FR-14
Priority Low

3.1.18 FR-18 View Pending Application

Identifier FR-18
Title View Pending Application
Requirement HR shall be to view the pending leave application.
Source Client/supervisor.
Rationale In order to allow the HR to view the pending leave applications that has neither
been accepted nor rejected.
Business Rule (if Employee have already submitted the leave application.
required)
Dependencies FR-14
Priority High

3.1.19 FR-19 Accept/Reject Pending Application

Identifier FR-19
Title Accept/Reject Pending Application
Requirement System shall allow HR to reject or accept the any pending leave application
Source Client/supervisor.
Rationale In order to allow employees to avail the leave.
 Business Rule (if Employee have already submitted the leave application.
required)
Dependencies FR-14
Priority High

3.1.20 FR-20 View List of Approved Applications

Identifier FR-20
Title View List of Approved Applications
Requirement HR and employee shall be able to view list of all approved leave applications.
Source Client/supervisor.
Rationale In order for user to see which applications are approved.
Business Rule (if The leave Application have been approved
required)
Dependencies FR-14
Priority High

3.1.21 FR-21 View List of Rejected Applications

Identifier FR-21
Title View List of Rejected Applications
Requirement System shall allow both the HR and employee to view the list of rejected leave
applications.
Source Client/supervisor.
Rationale In order for user to see which applications are rejected.
Business Rule (if The leave application has been rejected.
required)
Dependencies FR-19
Priority High

3.1.22 FR-22 View Leave Applications History

Identifier FR-22
Title View Leave History
Requirement System shall allow both the HR and employee to view the list of leave applications
history
Source Client/supervisor.
 Rationale In order for user to view his/her previous leave record.
Business Rule (if The leave application have been rejected/accepted by the HR.
required)
Dependencies FR-21
Priority Medium

4. Non-Functional Requirements
4.1 Performance
PER-1: The average response time per every user click shall be less than 4 seconds. And
the maximum average time per every click shall be less than 6 seconds.

4.2 Usability
USE-1: The system user interface shall be user friendly. i.e. the minimum amount of time
taken by novice user to learn the system shall be 15 minutes.

4.3 Maintainability
Main-1: The system can make new changes on the basis of the requirements, if demanded
after completion of the system. The maintainability of the system can be done by
integrating new modules and offering new solutions for the raised problems.

4.4 Reliability

REL 1: The system shall have less than 6 hours downtime per two months
REL 2: Maximum Bugs per 1000 lines should not be greater than 9.
5. Class Diagram
Following is the Class Diagram for the proposed system

Note: Download the image for better clarity

6. Activity diagram
6.1 Fingerprint Attendance
6.2 Attendance from home
If the employee is working from home then HR can ask them to log time in during different
intervals in the system. This will show that employee is engaging with work and system.
6.3 Add Appraisals
HR/HR can add employee appraisals. Given below is the activity diagram for it.
6.4 View Attendance List
HR can view attendance list of all employees.
6.5 Submit Leave Application
Employees can apply for E-Leave easily through the system. Given below is the activity
diagram.
6.6 Approve/Disapprove Employee Leave
HR can approve and disapprove employee leaves. Given below is the activity diagram of leave
approval.
6.7 Submit Claim Form
Employee can claim (medical etc bill) from the company. Given below is the activity diagram
for the claim application.
6.8 Approve Claim
HR can approve or disapprove the employee Claim Application. Given below is the activity
diagram for the claim approval.
7. ERD Diagram
Given below is the ERD of the proposed system.

Note: You can download the image from the word file for better clarity and view.
8. DFD Diagrams
8.1 Level 1 DFD of whole system

8.2 Employee Login DFD Diagram

 Level 2 DFD for login

8.3 Employee Leave Application DFD Diagram

Level 2 DFD for leave Application

8.4 Appraisal DFD Diagram

Level 2 DFD for adding appraisal
8.5 Leave Approval DFD Diagram

Level 2 DFD for leave approval