PANIMALAR INSTITUTE OF TECHNOLOGY

CHENNAI – 600 123

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CS8582–OBJECT ORIENTED ANALYSIS AND dESIGN LABORATORY

EMPLOYEE TRACKING SYSTEM

MINI PROJECT REPORT

Submitted by

GANAPATHI HARSHITHA (211517104043)

LIKITHA.R (211517104085)
MALAPATI BHAVYA SAI SREE (211517104049)

in the Fifth semester of

Bachelor of Engineering

in

Computer Science and Engineering

during the academic year 2019 - 2020

 PANIMALAR INSTITUTE OF TECHNOLOGY
CHENNAI – 600 123

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CS8582–OBJECT ORIENTED ANALYSIS AND DESIGN LABORATORY

This is to certify that the Mini Project entitled “EMPLOYEE TRACKING

SYSTEM” is the bonafide record of the work done by GANAPATHI
HARSHITHA(211517104043), LIKITHA.R (211517104085)and MALAPATI
BHAVYA SAI SREE (211517104049) of Third Year B.E - CSE during the
academic year 2019 – 2020.

Head of the Department Project Supervisor

CHAPTER NO. TITLE PAGE NO.

ABSTRACT

1. INTRODUCTION 6
1.1 Purpose 7
1.2 scope 7

2. PROJECT MODULE 8
2.1 Problem Definition 8

3. EXISTING SYSTEM 9
3.1 Limitations of existing system 9

4. SYSTEM DESIGN 10
4.1System functionality
4.2Architectural design

5. PROPOSED SYSTEM 12
5.1 Algorithms 13

6. FUNCTIONAL MODELING 14
6.1 Level 0 14
6.2 Level 1 15

7. UML MODELING 16
7.1 Use Case Diagram 16
7.2 Class diagram 18
7.3Activity Diagram 20
7.4 Sequence diagram 22

8. APPLICATION 24
8.1 Implementation Tools 24

9. TESTING 25

10. REPORT 26
10.1 Employee Performance 26
 10.2 Task Report 26
10.3 Employee Task Report 26
10.4Schedule Report (Employee Track Schedule Report) 26
10.5 Employee Reasons Report 27

11. RESULT 28
11.1 Main Activity Screen 28
11.2 Employee Tracking Screen 29
11.3 View Call Log Screen 30
11.4 Employee Performance Screen 31

12. CONCLUSION 32

13. REFERENCES 33
ABSTRACT:-

The client uses MS Excel, and maintains their records, however it is not
possible them to share the data from multiple system in multi user
environment, there is lot of duplicate work, and chance of mistake.
Then the records are changed they need to update each and every excel
file. There is no option to find and print previous saved records.
There is no security anybody can access any report and sensitive data,
also no reports to summary report.
This Employee Tracking System is used to overcome the entire problem
which they are facing currently, and making complete atomization of
manual system to.
Due to the use of company computers, telephones, workspaces, and
software, employers can have access to the daily activities of their
employees. These devices are used to monitor the organizations'
employees. Common methods of monitoring include software
monitoring, telephone tapping, video surveillance, email monitoring, and
location monitoring.
Software monitoring can occur if employees use company computers
for their work, companies often utilize employee monitoring software
that allows them to track what their employees are doing on the
computers. Such as, what the speed of typing is, what mistakes are
made, what applications were used, and what specific keys were pressed.
Telephone tapping can be used to recover employees' phone call details
and conversations. These can be recorded during monitoring. The
number of calls, the duration of each call, and the idle time between
calls, can all go into an automatic log for analysis by the company.
Video surveillance can provide video feed of employee activities that
are passed through to a central location where they are monitored live by
another person. These can be recorded and stored for future reference
which some believe is the most accurate way to monitor employees

CHAPTER 1

1. INTRODUCTION:

• Employee tracking system monitored and tracks companyemployee’s using android

technology.
• The application which developed for employee tracking iscalled as “Mitter-bitter”.
• The manager can track Employees all day to day activitieslike SMS, call logs, data usage, web
browser history,unauthorized calls. It also tracks the current location ofthe Employee.

In today’s world, man struggles to make his life easier. The need for tracking has assumed high
importance because of varied and diverse resources, then be it a product of a company being
shipped from the company to consumer, be it the assets, and be it in the supply chain
management or for that matter even the man-power. In large organizational buildings, where the
man-power is high, people are not always in their cabins.

They have to wander from room to room, floor to floor to perform their work. In such cases, it
becomes extremely difficult to keep a track of people and find them when they are needed.

Solution for the above problem is as further a tracking system which can track an individual
when they enter a room would suffice the need. This process should take place in a hassle free
manner and therefore a wireless system would be advantageous.
A receiver can be placed in each of the rooms in the building and connected to a computer
system which can take input from the connected receiver and enter it in a database of all
individuals or personnel in the building.

The receiver would receive input from a transmitter which would be given to all the people
working in the building. Since all the information is logged in a database, any person in the
building will be able to access this information through any computer connected to this system
and come to know the location of the person he or she is seeking for.

The system architecture consists of simple format of Central system and peripheral system.

1. Peripheral systems: It includes nodes, desktops that accept information from the RFID readers
which are mounted on the doors or at entry to any department.

2. Central systems: It includes server that handles all information of desktops. Server also
controls time, attendance, log and manage database.

3. Front end consist of GUI for administrator that do tracking.

4. Back end consist of Database that maintaining log and database, Time and attendance of
employee.

1.1 PURPOSE:
Our proposal is to create an "Employee Tracking System" for a company for the purpose of:

 generating payroll
 keeping weekly records of employees (i.e. hours worked, vacation time, etc.)
 viewing employee record
 viewing projects (i.e. employees involved, supervisors, hours spent, etc.)
 allocating spending limits to departments, supervisors and projects for employees
 indicating the needs and excesses of employees to human resources

1.2 SCOPE:
The scope of this project is divided into few main elements which are users, system operability,
functionality and development tool User

a) Employee In this system, user is allowable to register in this system and update their
information in the system to enable the employer to track the registered employee.

b) Manager, bosses, Principle or supervisor The manager, Principle, supervisor or bosses only
allow searching employee, register, viewing data and Location of their employee.
 c) Administrator For the administrator, they are important user in this system because they allow
adding, updating, deleting, viewing and searching the user in the system beside to search the
employee location.

CHAPTER 2
2. PROJECT MODULE
A software system is always divided into several sub systems that makes it easier for the
development and testing. The different subsystems are known as the modules and the process of
dividing an entire system into subsystems is known as modularization or decomposition. The
different modules are:

1. Add New Employee: This operation is performed when new employee needs to be added to
the system, for e.g. when company recruits a new employees, their entry is inserted in the
employee database. This option has three choices:

2. Manage Log: When Employee passes from door his information is get retrieved in database
and log of entire day will be stored in database means it gives where employee has gone through
departments.

3. Time And Attendance: This module keeps entry time of employee into company and
maintains attendance of employee.

4. Tracking: This module is used to track particular employee and gives flow which is followed
by employee throughout the day in the company.
5. Authentication Of Employee: When employee passes using RFID Tags through doors using
RFID readers he must be authenticated by using capturing g image of employee. If any employee
is doing proxy of any one it can be easily identified by administrator and following action must
be taken on that employee.

6. Provide Interactive GUI: This gives user simple interaction through the system.

7. Administrator Login: It gives authentication for administrator for system.

8. Requirement analysis

2.1 PROBLEM DEFINITION:

There are some problems arises in previous tracking system are:
- Inconsistency in data.
- Loss of data.
- Insecure communication between mobile and central server.
- Inaccurate location tracking.

CHAPTER 3

3. EXISTING SYSTEM
 AnjorJadhav was developed ”Track Your Buddies”Application.
 Ms.BhagyaPandurangaNaik “SAR operation based on calllog and location
details using GPSand Android Smartphone”.
 AbhishekBarve “Android Based Remote MonitoringSystem”.

3.1 Limitations of existing system

 The manager cannot trace out the Employee‘s activities likeweb history,
unauthorized call history and unauthorizedweb list in the mobile.
 The manager cannot know the Employee‘s behaviour.
 Manager cannot get alert message on his/her mobile phone.
 As a model of a complicated system (the code), it's still fairly complicated.
Many people have pointed out in comments that my complaint above is
invalid because there's a type of diagram that can do what I want. This
represents a different problem: it's hard enough to remember the details of
 the UML that using it as a simple model for communication purposes is
difficult.
 As a code generation (or code analysis) tool, its capabilities may not map
exactly onto your target language. It's designed for class-based object-
oriented programming languages and for compile-time method resolution. I
have difficulties getting more than the simplest representation of Objective-
C or Javascript out of it.
 Lack of expressiveness:

 it's hard to point out what's important, and what's not

 pure text allows you more flexibility when explaining things
 it only shows one isolated aspect at once (either the class diagrams, the
uses cases, the flow, etc) but usually, what you need for a good
understanding is a mix of those

CHAPTER 4

4. SYSTEM DESIGN

 The systems objectives outlined during the feasibility study serve as the basic from which
the work of system design is initiated.
 Such of the activities involved at this stage is of technical nature requiring a certain
degree of experience in designing systems, sound knowledge of computer related
technology and through understanding of computers available in the market and the
various facilities provided by the vendors. 1evertheless, a system cannot be designed in
isolation without the active involvement of the user.
 The user has a vital role to play at this stage too. !s we know that data collected during
feasibility study wills we utilized systematically during the system design.
 It should, however be kept in mind that detailed study of the existing system is not
necessarily over with the completion of the feasibility study.
 Depending on the plan of feasibility study, the level of detailed study will vary and the
system design stage will also vary in the amount of investigation that still needs to be
done.
 This investigation is generally an urgent activity during the system.
 Sometimes, but rarely, this investigation may form a separate stage between feasibility
study and computer system design.
  Designing a new system is a creative process, which calls for logical as well as lateral
thinking.
 The logical approach involves systematic moves towards the end product keeping in
mind the capabilities of the personnel and the equipment at each decision making step.
2ateral thought implies encompassing of ideas beyond the usual functions and equipment.
 This is to ensure that no efforts are being made to fit previous solutions into new
situations.

4.1 System functionality:

For the functionality of this system, the main function of the system is search
location of the employee during work hour beside the employer or administrator to
retrieve database such as add, update and deletion of each employee record besides
records the current location, date and time accessed by the each user. User also
allows registering and updating the information in the system.

4.2Architectural design:
EMPLOYEE

CHAPTER 5

5. PROPOSED SYSTEM
5.1 ALGORITHMS:
 o K-Means clustering
 It calculates the employee’s behaviour (Goodloyal/
 Average/Bad)

o AES encryption algorithm

 Data stored are secured using encryption algorithm.

Defect tracking systems are most commonly used in the coding and testing phases
of the software development process .
However, tracking systems can in fact be used for many other purposes such as
general issue tracking, simple task lists, help desk situations or contact
management, where the focus is on the tracking aspect rather than what is being
tracked .
Even in software development, tracking systems are quite often not limited to
simply tracking Defects, but extended to track feature requests or enhancements as
well as enquiries . Advantages of the proposed system are:
 Efficient centralized database schema
. Increased security with access only to authorized personnel.
 Quick report generation.
 Easy to update the records and track the defects.
 CHAPTER 6

6.FUNCTIONAL MODELING:

FR-1 Administrator shall be able to Login to the system.

FR-2 The system shall allow administrator to add new design department.
FR-3 The system shall allow administrator to Add/ Edit new defects.
FR-4 The system shall allow administrator to Add/ Edit priority to the defects.
FR-5 The system shall allow administrator to add new projects to the system.
FR-6 The system shall allow administrator to add new modules to the existing
projects.
FR-7 The system shall allow administrator to generate reports corresponding to the
status of each defect i.e. is it under process, completed or pending?
FR-8 The system shall allow administrator to add new employee or update existing
employee’s status in the system.
FR-9 The system shall allow administrator to change/update the status of the
defects.
FR-10 The system shall allow administrator to assign the bugs to a particular
employee new defects.

6.1 Level 0 DFD:

6.2 Level 1 DFD:
 CHAPTER 7

7. UML MODELING:

 UML is not a programming language, it is rather a visual language. We

use UML diagrams to portray the behavior and structure of a system.
 UML helps software engineers, businessmen and system architects with
modelling, design and analysis. The Object Management Group (OMG)
adopted Unified Modelling Language as a standard in 1997. I
 ts been managed by OMG ever since.
 International Organization for Standardization (ISO) published UML as an
approved standard in 2005. UML has been revised over the years and is
reviewed periodically.
Do we really need UML?
 Complex applications need collaboration and planning from multiple teams
and hence require a clear and concise way to communicate amongst them.
 Businessmen do not understand code. So UML becomes essential to
communicate with non programmers essential requirements, functionalities
and processes of the system.
 A lot of time is saved down the line when teams are able to visualize
processes, user interactions and static structure of the system.

Structural UML Diagrams –

 Class Diagram – The most widely use UML diagram is the class diagram. It is the
building block of all object oriented software systems. We use class diagrams to depict
the static structure of a system by showing system’s classes,their methods and attributes.
Class diagrams also help us identify relationship between different classes or objects.
 Composite Structure Diagram – We use composite structure diagrams to represent the
internal structure of a class and its interaction points with other parts of the system. A
composite structure diagram represents relationship between parts and their configuration
which determine how the classifier (class, a component, or a deployment node) behaves.
They represent internal structure of a structured classifier making the use of parts, ports,
and connectors. We can also model collaborations using composite structure diagrams.
They are similar to class diagrams except they represent individual parts in detail as
compared to the entire class.
 Object Diagram – An Object Diagram can be referred to as a screenshot of the instances
in a system and the relationship that exists between them. Since object diagrams depict
behaviour when objects have been instantiated, we are able to study the behaviour of the
system at a particular instant. An object diagram is similar to a class diagram except it
 shows the instances of classes in the system. We depict actual classifiers and their
relationships making the use of class diagrams. On the other hand, an Object Diagram
represents specific instances of classes and relationships between them at a point of time.
 Component Diagram – Component diagrams are used to represent the how the physical
components in a system have been organized. We use them for modelling
implementation details. Component Diagrams depict the structural relationship between
software system elements and help us in understanding if functional requirements have
been covered by planned development. Component Diagrams become essential to use
when we design and build complex systems. Interfaces are used by components of the
system to communicate with each other.
 Deployment Diagram – Deployment Diagrams are used to represent system hardware
and its software.It tells us what hardware components exist and what software
components run on them.We illustrate system architecture as distribution of software
artifacts over distributed targets. An artifact is the information that is generated by system
software. They are primarily used when a software is being used, distributed or deployed
over multiple machines with different configurations.
 Package Diagram :- We use Package Diagrams to depict how packages and their
elements have been organized. A package diagram simply shows us the dependencies
between different packages and internal composition of packages. Packages help us to
organise UML diagrams into meaningful groups and make the diagram easy to
understand. They are primarily used to organise class and use case diagrams.

Behavior Diagrams –

1. State Machine Diagrams – A state diagram is used to represent the condition of the system
or part of the system at finite instances of time. It’s a behavioral diagram and it represents
the behavior using finite state transitions. State diagrams are also referred to as State
machines and State-chart Diagrams . These terms are often used interchangeably.So
simply, a state diagram is used to model the dynamic behavior of a class in response to time
and changing external stimuli.
2. Activity Diagrams – We use Activity Diagrams to illustrate the flow of control in a system.
We can also use an activity diagram to refer to the steps involved in the execution of a use
case. We model sequential and concurrent activities using activity diagrams. So, we
basically depict workflows visually using an activity diagram.An activity diagram focuses
on condition of flow and the sequence in which it happens. We describe or depict what
causes a particular event using an activity diagram.
3. Use Case Diagrams – Use Case Diagrams are used to depict the functionality of a system
or a part of a system. They are widely used to illustrate the functional requirements of the
system and its interaction with external agents(actors). A use case is basically a diagram
representing different scenarios where the system can be used. A use case diagram gives us
a high level view of what the system or a part of the system does without going into
implementation details.
4. Sequence Diagram – A sequence diagram simply depicts interaction between objects in a
sequential order i.e. the order in which these interactions take place.We can also use the
 terms event diagrams or event scenarios to refer to a sequence diagram. Sequence diagrams
describe how and in what order the objects in a system function. These diagrams are widely
used by businessmen and software developers to document and understand requirements for
new and existing systems.
5. Communication Diagram – A Communication Diagram(known as Collaboration Diagram
in UML 1.x) is used to show sequenced messages exchanged between objects. A
communication diagram focuses primarily on objects and their relationships. We can
represent similar information using Sequence diagrams,however, communication diagrams
represent objects and links in a free form.
6. Timing Diagram – Timing Diagram are a special form of Sequence diagrams which are
used to depict the behavior of objects over a time frame. We use them to show time and
duration constraints which govern changes in states and behavior of objects.
7. Interaction Overview Diagram – An Interaction Overview Diagram models a sequence of
actions and helps us simplify complex interactions into simpler occurrences. It is a mixture
of activity and sequence diagrams.

7.1 Use Case Diagram:

 A use case is a set of scenarios that describing an interaction between a user and a
system. A use case diagram displays the relationship among actors and use cases. The
two main components a user or another system that will interact with the system
modeled. A use case is an external view of the system that represents some action the
user might perform in order to complete a task.
 Use case diagrams consists of actors, use cases and their relationships.
The diagram is used to model the system/subsystem of an application. A single use case
diagram captures a particular functionality of a system.

 The purpose of use case diagram is to capture the dynamic aspect of a system. However,
this definition is too generic to describe the purpose, as other four diagrams (activity,
sequence, collaboration, and Statechart) also have the same purpose.
 We will look into some specific purpose, which will distinguish it from other four
diagrams.
 Use case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. Hence, when a
system is analyzed to gather its functionalities, use cases are prepared and actors are
identified.
When the initial task is complete, use case diagrams are modelled to present the outside view.
In brief, the purposes of use case diagrams can be said to be as follows −
 Used to gather the requirements of a system.
 Used to get an outside view of a system.
 Identify the external and internal factors influencing the system.
 Show the interaction among the requirements are actors.
7.2 Class Diagram:

 Class Diagram provides an overview of the target system by describing the objects and
classes inside the system and the relationships between them. It provides a wide variety
of usages; from modeling the domain-specific data structure to detailed design of the
target system. With the share model facilities, you can reuse your class model in the
interaction diagram for modeling the detailed design of the dynamic behavior
 Class diagram describes the attributes and operations of a class and also the constraints
imposed on the system. The class diagrams are widely used in the modeling of
objectoriented systems because they are the only UML diagrams, which can be mapped
directly with object-oriented languages.
 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.
 The class diagram is the main building block of object-oriented modeling. It is used for
general conceptual modeling of the structure of the application, and for detailed modeling
translating the models into programming code.
 Class diagrams can also be used for data modeling.[1] The classes in a class diagram
represent both the main elements, interactions in the application, and the classes to be
programmed.
In the diagram, classes are represented with boxes that contain three compartments:

 The top compartment contains the name of the class. It is printed in bold and centered, and
the first letter is capitalized.
 The middle compartment contains the attributes of the class. They are left-aligned and the
first letter is lowercase.
 The bottom compartment contains the operations the class can execute. They are also left-
aligned and the first letter is lowercase.
7.3 Activity Diagram:

 The activity diagram used to describe flow of activity through a series of actions. Activity
diagram is a important diagram to describe the system. An activity diagram shows the
overall flow of control.
 An activity diagram visually presents a series of actions or flow of control in a system
similar to a flowchart or a data flow diagram. Activity diagrams are often used in
business process modeling. They can also describe the steps in a use
case diagram. Activities modeled can be sequential and concurrent.

 The basic purposes of activity diagrams is similar to other four diagrams. It captures the
dynamic behavior of the system. Other four diagrams are used to show the message flow
from one object to another but activity diagram is used to show message flow from one
activity to another.
 A ctivity is a particular operation of the system. Activity diagrams are not only used for
visualizing the dynamic nature of a system, but they are also used to construct the
executable system by using forward and reverse engineering techniques. The only
missing thing in the activity diagram is the message part.
 It does not show any message flow from one activity to another. Activity diagram is
sometimes considered as the flowchart. Although the diagrams look like a flowchart,
they are not. It shows different flows such as parallel, branched, concurrent, and single.
 The purpose of an activity diagram can be described as −
Draw the activity flow of a system.
Describe the sequence from one activity to another.
Describe the parallel, branched and concurrent flow of the system.

 This is the login activity diagram of attendance management system which shows the
flows of login activity where admin will be able to login using their user name and
password.
 The diagram below helps demonstrate how the login page works in a attendance
management system.
7.4 Sequence diagram:

 The Sequence Diagram models the collaboration of objects based on a time sequence. It
shows how the objects interact with others in a particular scenario of a use case. With the
advanced visual modeling capability, you can create complex sequence diagram in few
clicks. Besides, VP-UML can generate sequence diagram from the flow of events which
you have defined in the use case description.
 A sequence diagram simply depicts interaction between objects in a sequential order i.e.
the order in which these interactions take place. We can also use the terms event
diagrams or event scenarios to refer to a sequence diagram. Sequence diagrams describe
how and in what order the objects in a system function. These diagrams are widely used
by businessmen and software developers to document and understand requirements for
new and existing systems.

 UML Sequence Diagrams are interaction diagrams that detail how operations are carried
out.
 They capture the interaction between objects in the context of a collaboration. Sequence
Diagrams are time focus and they show the order of the interaction visually by using the
vertical axis of the diagram to represent time what messages are sent and when.

 Model high-level interaction between active objects in a system

 Model the interaction between object instances within a collaboration that realizes a use
case
 Model the interaction between objects within a collaboration that realizes an operation
 Either model generic interactions (showing all possible paths through the interaction) or
specific instances of a interaction (showing just one path through the interaction)

Sequence diagrams can be useful references for businesses and other organizations. Try drawing
a sequence diagram to:

 Represent the details of a UML use case.

 Model the logic of a sophisticated procedure, function, or operation.
 See how objects and components interact with each other to complete a process.
 Plan and understand the detailed functionality of an existing or future scenario.
 CHAPTER 8

8.APPLICATIONS

- Company
- Hotels
- Institutes

8.1 IMPLEMENTATION TOOLS:

Net Beans
Android Studio
 CHAPTER 9

9. TESTING

The component and the integrated entire are carefully verified to confirm there no error and fully
meet the requirement. they normally a series of tests, which are run to check the performance of
the software, and also to find if any new bugs were introduced into the system, after the previous
bugs were fixed.

If any more errors do exist, the bugs are fixed only to be retested.

In our Defect tracking system, we are using MS Access database for data storage . We are
running database on local machine . Database connectivity is done by following the regular
database connectivity steps .

This database is stored on the local machine which is secured by an username and password.

This database can only be accessed using ODBC Data Sources Workspace using the assigned
user and password, thereby enforcing the data security.

Login Details of the users are saved in LOGINDETAILS Table.

This data is important and must be secured from any unauthorized access. This data must be
saved or backed up on separate hard disk drive.

From the applications point of view, it makes no difference when it accesses a relational database
or parses xml files.

The UML is usually able to create an instance of a data object ("to read data") and also to persist
data ("to save data") to the data source .

Data Access Objects can be used in a large percentage of applications - anywhere data storage is
required.

 hide all details of data storage from the rest of the application.

 act as an intermediary between your application and the database. They move data back

 and forth between Java objects and database records and allow ripple effects from possible
changes to the persistence mechanism to be confined

 to specific area.
Evalution of tests:
Testing is one of the main stages in the development process in which we check
the project for the different data sets and to see which the cases in which the
project failed are.

This helps in deciding which necessary steps that can be taken to make sure that
the system is immune to such kind of data inputs in the future. In our project we
have used the above mentioned test cases.

These test cases from TC1 to TC11 test all the important functionalities of the
system and pinpoint the cases which make the system fail.

Our system failed for test cases TC1 and TC2 where, if the priority of the bug was
set to some number other than 1 or 2 then system crashed.

To overcome such problem in future we restricted the input from the user to only 1
and 2 using dropdown list.

The table below mentions the summary of all the test cases; which of them passed
and which of them failed along with the recuperative action that we took to prevent
the failing cases.
 CHAPTER 10

10. REPORTS
1. Employee performance
2. Task Report
3. Employee Task report
4. Schedule Report
5. Employee Reasons Report
6. Message notification Report

10.1 Employee Performance:-

It helps in monitoring employee performance as per no. of task completed by a individual

employee. It gives the details information of task assigned with status of that task. Admin can
see the tasks assigned between by dates. According to tasks assigned to a particular employee
Admin Can Generate Report.

10.2 Task Report:-

In this Admin can generate Reports as per no. of task given to an employee In particular span
Ofdates.
It gives the Employee name with task assigned and status of task.
Tools option to print, save as PDF, Export to Excel.

10.3 Employee Task Report:-

It helps admin to change the status of task assigned to a particular employee as (open,
ongoing, on hold, close, all).
Employee task provide all tasks details like

(Task Description, Task Category, contact person, Address, status, action). Admin can print,
saves as PDF, Export to Excel in tools.

10.4 Schedule Report (Employee Track Schedule Report):-

It Helps in Tracking Employee Details From date to date with (Employee name, tracking
data, travel Distance, travel Duration).
10.5 Employee Reasons Report:-

It helps in monitoring employee leave, reason of not completing task or any other specific
reason.
Generating report as per requirement by clients.

10.6 Message Notification Report:-

It helps in monitoring the message sent through a particular employee mobile no. with date.
According with admin can print, save as PDF, Export in tools option.
 CHAPTER 11

11. RESULT

11.1 Main Activity Screen:

11.2 Employee Tracking Screen:
11.3 View Call Log Screen:
11.4 Employee Performance Screen:
 CHAPTER 12

12. CONCLUSION

 Employee tracking system uses android smartphone fortracking.

 “Employee tracking system using android phone” is a application which
monitors the employee’s cell phonesprovided by the organization.
 By using this system it is possible for the manager to trackan employee in
the organization and calculate the behaviorof the employee using K-Means
clustering algorithm.
 CHAPTER 13
13. REFERENCES

 -"MOSES:Supportingand Enforcing Security Profiles

onSmartphones"YuryZhauniarovich,Giovanni Russello, Mauro Conti,Bruno Crispo, and
EarlenceFernandes, IEEE transactions ondependable and secure computing,2014.
o AnjorJadhav,SavitaKharje, Pooja More and Prof. Nasim Shah, “Track Your
Buddies,” proceedings of national conference on new horizons inIT-NCNHIT
2013 .
o AbhishekBarve,Pragnesh Shah, ―Android based remote
monitoringsystem―,International Conference in recent trends in
informationtechnology and computer science(ICRTITCS- 2012
 [1] OrangeHRM Open Source, Retrieved: November 4, 2013. From:
http://www.orangehrm.com/open-source-product-featurespim.shtml
 [2] A.S.SyedNavaz, A.S. SyedFiaz, C. Prabhadevi, V. Sangeetha, S. Gopalakrishnan,
“Human Resource Management System”, IOSR