M OHAMMAD FAIQ A LI

16-CS-02

Employee Management System

Bachelor of Science in Computer Science

Supervisor: Mr. Ammar Rafiq

Department of Computer Science

NFC-Institute of Engineering and Fertilizer Research, Faisalabad

Sept 29th , 2020

 Certificate

This is to certify that the work contained in the report titled “Employee Management
System”, submitted by Mr. M. Faiq Ali (2016-UET-IEFR-BSC (H)-CS-FD-02) for the
award of the degree of Bachelor of Computer Science.

Approved by . . . :

Supervisor: Mr. Ammar Rafiq

Committee Members:

Sept 29th , 2020

Dedication

This work is dedicated to my mother, who taught me that the best kind of knowledge to
have is that which is learned for its own sake.A special feeling of gratitude to my loving
siblings who taught me that even the largest task can be accomplished if it is done one step
at a time, whose words of encouragement and push for tenacity ring in my ears.

i
Abstract

Today is the age of internet. Internet is accessible in almost every part of the world and
wide variety of tasks can be performed using your mobile phone or computer. One can
do different tasks through internet with just one click. This Project entitled “Employee
Management System” has been designed towards improving the Management of Employee
in an organization. It is an android application designed for the availability of Employees,
Departments, Finance, Attendance and Leaves Records of an organization. It is user
friendly and easy to understand that can be used by anyone who is even familiar with
simple computer and mobile skills.

ii
Acknowledgments

This Project becomes a reality with the support and help of my Supervisor and Teachers. I
would like to extend our sincere thanks to all of them. I would like to express my gratitude
to Allah Almighty and my Mother for her prayers and encouragement which helped a lot
in this project. I am highly indebted to NFC Institute of Engineering & Fertilizer Research
for their guidance and constant supervision as well as for providing necessary information
regarding this project and also for their support in completing this endeavor.

M OHAMMAD FAIQ A LI
2016-UET-IEFR-BSC(H)CS-FD-02

September 2020

iii
Contents

Dedication i

Abstract ii

Acknowledgments iii

1 Introduction 1
1.1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Problem Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4.1 Chosen Methodology and Reason . . . . . . . . . . . . . . . . . 3
1.5 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5.1 Admin Panel: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5.2 Employee Panel: . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.6 Feasibility Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.6.1 Resource Requirement . . . . . . . . . . . . . . . . . . . . . . . 4
1.6.2 Risks Involved . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.7 Solution Application Areas . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.8 Tools and Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Literature Review 6
2.1 Related Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Benefits of Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Supply and Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Requirement Analysis 8
3.1 Requirments Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.1 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . 8
3.1.2 Non Functional Requirment . . . . . . . . . . . . . . . . . . . . 10
3.1.3 Software Requirment . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.4 Hardware Requirment . . . . . . . . . . . . . . . . . . . . . . . 11

4 System Design 12
4.1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1.1 Level-0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1.2 Level-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

iv
CONTENTS v

4.1.3 Level-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2.1 Discription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3 Entity Relationship Diagram . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3.1 Discription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.4 Usecase Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.1 Admin Use Case Diagram . . . . . . . . . . . . . . . . . . . . . 18
4.4.2 Employee Use Case Diagram . . . . . . . . . . . . . . . . . . . 19
4.5 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5.1 Admin Sequence Diagram . . . . . . . . . . . . . . . . . . . . . 20
4.5.2 Employee Sequence Diagram . . . . . . . . . . . . . . . . . . . 21
4.6 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6.1 Complete System . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6.2 Discription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.7 Class diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.7.1 Discription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5 System Implementation 25
5.1 Admin Application Interface . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.1 Main Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.2 Admin Login Page . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.3 Admin Dashboard Page . . . . . . . . . . . . . . . . . . . . . . 27
5.1.4 Sidebar Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1.5 Employee Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.1.6 Discipline Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.1.7 Finance Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.1.8 Salary Deduction Page . . . . . . . . . . . . . . . . . . . . . . . 32
5.1.9 Attendance Page . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.1.10 Leave Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.1.11 Performance Page . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.1.12 Setting Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.2 Employee Application Interface . . . . . . . . . . . . . . . . . . . . . . 37
5.2.1 Login Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.2.2 Employee Dashboard Page . . . . . . . . . . . . . . . . . . . . . 38
5.2.3 Sidebar Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2.4 Employee Profile Page . . . . . . . . . . . . . . . . . . . . . . . 40
5.2.5 Finance Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.2.6 Attendance Page . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2.7 Attendance Report Page . . . . . . . . . . . . . . . . . . . . . . 43
5.2.8 Leave Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.2.9 Settings Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6 System Testing 46
6.1 Functional testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.1.1 Installing and running the application . . . . . . . . . . . . . . . 46
6.1.2 Fields testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.1.3 Constant users feedback testing . . . . . . . . . . . . . . . . . . 47
CONTENTS vi

6.2 Usability testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.4 Compatibility testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.5 Security testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.6 TestCase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.6.1 Installing App . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.6.2 Admin Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.6.3 Add New Employee . . . . . . . . . . . . . . . . . . . . . . . . 49
6.6.4 List All Employees . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.6.5 Employee Categories . . . . . . . . . . . . . . . . . . . . . . . . 49
6.6.6 Employee Designation . . . . . . . . . . . . . . . . . . . . . . . 50
6.6.7 Employee Promotion . . . . . . . . . . . . . . . . . . . . . . . . 50
6.6.8 Fire Employee . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.6.9 Employee Discipline . . . . . . . . . . . . . . . . . . . . . . . . 51
6.6.10 Employee Finance . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.6.11 Employee Attendance . . . . . . . . . . . . . . . . . . . . . . . 52
6.6.12 Employee Leave . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.6.13 Employee Performance . . . . . . . . . . . . . . . . . . . . . . . 52
6.6.14 Admin Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.6.15 Admin Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.6.16 Employee Login . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.6.17 Employee Profile . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.6.18 Employee Finance . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.6.19 Employee Attendance . . . . . . . . . . . . . . . . . . . . . . . 54
6.6.20 Employee Leave . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.6.21 Employee Settings . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.6.22 Employee Logout . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.7 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

7 Conclusion 57
7.1 Future Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.1.1 Integration with Payroll System . . . . . . . . . . . . . . . . . . 57
7.1.2 Information Archiving . . . . . . . . . . . . . . . . . . . . . . . 57
7.1.3 Complain Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7.1.4 Live Chat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7.1.5 Theme & Appearance . . . . . . . . . . . . . . . . . . . . . . . 58

References 59
List of Figures

4.1 Context Level DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.2 Level-1 DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3 Level-2 DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.4 System Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.5 Entity Relationship Diagram . . . . . . . . . . . . . . . . . . . . . . . . 17
4.6 Admin Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.7 Employee Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . 19
4.8 Admin Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.9 Employee Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . 21
4.10 System Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.11 System Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.1 Application Main Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2 Admin Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.3 Admin Dasboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.4 Admin Sidebar Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.5 Employee Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.6 Discipline Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.7 Finance Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.8 Salary Deduction Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.9 Attendance Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.10 Leave Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.11 Performance Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.12 Setting Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.13 Employee Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.14 Employee Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.15 Employee Sidebar Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.16 Profile Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.17 Finance Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.18 Attendance Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.19 Attendance Report Page . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.20 Leave Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.21 Setting Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

vii
Chapter 1

Introduction

Employees are the backbone of any company therefore their management plays a major
role in deciding the success of an organization. In this world of growing technologies
everything has been computerized. With Large number of work opportunities the human
workforce has increased. Thus there is a need of a system which can handle the data of
such a large number of employees in an organization. This android application simplifies
the task of maintaining records because of its user friendly nature.

1.1 Objectives

Now a days there are many easy and outstanding methodologies to manage information of
employees in an organization of well developed countries. As our country is in the phase
of development, we have to get expert in modern technology. In order to do so I have to
bring technology to our country and introduce people with more easily and user friendly
technology that works at any place in the world.
This Employee Management System (EMS) is the step ahead towards this success
and providing a resource (android-a handheld application) to organizations that is not
present in most of the companies or institutes of our country. As employ’s has to go to HR
Department to get some information about their salary or change personal information etc.
Which is exhaustive.
Main objective is to develop a system to override the problems prevailing in practicing
manual system and to overcome them, so that employees can easily get access and updated
to their information more efficiently at anyplace in the world (Providing a real-time
environment). Well-designed database to store employee information.

1
Introduction 2

1.2 Problem Statement

Providing an Android version of an existing Web based Employee Management System so

that employees of an organization can perform all actions much quicker and efficiently.

1.3 Problem Description

Problems that can be solved by launching android version of Existing Web Based Employee
Management System:

• By using android application employees can view their personal information, can
register their leaves at any time anyplace using mobile data as the admin is also
available at the same time on mobile application.

• Many people use different kind of browser but sometimes no matter how user
friendly the browser is, there are people who still cannot understand the browser
functionalities i.e. moving back or next page (wasting a lot of time in request and
response of server) or the browser software may crash due to out of date and not
supporting latest features rather the app is more user-friendly and itself keeps on
updating as required and maintains its features.

• Apps usually store their data locally on mobile devices, in contrast to websites that
generally use web servers. For this reason, data retrieval happens swiftly in mobile
apps. Apps can further save users’ time by storing their preferences, and using them
to take proactive actions on users’ behalf. There is also a technical justification as to
why mobile apps can work faster. Mobile websites use JavaScript code to perform
most of their functions. And the framework that mobile apps use can run almost five
times faster than a JavaScript code

• As users spend a lot of time in mobile as compared to desktop so an android version

is more helpful than web based version.

• A mobile app can be designed with a lot of elaborate functions, based on advanced
gestures like ‘tap,’ ‘swipe,’ ‘drag,’ ‘pinch,’ ‘hold,’ so that user can perform actions
more quickly than a website.

• Even when employees are not actively using a mobile app, they are still reminded
of the organization associated with the app. The icon of the app acts like a mini-
advertisement for the organization. The presence of an app on an employs device
helps influence employs perception about organization subconsciously.[1]
1.4 Methodology 3

1.4 Methodology

There are different models and methodologies that are used, in this system incremental
model is used. In this model, each module passes through the requirements, design,
implementation and testing phases. A working version of application is produced during
the first module. Each subsequent release of the module adds function to the previous
release. The process continues till the complete system is achieved. [2]

1.4.1 Chosen Methodology and Reason

System methodology is incremental model, as all the requirements of complete system are
clearly defined in existing system and can be understandable by using existing web based
system. Easier to manage risk because risky pieces are identified and handled during its
iteration. It is easier to test and debug during each smaller iteration.

1.5 Project Scope

Android Application interface is divided into two parts:

1.5.1 Admin Panel:

• Admin can add and remove employees

• Admin can add or delete departments

• Admin can add or delete categories of employees

• Admin can add or delete discipline of employees

• Admin can mark performance of employees

• Admin can promote employees

• Admin can manage the salaries of employees

• Admin manages the attendance of employees

• Admin can view daily or monthly attendance reports of employees

• Admin manages the leaves request of employees

• Admin can accept or reject the leave requests

• Admin can view the leaves reports of employees

• Admin can fire and rehire employees

Introduction 4

1.5.2 Employee Panel:

• Employee can view his personal information.

• Employee can view his salary

• Employee can request for leaves

• Employee can view his attendance report

• Employee can update his password

1.6 Feasibility Study

1.6.1 Resource Requirement

System will require compatible hardware to develop android. Hardware that can easily run
Android Studio and Java SDK for android development and compatible devices to test the
end product.

1.6.2 Risks Involved

Most critical risk is the misunderstanding of existing system requirements that results
in quality problems. Lack of resource commitment. Admin person’s exposure to the
employee is really important. If the Admin person’s attitude to users is offensive we can
lose our user base.

1.7 Solution Application Areas

The Android version of EMS intends to introduce a high level of efficiency into the current
Process of viewing salary notifications and registration of leaves at their own places. As
users spend a lot of time in mobile as compared to desktop so an android version is more
helpful than web based version. And it will provide more functionality to the user for more
efficiency and user friendly experience.

1.8 Tools and Technology

• Android Studio

• Adobe XD

• StarUML

• XML
1.8 Tools and Technology 5

• Java

• Firebase Database
Chapter 2

Literature Review

Management is not only about managing resources and controlling expenses. Although
these are basic functions of management, there’s more to management than just managing
resources and controlling expenses. Another extremely important function of management
is the ability to manage employees beacause they are the lifeline of any organization.
Given the fact that every person and employee is different, managing employees
effectively continues to be one of the most common management issues that businesses
face in this demanding world of business. Employees not only need guidance from their
managers or admins, but they also need to know that they will be there to help them when
they need them or to help put things back on the right track.[3]

2.1 Related Applications

There are a lot of employee management system available in market and internet.Below
are discussed some employees systems which are currently used by organizations.
OrangeHRM’s is a human resources tool for a small or medium-sized bussiness. Fea-
tures include: fully modular, addons (e.g., benefits, employee self-service,training, budget,
job and salary history, etc.) for purchase, all standard HR functions (employees,leave,
benefits, performance, etc.), and more. [4]
WaypointHR is the HR software for any small or midsize company. WaypointHR can
manage employee data, which include personal details, leave/absent history, salary details,
discipline, performance etc.[5]
Employee Management System: Attendance Manager application allows fastest and
easiest way to manage staff details like attendance, leaves, salary etc.[6]
HR Management System is an android application designed specially for the employees
of an organization. It can keep employee details,can mark attendance, performance,
promotion etc. It can also ad more HR’s to the system. [7]

6
2.2 Benefits of Project 7

Tinypulse is an employee managemet system that helps organizations around the

world improve employee and customer happiness through a lightweight, cloud-based,
software-as-a-service solution. [8]

2.2 Benefits of Project

• It is simple to understand and can be used by anyone who is not even familiar with
simple employees system.

• The HR manager helps to provide information of employees and many other facilities
at the tap of a button.

• Time saving.

• There is no need of frequent meetups with HR manager, as complete system is online

in your handheld device to access and get service.

• Accessible to everyone through latest technology trends (smartphones, pc etc.)

• No need to have deep knowledge of web browsers and desktops.

2.3 Supply and Demand

The demand of using mobile applications services are increasing day by day because
technology has become a part of everyone’s life and increasing time efficiency has become
a norm. This system is supplying interactive interfaces in handheld devices.
Chapter 3

Requirement Analysis

This chapter focuses on requirements needed for the development of this project.

3.1 Requirments Specifications

There are many types of requirements require for completion of the project. These are
given below:
• Functional Requirements

• Non-Functional Requirements

• Software Requirements

• Hardware Requirements

3.1.1 Functional Requirements

Following are the Functional Requirements:

3.1.1.1 Authentication

• Login:The user can login to the Employee Management System with his/her user-
name and password

• Logout:The user can log out from the Employee Management System

• Login Failure:If the user does not exist in the database or the user is entering wrong
username or password

3.1.1.2 Authorization

• User Role Check: After logging in, the user role will be checked from the database
and the user interface will be displayed according to their role.

8
3.1 Requirments Specifications 9

3.1.1.3 Process Data

• Display: User with defined role can display the contents of the database. Being more
specific, employee can only view his/her personal information. Admin can see all
employees’ personal and professional information.

• Edit: A user with employee role cannot edit his/her information. Only admin can edit
employee’s personal and professional information. Admin can edit all information
related to all employee’s including their user role type.

• Search: Admin role can search all the employee’s information in the database.
Search feature works on specific keywords showing employee’s name, designation,
dicipline etc.

• Update Role: This feature can be used only by admin. Admin can update the role
type of a specific user. For example, an employee got promotion and his role type
will be changed from Assistant Professor to Associate Professor. Admin will be able
to update this employee role.

3.1.1.4 Leave Application/Approval

• Leave Application: The user can fill in leave application form in the appropriate
fields.

• Leave Approval: The admin can accept or reject leave application based on the
reasons stated.

3.1.1.5 Recruitment

• Add New Employee: Admin can add a new employee to the database. The new
employee will have all the required personal information related to him. The new
created employee will have an id. The unique id will be given by the system.

3.1.1.6 Attendance

• Mark Attendance: Admin can mark the attendance of employees. He can mark
attendance by Department. Admin can select the department then he can mark
attendance of employees of that specific department.

• Attendance Report: Admin can check the attendance report of employees. He can
check attendance report by three different ways. Firstly he can select starting date,
ending date and then report will be generated by those dates. Secondly he can view
attendance of some specific employees by entering employee’s ID and starting date
Requirement Analysis 10

and ending date. Thirdly he can view a specific department attendance by selecting
the department and entering starting and ending date. While an employee can only
view his/her own attendance by selecting starting and ending date.

3.1.1.7 Salary Management

• Basic Salary: Basic salary of employee will be automatically assigned to employee

when a employee is added to system. This salary will be assigned according to
designation of employee.

• Allowance: Admin can assign the allowance to employee according to his/her

education and previous work experience. It will be added to employee’s basic salary.

• Salary Deduction: Salary deduction is based on employees absents. On each absent

salary will be deducted automatically by system.

• View/Edit Salary: Admin can edit the allowance of an employee. He can also edit
the basic salary. But he can only edit the salary by designation, he cannot edit the
basic salary by some specific employee. While Employee can only view his basic
salary, allowance, absents and salary deduction according to his absent in employee
panel.

3.1.1.8 Admin Profile Management

• Add New Admin: Admin can add a new admin. Newly created admin will have
same role as its parent but it cannot edit or delete its parent or fellow admin. It can
only edit or delete its child admins.

• Edit Profile: Admin can change its own email address. It can also change its
password. Both these changes will happen only after admin authenticates himself by
entering his/her password.

3.1.1.9 Security

System will encrypt user password and maintain confidential record.

3.1.2 Non Functional Requirment

Following are the non-functional Requirements:

3.1.2.1 Accuracy

Providing accurate information as required by the user and real-time environment.

3.1 Requirments Specifications 11

3.1.2.2 Useability

Application is user friendly, interactive, attractive and easy to use.

3.1.2.3 Performance

The performance of the Application depends upon the network speed if resources are ac-
cessed through network. Overall the Response Time, Throughput, Utilization of application
is good.

3.1.2.4 Availability

The application will be available to the user locally but it requires internet connectivity to
sending request and getting information.

3.1.3 Software Requirment

• Android Studio

• Adobe XD

• Firebase Console

– Firebase Database
– Firebase Store
– Firebase Authentication

3.1.4 Hardware Requirment

• Desktop PC

– Min. 8GB RAM

– Min. 250GB HDD
– OS Win 7,8,10

• Android device

– Min. 2GB RAM

– Min. 16GB R0M
– Min. Android Version 6.0

• Stable Internet Connection

Chapter 4

System Design

The purpose of this chapter is to describe detailed architecture of "Employee Management

System". This chapter also explains the working, functionality, data flow and states of the
system through diagrams under which the proposed application will operate and how it
will behave.

4.1 Data Flow Diagram

Data Flow Diagram graphically representing the functions, or processes, which capture,
manipulate, store, and distribute data between a system and its environment and between
components of a system". DFD is the visual representation of the system that is very useful
for the communication between user and system designer. The hierarchical arrangement of
DFD can provide a broad view of the system as well as the detailed view. DFD has often
been used due to the following reasons:

• Logical information flow of the system

• Determination of physical system construction requirements

• Simplicity of notation

• Establishment of manual and automated systems requirements

4.1.1 Level-0

Level-0 also known as context diagram, is the highest level in a Data Flow Diagram.
This level of DFD makes it easier for business analysts to understand the boundaries of
the system. It represents a general flow of information between the system and external
components.

12
4.1 Data Flow Diagram 13

Figure 4.1: Context Level DFD

Level-0 DFD is made up of a context bubble, first drawn in the middle of the chart. It has
a circle shape that represents a conceptual boundary that encloses a group of interconnected
processes and activities of a project. In figure 4.1, bubble or circle represents the "Employee
Management System". This figure provides a general overview of the system, what this
system is supposed to do.

4.1.2 Level-1

Level-1 DFD is the expanded view of the level-0 diagram. Level-1 DFD represents basic
modules of the system and flow of data between various modules.
System Design 14

Figure 4.2: Level-1 DFD

Level-1 DFD of "Employee Management System" is shown in Figure 4.2. This diagram
shows a basic flow of data among various stages starting from the user and ending at the
final stages.

4.1.3 Level-2

A level-2 data flow diagram (DFD) offers a more detailed look at the processes as compared
to level-0 and level-1. It can provide information about different modules of the system
and shows their flow. It allows user to understand more about the working of the system.
4.1 Data Flow Diagram 15

Figure 4.3: Level-2 DFD

Figure 4.3 shows the level-2 data flow diagram of the system. It may require more
functionalities of Employee Management System to reach the necessary level of detail
about the Employee Management Functioning. The 2nd Level DFD contains more details
of task, attendance, finance, leave, performance, designation and departments etc
System Design 16

4.2 Flowchart

A flowchart is a type of diagram that represents a workflow or process. A flowchart can

also be defined as a diagrammatic representation of an algorithm, a step-by-step approach
to solving a task. Flowcharts play an extremely important role in displaying the flow of
information and various tasks in a system.

Figure 4.4: System Flowchart

4.2.1 Discription

Figure 4.4 shows a graphical representation of working of "EMS".The system consists of

two modules.In both modules of the application, the admin/employee will enter credentials
to log in.Once the admin/employee logs into the system, various tasks can be performed, if
admin/employee do not wants to login they can simply move the main page.In Admin side,
admin can manage employees.Admin can manage departments, manage employees salary,
manage attendance and manage designation. The other is Employee side. Employee can
view personal information, view his/her salary, request for leave, view attendance and
update password etc.
4.3 Entity Relationship Diagram 17

4.3 Entity Relationship Diagram

ER-modeling is a data modeling technique used in software engineering to produce a

conceptual data model of a information system. Diagrams created using this ER-modeling
technique are called Entity-Relationship Diagrams.

Figure 4.5: Entity Relationship Diagram

4.3.1 Discription

Figure 4.5 represents the ER Diagram of the system. In this diagram, the main entities are
admin and employee. Each admin and employee has it’s own keys and values. Admin table
contains a complete list of admin-related data. Employee table contains a complete list
of employee-related data. Employee designation, employee education, employee finance,
employee discipline, employee attendance, employee leaves, employee category, employee
promotion and employee fired history. Each table of employee data has it’s own keys and
values. In ER Diagrams, lines with various symbols are used to represent the relation of all
the entities with each other. Figure 4.5 shows admin has one-to-many relationship with
employee and an employee has one-to-many relationship with other emplyee tables.
System Design 18

4.4 Usecase Diagram

A use case diagram is a graphic depiction of the interactions among the elements of a
system. A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements.

4.4.1 Admin Use Case Diagram

Figure 4.6: Admin Use Case Diagram

4.4.1.1 Discription

Figure 4.6 represents the Admn Usecase Diagram of the system. In this diagram, the main
actor is the admin. The diagram shows various usecases i.e Log In, Employee Management,
Discipline Management, Salary Management, Attendance Management, Admin Profile
Management, Performance and Logout. Each usecase represent different functionalities
show in note links. Admin use case diagram simply represents Admin’s interaction with
the system that shows the relationship between the admin and the different use cases in
4.4 Usecase Diagram 19

which the admin is involved. It only summarizes some of the relationships between use
cases, actors, and systems. It does not show the order in which steps are performed to
achieve the goals of each use case.

4.4.2 Employee Use Case Diagram

Figure 4.7: Employee Use Case Diagram

4.4.2.1 Discription

Figure 4.7 represents the Employee Usecase Diagram of the system. In this diagram,
the main actor is the Employee. The diagram shows various usecases i.e Log In, View
Profile, View Attendance, View Salary, Leave, Change Password and Logout. Each usecase
represent different functionalities show in note links. Employee use case diagram simply
represents Employee’s interaction with the system that shows the relationship between
the employee and the different use cases in which the employee is involved. Basically, it
Specifies the context of a system.
System Design 20

4.5 Sequence Diagram

A sequence diagram shows object interactions arranged in time sequence. In simpler words,
a sequence diagram shows the sequence of different parts of a program to complete a task.

4.5.1 Admin Sequence Diagram

Figure 4.8: Admin Sequence Diagram

4.5.1.1 Discription

Figure 4.8 represents the Admin Sequence Diagram of the system. In this diagram, there
are three main lifelines i.e Admin, System and Database. The diagram shows all processes
in sequence. The admin logins the system, the system validates from database. Admin can
add employee. Add employee is recorded in database. Admin can add/remove discipline.
Add/remove discipline status is recorded in database. Admin can mark attendance. Marked
attendance is recorded in database. Admin can edit salary and allowance. The edit salary
and allowance status is recorded in database. Admin can manage leaves. The status is
recorded in database. Admin can mark performance. The status is recorded in database.
4.5 Sequence Diagram 21

Admin can manage profile. The status is recorded in database. Admin can logout. It is
recorded in database and the system shows Logout success message.

4.5.2 Employee Sequence Diagram

Figure 4.9: Employee Sequence Diagram

4.5.2.1 Discription

Figure 4.9 represents the Employee Sequence Diagram of the system. In this diagram,
there are three main lifelines i.e Employee, System and Dataabse. The diagram shows all
processes in sequence. The employee logins the system, the system validates from database.
Employee can view his/her profile and performance. The database shows. Employee can
view his financial status. The database shows. Employee can view his attendance and
attendance report. The database shows. Employee can request for leave. The leave request
status is recorded in database and updated after rejection or approval. Employee can update
password. It is recorded in database. Employee can logout. It is recorded in database and
the system shows Logout success message.
System Design 22

4.6 Activity Diagram

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. Activity diagram is basically a
form of flow chart that shows flow from one activity to antoher activity in a sequence.

4.6.1 Complete System

Figure 4.10: System Activity Diagram

4.6.2 Discription

Figure 4.10 shows a graphical representation of step-by-step activities of "EMS".The

system consists of two modules.In both modules of the application, the admin/employee
will enter credentials to log in.Once the admin/employee logs into the system, various
tasks can be performed.In Admin side, admin can manage employees.Admin can manage
discipline, manage employees salary, manage attendance, mark performance, manage
designation, add new admin and can Logout from the system. The other is Employee side.
4.6 Activity Diagram 23

Employee can view profile,view performance view his/her salary, request for leave, view
attendance, update password and can log out from the system.
System Design 24

4.7 Class diagram

A class diagram in the Unified Modeling Language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system’s classes, their
attributes, operations (or methods), and the relationships among objects.It is a type of static
structure diagram that describes the structure of a system by showing the system’s classes,
their attributes, operations (or methods).

Figure 4.11: System Class Diagram

4.7.1 Discription

Figure 4.11 shows the class diagram of the system. This class diagram consists of multiple
classes;Admin, employee, manage attendance, manage employee, manage salary, add
admin, designation etc Admin class represents the admin side of the system. It has
attributes and methods related to admin information e.g: name,id,cnic,email and password.
Employee class represents the employee side of the system. It has attributes and methods
related to employee information e.g empoyee id, name, password, email,cnic, phone etc.
All other classes are inherited or child classes of these two super classes. The child classes
have inherited attributes and methods and have also their own additional methods() to
maintain object orientation.
Chapter 5

System Implementation

This chapter describes the implementation of project.

5.1 Admin Application Interface

5.1.1 Main Page

Figure 5.1: Application Main Page

25
System Implementation 26

5.1.1.1 Description

The Figure 5.1 shows that the user (Admin and Employee) selects the choice as if they
want to login as admin or as employee in Employee management system to perform their
activities.

5.1.2 Admin Login Page

Figure 5.2: Admin Login

5.1.2.1 Description

The Figure 5.2 shows that the user (Admin) logins the system by writing his/her email,
password and tapping the login button to perform their activities. He/She can also move to
the main page by tapping the Go Home button.
5.1 Admin Application Interface 27

5.1.3 Admin Dashboard Page

Figure 5.3: Admin Dasboard

5.1.3.1 Description

The Figure 5.3 shows the Admin dashboard page in which he/she can view admin menu,
Leave requests, total present employees, total absent employees and basic administration
settings (Login Page,Change Password and Logout) to perfom these activities.
System Implementation 28

5.1.4 Sidebar Menu

Figure 5.4: Admin Sidebar Menu

5.1.4.1 Description

The Figure 5.4 shows that the Admin dashboard Sidebar Menu having Employee, Dis-
cipline, Finance, Attendance, Leave, Performance and Settings options. The admin can
perform any desired operation from given options of menu.
5.1 Admin Application Interface 29

5.1.5 Employee Page

Figure 5.5: Employee Page

5.1.5.1 Description

The Figure 5.5 shows the activities of Employee (option) from Admin Dashboard. At this
page admin can add new empoyees, can view list of allemployees, can add, edit and delete
employee categories, can add, edit, search and delete employee designation with salary,
can promote employee and can fire and rehire employee.
System Implementation 30

5.1.6 Discipline Page

Figure 5.6: Discipline Page

5.1.6.1 Description

The Figure 5.6 shows the activities of Discipline (option) from Admin Dashboard. At this
page admin can add, edit,search and delete discipline of Employees.
5.1 Admin Application Interface 31

5.1.7 Finance Page

Figure 5.7: Finance Page

5.1.7.1 Description

The Figure 5.7 shows the activities of Finance (option) from Admin Dashboard. At this
page admin can search employee to edit salary and allowance or to view his/her salary and
allowance.
System Implementation 32

5.1.8 Salary Deduction Page

Figure 5.8: Salary Deduction Page

5.1.8.1 Description

The Figure 5.8 shows the activities of Salary Deduction (icon) from Finance Page. At this
page admin can search employee by name to view his/her salary deduction and net salary.
5.1 Admin Application Interface 33

5.1.9 Attendance Page

Figure 5.9: Attendance Page

5.1.9.1 Description

The Figure 5.9 shows the activities of Attendance (option) from Admin Dashboard. At
this page admin can mark attendance of employees individually. Admin can also edit and
delete attendance.
System Implementation 34

5.1.10 Leave Page

Figure 5.10: Leave Page

5.1.10.1 Description

The Figure 5.10 shows the activities of Leave (option) from Admin Dashboard. At this
page admin can check the leaves of employees. He/She can accept leave, reject and set
leave on pending. He/ She can also check daily leave reports.
5.1 Admin Application Interface 35

5.1.11 Performance Page

Figure 5.11: Performance Page

5.1.11.1 Description

The Figure 5.11 shows that the activities of Performance (option) from Admin Dashboard.
At this page admin can view,edit,delete and mark the performance of employees.
System Implementation 36

5.1.12 Setting Page

Figure 5.12: Setting Page

5.1.12.1 Description

The Figure 5.12 shows the activities of Setting (option) from Admin Dashboard. At this
page admin can add more admins and can also change his/her name and password.
5.2 Employee Application Interface 37

5.2 Employee Application Interface

5.2.1 Login Page

Figure 5.13: Employee Login

5.2.1.1 Description

The Figure 5.13 shows that the user (Employee) logins the system by writing his/her email,
password and tapping the login button to perform their activities. He/She can also move to
the main page by tapping the Go Home button.
System Implementation 38

5.2.2 Employee Dashboard Page

Figure 5.14: Employee Dashboard

5.2.2.1 Description

The Figure 5.14 shows the Employee Dashboard Page in which the user (Employee) can
change his/her password, choose the menu to perform activities and can logout from
employee panel.
5.2 Employee Application Interface 39

5.2.3 Sidebar Menu

Figure 5.15: Employee Sidebar Menu

5.2.3.1 Description

The Figure 5.15 shows the Employee dashboard Sidebar Menu having Profile, Finance,
Attendance, Leave and Settings options. The employee can perform any desired operation
from given options of menu.
System Implementation 40

5.2.4 Employee Profile Page

Figure 5.16: Profile Page

5.2.4.1 Description

The Figure 5.16 shows all profile information of employee having First Name, Last Name,
CNIC, Email, Gender, Average Performance, Date of Birth, Phone, Join Date, Employee
Category and Designation. It also shows the performance of employee.
5.2 Employee Application Interface 41

5.2.5 Finance Page

Figure 5.17: Finance Page

5.2.5.1 Description

The Figure 5.17 shows cureent month salary status of employee having employee name,
discipline, actual salary, allowance, deducted salary, net salary, absent, and month.
System Implementation 42

5.2.6 Attendance Page

Figure 5.18: Attendance Page

5.2.6.1 Description

The Figure 5.18 shows attendance status of employee. Employee can search his/her
attendance by entering attendance status and by entering date.
5.2 Employee Application Interface 43

5.2.7 Attendance Report Page

Figure 5.19: Attendance Report Page

5.2.7.1 Description

The Figure 5.19 shows the attendance report page. The employee can enter start-date and
end-date of attendance and can click on show button. The system will show attendance
status with date.
System Implementation 44

5.2.8 Leave Page

Figure 5.20: Leave Page

5.2.8.1 Description

The Figure 5.20 shows the leave page. The employee can send the leave request to admin
by tapping on the leave button. Employee can enter leave reason, from date, to date and
can tap on Mark Request button. The employee can also search for already requested
leaves.
5.2 Employee Application Interface 45

5.2.9 Settings Page

Figure 5.21: Setting Page

5.2.9.1 Description

The Figure 5.21 shows the setting page in which employee can change his/her password
by entering old password, new password and confirming password. In this way, password
will be changed.
Chapter 6

System Testing

Testing is the process of validation and verification to confirm that system and its com-
ponents are working well to meet requirement specification and it is very critical part of
every project. Testing should be started from initial stage and its ongoing process while
developing software to avoid error rather than doing at end of project which may cost
in term of time which is very important factor to meet deadlines that’s why the system
is tested as much as possible at different stages of development. Following are different
testing techniques used by the system.

6.1 Functional testing

Functional testing is aimed to ensure that it is working as per the defined requirements. In
simple terms, checking whether the application performs the expected functions, which
are described in the specification.

6.1.1 Installing and running the application

Installing and running the application was a repetitive task which had to perform since
the very beginning of the development phase. Application was installed and checked after
every new functionality changed.
App was installed on following OS

• Android 6.0.1

• Android 7.2

• Android 8

• Android 9.0

46
6.2 Usability testing 47

6.1.2 Fields testing

All the required fields in the app are in functional state. Every necessary option required
for user input are tested.

6.1.3 Constant users feedback testing

All the feedbacks are tested to make user aware that their required option is working. User
is provided with all the necessary feedback and information after performing the tasks.

6.2 Usability testing

Usability testing is aimed to ensure the convenience of using the application, creates an
intuitive interface that conforms to accepted standards. Usability of any app is important
for better user experience. Various factors are tested that can affect the usability for the
user. All the buttons are of right size which are easily accessible by the user. Application
is navigating through all the pages properly. All the tasks are easy to perform. Font size is
optimal for the users. Every task is being performed efficiently without any lag.

6.3 User Interface

User Interface (UI) testing is performed to ensure the graphic user interface of your app
meets the specifications. User interface in my system is very user friendly. Every option
is described properly. Colors of buttons and tabs are giving positive impact on user.
Application is working on different devices with screens of various resolutions and screen
ratios.

6.4 Compatibility testing

Compatibility testing is performed to ensure application is performing similarly on all

compatible devices. This application is tested on various smartphones from different
manufactures including, Samsung, Huawei and Oppo. Database of system is working
optimally on android. Application is tested on various different networks of 3G, 4G and
wifi.

6.5 Security testing

Security testing is aimed to check the security of the system, as well as to analyze the risks
associated with the application. Application require employee and sub-Admin registration.
System Testing 48

Employee and Sub-Admin cannot login if id and password are not available in database.
User’s personal details like contact and address details are stored in Firebase which is
secured by Google.

6.6 TestCase

Following are test case tables of the system.

6.6.1 Installing App

Test Case No. 01

Function needed to test Installing the app in the device
Initial State App source file available in device
Input Install the app
Expected Output App must get installed on device and run
Output Installation Successful
Status Pass
Table 6.1: Installing Test Case

6.6.2 Admin Login

Test Case No. 02

Function needed to test Admin Login
Initial State App running in the device
Input Entering data in text fields of login page
User can login using the credentials entered in
Expected Output
fields
Output Login Successful
Status Pass
Table 6.2: Admin Login Test Case
6.6 TestCase 49

6.6.3 Add New Employee

Test Case No. 03

Function needed to test Adding new Employee
Initial State User logged into the app
Input Uploading picture and all required information
Expected Output Employee details received in the database
Employee Registered and Employee Addeed
Output
successfully message displayed to Admin
Status Pass
Table 6.3: Add New Employee Test Case

6.6.4 List All Employees

Test Case No. 04

Function needed to test View List of All Employees
User logged into the app and Employees must
Initial State
be registered
Searching employees from search bar or select-
Input
ing from employee list
Employee Profile must open allowing user to
Expected Output
view details and delete
User is able to view employee details and delete
Output
employee
Status Pass
Table 6.4: List All Employees Test Case

6.6.5 Employee Categories

Test Case No. 05

Function needed to test Adding new Categories for Employees
Initial State User logged into the app
Add new category name or edit the existing cat-
Input
egory
New Category Name or updated category name
Expected Output
received in the system
Output Employee Category Added Successfully
Status Pass
Table 6.5: Employee Category Test Case
System Testing 50

6.6.6 Employee Designation

Test Case No. 06

Function needed to test Add New Designation
Initial State User logged into the app
Add new designation name or edit and delete the
Input
existing designation
New Designation Name or updated designation
Expected Output
name received in the system
Output Employee Designation Added Successfully
Status Pass
Table 6.6: Employee Designation Test Case

6.6.7 Employee Promotion

Test Case No. 07

Function needed to test Promoting the Employee
Initial State Employee must be registered
Entering employee name, designation and date
Input
to be promoted
Employee must get promoted on the specefied
Expected Output
date and message displayed to the user
Output Employee Promoted Successfully
Status Pass
Table 6.7: Employee Promotion Test Case
6.6 TestCase 51

6.6.8 Fire Employee

Test Case No. 08

Function needed to test Fire Employee
Initial State Employee must be registered
Entering the employee name who has to be fired
Input
and date on which to be fired
Employee must get fired and message displayed
Expected Output
to the user
Output Employee Fired Successfully
Status Pass
Table 6.8: Fire Employee Test Case

6.6.9 Employee Discipline

Test Case No. 09

Function needed to test Add/Remove Discipline
Initial State User logged into the app
Entering the discipline name to add discipline,
Input
edit or delete the discipline
New discipline name or updated descipline name
Expected Output
received in the system
Output Employee Discipline Added Successfully
Status Pass
Table 6.9: Employee Discipline Test Case

6.6.10 Employee Finance

Test Case No. 10

Function needed to test Employee salary details
Initial State Employee must be registered
Entering the employee name to check and edit
Input
salary details
Expected Output Employee details must be displayed to the user
Employee salary details show and updated Suc-
Output
cessfully
Status Pass
Table 6.10: Employee Finance Test Case
System Testing 52

6.6.11 Employee Attendance

Test Case No. 11

Function needed to test Employee Attendance
Initial State Employee must be registered
Entering the employee name, attendance status
Input
and date
Attendance must marked and message displayed
Expected Output
to the user
Output Employee Attendance marked Successfully
Status Pass
Table 6.11: Employee Attendance Test Case

6.6.12 Employee Leave

Test Case No. 12

Function needed to test Manage Leave
Initial State Leave must be rquested
Input Change leave status or delete the leave
Expected Output Leave status updated and notified to employee
Output Leave updated Successfully
Status Pass
Table 6.12: Employee Leave Test Case

6.6.13 Employee Performance

Test Case No. 13

Function needed to test Employee Performance
Employee must be registered and attendance
Initial State
time must be recorded
Enter the employee name along with perfor-
Input
mance status and date
Employee performance must be marked and dis-
Expected Output
played to the user
Output Employee performance updated Successfully
Status Pass
Table 6.13: Employee Performance Test Case
6.6 TestCase 53

6.6.14 Admin Settings

Test Case No. 14

Function needed to test Admin Settings
Initial State User logged into the app
Update password of existing admin or Enter data
Input
of new admin
Update password or New admin must be added
Expected Output
and displayed to the user
Update password and new admin added Success-
Output
fully
Status Pass
Table 6.14: Admin Settings Test Case

6.6.15 Admin Logout

Test Case No. 15

Function needed to test Admin Logout
Initial State User logged into the app
Input Tap on the Logout button
Expected Output Logout from the system and move to home page
Output Admin Logout Successfully
Status Pass
Table 6.15: Admin Logout Test Case

6.6.16 Employee Login

Test Case No. 16

Function needed to test Employee Login
Initial State App running in the device
Input Entering data in text fields of login page
User can login using the credentials entered in
Expected Output
fields
Output Login Successful
Status Pass
Table 6.16: Employee Login Test Case
System Testing 54

6.6.17 Employee Profile

Test Case No. 17

Function needed to test Employee Profile
Initial State User logged into the app
Input Tap on profile option from dashboard
Expected Output All profile details displayed to the user
Output Employee Profile displayed Successfully
Status Pass
Table 6.17: Employee Profile Test Case

6.6.18 Employee Finance

Test Case No. 18

Function needed to test Employee finance details
Initial State User logged into the app
Input Tap on finance option from dashboard
Expected Output All finance details displayed to the user
Output Employee finance report displayed Successfully
Status Pass
Table 6.18: Employee Finance Test Case

6.6.19 Employee Attendance

Test Case No. 19

Function needed to test Employee Attendance
Initial State User logged into the app
Input Tap on attendance option from dashboard
All required attendance details displayed to the
Expected Output
user
Employee attendance report displayed Success-
Output
fully
Status Pass
Table 6.19: Employee Attendance Test Case
6.6 TestCase 55

6.6.20 Employee Leave

Test Case No. 20

Function needed to test Employee Leave
Initial State User logged into the app
Input Enter Leave Reason and duration
Leave requested to admin and displayed to the
Expected Output
user
Output Employee Leave requested Successfully
Status Pass
Table 6.20: Employee Leave Test Case

6.6.21 Employee Settings

Test Case No. 21

Function needed to test Change employee password
Initial State User logged into the app
Enter old password, new password and confirm
Input
password
Expected Output Updated password added in the system
Output Employee Password updated Successfully
Status Pass
Table 6.21: Employee Settings Test Case

6.6.22 Employee Logout

Test Case No. 22

Function needed to test Employee Logout
Initial State User logged into the app
Input Tap on the Logout button
Expected Output Logout from the system and move to home page
Output Employee Logout Successfully
Status Pass
Table 6.22: Employee Logout Test Case
System Testing 56

6.7 Result

All the above tests were performed on following devices

• Oppo A57

• Oppo A12

• Samsung s7 Edge

• Huawei Y7 Prime

All those devices running following Operating systems respectively

• Android 6

• Android 7

• Android 8

• Android 9

Performed all the tests mentioned above on the above mentioned devices. Installed
final app on the devices. App ran similarly on each devices. But there was an issue of
performance on old devices like Samsung Galaxy s6 with Android 7. Response time on
older devices is bit slow. Response time also slows down with the slow internet. Overall
functionalities worked without any issue on every device mentioned.
Chapter 7

Conclusion

In this age of technology mobile phones and internet are widely used by large number
of population. System objective is to provide a useful platform to the administration and
the employees for easy management. After developing this project it introduces the new
trend of management between administration and employees of any institute. Android
platform will be very helpful in managing data, daily tasks like attendance and reports.
An interactive android based interface for the administration by which users can use to
manage all the departments and employees of any organization.

7.1 Future Enhancement

Every system never gets completed; continuous improvements are part of software devel-
opment. With the passage of time system enhance user experience by increasing security
and performance. It can bring more features and various types of promotions for the ease
of user. The system is completely resilient that can bear any change and merge the change
into it.

7.1.1 Integration with Payroll System

In order for the system to be more comprehensive, it is recommend to integrate the system
with payroll system that enables employees to view and download their pay slips on
demand.

7.1.2 Information Archiving

A system holding all the employee information should have some form of archiving system
so that retired, suspended or fired employees are archived rather than been completely

57
Conclusion 58

deleted from the system. This is so because cases may occur where details of an ex-
employee may be required especially in cases where an employee did several projects and
there details are required for future references.

7.1.3 Complain Box

Complain box can be created to register and store complains.

7.1.4 Live Chat

Interactions among various employees of the organization through live chats.

7.1.5 Theme & Appearance

UI Panel that shows menu and settings to change the theme and overall appearance of
application.
References

[1] Nitin Deshdeep. App or Website? 10 Reasons Why Apps are Better: Vwo blog, 2020.
https://vwo.com/blog/10-reasons-mobile-apps-are-better/
. Cited on p. 2.
[2] Raje Fndo. Incremental Model in SDLC: Use, Advantage and Disadvantage: gurru99,
2020.
https://www.guru99.com/what-is-incremental-model-in-sdlc\
-advantages-disadvantages.html/
. Cited on p. 3.
[3] Kellerman. Review of literature on employee management : Uk essays, 2020.
https://www.ukessays.com/essays/management/
review-of-literature-on-employee-management-management-essay.
php
. Cited on p. 6.
[4] Pete Needham. OrangeHRM : Desktop application, 2020.
https://www.orangehrm.com//
. Cited on p. 6.
[5] Helen Ramsey. Waypoint HR : Web app, 2020.
https://selection.waypointhr.com/
. Cited on p. 6.
[6] Google. Employee Management System: Attendance Manager : Mobile app, 2020.
https://play.google.com/store/apps/details?id=com.droid.
tech.employeemanager&hl=en
. Cited on p. 6.
[7] Google. HR Management System - Employee Attendance : Mobile app, 2020.
https://play.google.com/store/apps/details?id=com.pract.
employeemanager&hl=en
. Cited on p. 6.
[8] Josh Bersin. Tinypulse : System software, 2020.
https://www.tinypulse.com/
. Cited on p. 7.

59