CERTIFICATE

This is to certify that the project entitled, “HUMAN RESOURCE

MANAGEMENT SYSTEM”, is benefited Work of VISHAL P.AWAN
RAJBHAR bearing Seat. No: 606submitted in partial fulfillment of the
Requirements for the award of degree of BACHELOR OF SCIENCE in
INFORMATION TECHNOLOGY Form University of Mumbai.

Internal Guide Coordinator

External Examiner
Date:- college seal
ACKNOWLEDGEME.NT
 I express sincere gratitude of Professor Mr
Suryaprakash Upadhyay on my project guide for
making available, the facilities required for the
completion of the project.

 I greatly indebted to my project guide for his

valuable and timely guidance along with his
 Wholehearted cooperation, which has played a key
role in the successful completion of the project.

 A vote of thanks to all staff members of Ramanand

Arya D.A.V College, who have directly or indirectly,
contributed towards the completion of the project.

 I would also like to thank the non-teaching staff

members of the college for allowing me to use the
laboratory facilities for as much time as required
DECLARATION
 I hereby declare that the project entitled, “HUMAN
RESOURCE MANAGEMENT SYSTEM” done at
Ramanand Arya D.A.V
College, has not been any case duplicated to submit
to any other university for the AWARD OF any degree.
To the best of my knowledge other than me, no one
has submitted to any other university.

 The project is done In partial fulfillment of the

requirements for the award of degree of BACHELOR
OF SCIENCE
(INFORMATION TECHNOLOGY) to be submitted as
final semester project as part of our curriculum.
Index
Chapter 1:- INTRODUCTION
•Object
•Purpose
•Scope
•Achievement
Chapter 2:-SURVEY OF TECHNOLOGY
• Front-end technology

• Back-end technology
• Database management system
Chapter 3:-SYSTEM REQUIREMENTS SPECIFICATION
 Performance Requirements
 Functional Requirements
 FEASIBILITY STUDY
Chapter 4:- SYSTEM
DESIGN
 USE CASE DIAGRAM
 IS DIAGRAM
 CONTEXT DIAGRAM
 Activity diagram
 DATA FLOW DIAGRAM
 CONCLUSIONS
 Reference
 Chapter 1:- INTRODUCTION ABOUT
PROJECT

The human resource management system is a database of the

employee’s information, talents, employee schedule and the
projects under taken. The HRMS database provides the information
by the external corporate databases and directly. The attendance
summary display provides the management of
the employee scheduled plans and the other scheduled activities.

The function known as the Human resource search and scheduling

is made for the human resources with desired skills. The interface
is developed for the handling of the external database and the
HRMS database. The view of the external database and the HRMS
database is made for the common user
interface. The HRMS server and the HRMS database are applied in
the programmed system.

The HR work in an organization is to maintain recruitment of

employee, time management, management of the payroll, and
other employee management process. The manual handling of the
employee recruitment, time scheduling and the salary slip creation
for the thousands of employee organization is difficult task. The
requirement of the automated system makes the job easy for the
HR department in an effective manner.

The current system has some problems like the test conducting
feature is difficult, the attendance system need to update every
time by login. The attendance and the appropriate salary with
leave can be made easily by applying the proposed system.
OBJECTIVE OF THE PROJECT:

Manually it is very difficult to manage the human resource. With the

help of computer it becomes easy and faster to manage the system.
In this project it is the facilities to storing and managing all the
information about the employee working in that company and the
projects handle by the company.

Functions of human resource management system:

The function of Human Resources departments is generally administrative and not

common to all organizations. Organizations may have formalized selection,
evaluation, and payroll processes. Efficient and effective management of
“Human Capital” has progressed to an increasingly imperative and complex
process. The HR function consists of tracking existing employee data which
traditionally includes personal histories, skills, capabilities, accomplishments
and salary. To reduce the manual workload of these administrative activities,
organizations began to electronically automate many of these processes by
introducing specialized Human Resource Management Systems. HR
executives rely on internal or external IT professionals to develop and
maintain an integrated HRMS. Before the client-server architecture evolved in
the late 1980s, many HR automation processes were relegated to mainframe
computers that could handle large amounts of data transactions. In
consequence of the low capital investment necessary to buy or program
proprietary software, these internally-developed HRMS were unlimited to
organizations that possessed a large amount of capital. The advent of client-
server, Application Service Provider, and Software as a Service or SaaS
Human Resource Management Systems enabled increasingly higher
administrative control of such systems.

Currently Human Resource Management Systems encompass:

1. Payroll Module
2. Recruiting Module
3. Training Module
4. Performance Record Module
5. Employee Self-Service Module
6. Grievances Module
Scope of project:-
• Digitalization: HRMS can automate and centralize core HR
processes, such as payroll, time and attendance, and benefits
administration.
•Talent management: HRMS can help with recruiting,
onboarding, performance management, goal planning,
and succession planning.
•Testing and quality assurance: Before going live, HRMS projects
undergo rigorous testing to identify and fix any issues. This
includes functional testing, user acceptance testing, and
performance testing.
•Employee information management: HRMS can help with
employee information management, leave policy and
transaction management, and salary changes and increment
calculations.

•Performance appraisal and promotions: HRMS can help with

performance appraisal and promotions.

Purpose:-
The purpose of a Human Resource Management System (HRMS) project is to
automate and centralize core HR processes, which can help improve the
efficiency and productivity of a business:

Automation

HRMS software automates manual and repetitive tasks, such as employee

data storage, time and attendance, and payroll.

Centralization

HRMS software centralizes information about a company’s employees,

including their data, benefits, and attendance.

Talent management

HRMS software can help with recruiting, onboarding, performance

management, and more.
Achievement:-
There are many achievements are here in
HRMS(human resources management
system).
• Data quality
HRMS projects can ensure that data quality is up to agreed standards.

• System performance
HRMS projects can ensure that the system goes live on schedule,
and that system errors and bugs are fixed within the agreed
timeframe.
• Usage rates
HRMS projects can ensure that usage rates for key features meet target
levels.

• Centralized data
HRMS projects can centralize all employee data in a secure and
accessible platform, eliminating the need for manual data entry. @
• Reduced errors
HRMS projects can reduce administrative errors by centralizing
employee data.
Chapter 2:- Survey of technologies
*Front end technology:-
The front end of an application or website is
what users see, and includes the visual
elements and interactive features that allow
users to interact with the app. Front end
developers use languages like HTML, CSS, and
JavaScript to design user interfaces and
ensure compatibility across devices.

*Back end technology:-

The back end of an application or website is
the data and infrastructure that make the app
work, including the server, application, and
database. Back end
developers use languages like Python, Java,
Ruby, and PHP to handle the server side and
create the
backbone for the front end to run smoothly.
*Database management system:-A Human
Resources Management System (HRMS) can be a
collection of systems or an application that’s affiliated
with a database management system (DBMS). HRMS
software is often referred to as human capital
management (HCM) software.

Centralized data storage: An HRMS can store

employee data in a centralized location.
Faster data access: A DBMS can help answer queries
quickly, which can lead to faster and more accurate
data access.
Streamlined data processing: A DBMS can streamline
the entire data processing and maintenance process.
And etc.
Chapter 3:- SYSTEM REQUIREMENTS
SPECIFICATION

REQUIREMENTS SPECIFICATION:
Requirements Specification involves the basic
requirements that the system to be developed should
posses. These can be broadly classified into two types.
1. Performance Requirements.
2. Functional Requirements.
Understanding the requirements specification is critical
for the projects success otherwise the system does
not get developed according to the user’s wishes.
Performance Requirements:
1. The system should be built in a way such that it is
independent of the type of database used.
2. Response should be fast.
3. High throughput.
4. Security should be high such that no Intruder can
tamper with data.
Functional Requirement:
Here HR Manager will do the following
jobs: They can see employee and project
Information.
They can update employee and project information.
They can remove any particular information.They can
add new information about the project and the
employee.
FEASIBILITY STUDY
Feasibility is the determination of whether or not a project is worth
doing. The process followed in making this determination is called
feasibility study. This type of study determines if a project can and
should be taken. Once it has been determined that a project is
feasible, the analyst can go ahead and prepare the project
specifications which finalizes project requirements.
Generally feasibility studies are undertaken within tight time
constraints and normally culminate in a written and oral feasibility
report. The contents and recommendations of such a study will be
used as a sound basis for deciding whether to proceed, postpone,
or cancel the project. Since feasibility study may lead to the
commitment of large resources, it becomes necessary that it
should be conducted competently and that no fundamental errors
of
judgment are made.

The system is technically feasible because this is platform

independent. I can run on Linux as well as on windows platform. I
used PHP 4.1 as a scripting
language which is very fast scripting language. I have used HTML,
JavaScript for user interface design which are very common. End
users are also familiar with the GUI standards of HTML page. So
they are more comfortable using it.

The system is developed using MySQL as database server which

can be either on Linux or windows platform, MySQL is very fast
and ACID compliant database. MySQL is very much compatible
with PHP. MYSQL is free. The implementation cost of other
database servers is also high.
Economical Feasibility:

The system is financially feasible. Development was completed

at very low cost. Client can easily afford the cost of development
and implementation. Running cost of project is very low. Also
the softwares used to develop this project are free of cost and
cross platform. This Is major benefit of this
project. That’s why I used these tool/languages to develop this
software. Client need not to purchase any license to run this
project. He has to register only a domain to host this site with a
web hosting company. That is very cheap nowadays.

Operational Feasibility:

Operationally this site is very much feasible. User can run this site
in internet explorer or Netscape navigator by typing the URL of this
site. This site can run on Apache or IIS web server with PHP
support. This site can easily run on LINUX or windows platform
without making any change in coding. This site is platform
independent.
Chapter 4:- SYSTEM DESIGN
• USE CASE DIAGRAM
A Use case is a description of set of sequence of
actions.
Graphically it is rendered as an ellipse with solid line
including only its name. Use case diagrams model
behavior within a system and helps the
developers understand of what the user require.
The stick man represents what is called an actor.
Use case diagram can be useful for getting an
overall view of the system and clarifying who can
do and more importantly what they cannot do.
Use case diagram
consists of use cases and actors and shows the
interaction between the use case and actors,
 The purpose is to show the interactions
between the use case and actor.
 To represent the system requirements
from user's perspective.
 An actor could be the end-user of the
system or an external system.
ER DIAGRAM:-
ER model stands for an Entity-Relationship model. It is a high-level data
model. This model is used to define the data elements and relationship
for a specified system.
It develops a conceptual design for the database. It also develops
a very simple and easy to design view of data.
In ER modeling, the database structure is portrayed as a
diagram called an entity- relationship diagram.
The below ER Diagram for ATM Simulator shows different entities and
their Relationship with each other.
• CONTEXT DIAGRAM
A context diagram is data flow diagram by which the whole system is
modeled by one process. It shows all the external entities that interact with
the system and the data flows between these external entities and the
system. Actually the system shown by the context diagram does not describe
the system in detail. For more details it is necessary to identify the major
system process and draw a data flow diagram made up of these processes
and the data flow between them. Such a diagram is called a Top Level DFD.
We can go on expanding each process of the top-level DFD into a more
detailed DFD.
• DATA FLOW DIAGRAM (DFD).
DFD or Data Flow Diagram is the cornerstone for structured systems analysis and
design. A Data Flow Diagram (DFD) is a graphical representation that depicts
information flow and the transforms that are applied as data move form input to
output. It is the starting point of the design phase the functionally decomposes the
requirements specifications down to the lowest level. The Data Flow Diagram can be
used to represent a system or software at any level of abstraction. Data Flow
Diagram can even be partitioned into levels that represent increasing information
flow and functional detail. Therefore, the Data Flow Diagram provides a mechanism
for functional modeling as well as information flow modeling.
ACTIVITY DIAGRAM:-
Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.

The control flow is drawn from one operation to another. This flow can be sequential,
branched, or concurrent. Activity diagrams deal with all type of flow control by using
different elements such as fork, join, etc. Activity diagram is sometimes considered as
the flowchart. Although the diagrams. look like a flowchart, they are not.
Chapter 5: IMPLEMENTATION AND TESTING
5.1.Implementation and Approaches

Planning is an essential aspect of any successful project. However, it can be difficult to turn goals and
strategy into tangible action, and, therefore, projects of all sizes and across all industries have a high
tendency to fail. Implementation planning can reduce this chance of failure by helping turn strategy into
action.
An implementation plan for a project refers to a detailed description of actions that demonstrate
how to implement an activity within the project in the context of achieving project objectives,
addressing requirements, and meeting expectation.

5.2 Implementation Environment

The application is a single server multiple client application. Multiple users can log in to use the system.
Multi-user vs. Single-user
Single user applications are the application where it is useful to only one user at a time. While in Multi
user given application is used by many users at the same time and thus web application is used by many
users at the same time. Our system is a multi-user system as we have more than one user who can use
the system at the same time.
GUI vs. Non-GUI
Non-GUI application uses command Prompt for input and output while GUI application has graphics
form to interface and other graphics property for various I/O operations and are easy to use Our System
is a GUI based and thus easy and effective to use therefore user can easily give input and take Input.

5.3 Coding Standards

Coding techniques incorporate many facts about software development. Although they usually have no
impact on the functionality of the application; they contribute to an improved comprehension of source
code. All forms of source code are considered here, including programming, scripting markup.
The coding techniques defined are not proposed to form an inflexible set of coding standards. Rather,
they are meant to serve as a guide for developing a coding standard for a specific software project. We
used sonatina standards for creating our whole project.

Purpose of Coding Standards and Best Practices

To develop reliable and maintainable applications, you must follow coding standards and best practices.
The naming conventions, coding standards and best practices described in this document are compiled
from our own experience and by referring to various guidelines. There are several standards that exist in
the programming industry. None of them are wrong or bad and you may follow any of them. What is
more important is, selecting one standard approach and ensuring that everyone is following

5.4 Coding Scenario used python Programming and the Graph query language of API Call..
Graph is used instead REST. We modularization every functionality so we can reuse those whenever we
need.[7]We have also used Google Drive API, to access the Attachment of employees. We have stored
those documents and only the admin can access it.[4]We have used react.js for front end.We have utilized
components very well and also used redux.Reduces a very powerful tool of react.[2]A major challenge
for us was to achieve success when 500 employees use HRMS at a time.We have-used Nginx for load
balancing. Our HRMS product is also secure in terms of HTTP support.
5.5 Coding Details and Efficiency

Testing Objectives
● Testing is a process of executing a program with the intention of finding an error.
● A good test case is one that has a high probability of finding an as-yet undiscovered error.
● A successful test is one that uncovers an as-yet undiscovered error.

Unit Testing
Unit testing is a software development process in which the smallest testable part of an application,
called units, are individually scrutinized for proper operation. Unit testing is often automated but it can
also be done manually. This testing mode is a component of Extreme Programming (XP), a pragmatic
method of software development that takes a meticulous approach to building a product by means of
continual testing and revision.[3]

Unit testing
involves only those characteristics that are vital to the performance of the unit under test.
This encourages developers to modify the source code without immediate concerns about how such
changes might affect the functioning of the units or the program as a whole. Once all of the units in a
program have been found to be working in the most efficient and error free manner possible, larger
components of the program can be evaluated by means of integration testing.[3]

System testing
Now, it’s time for whole System testing. We have found some cosmetic bugs and minor bugs .We have
fixed it and tested it again. We worked on each error and exception that we got while testing and most of
them are resolved or handled programmaticall

Test Cases
To minimize the number of errors in software, a rich variety of test design methods have evolved for
software. These methods provide the developer with a systematic approach to testing. More importantly,
methods provide a mechanism that can help to ensure the completeness of the test and provide the
highest likelihood for uncovering errors in software.[
CONCLUSION

 While developing the system a conscious effort has been

made to create and develop a software package,
making use of available tools, techniques and
resources that would generate a proper system for
HR MANAGEMENT SYSEM.
  While making the system, an eye has been kept on
making it as user-friendly. As such one may hope
that the system will be
acceptable to any user and will adequately meet
his/her needs.

Reference

1. 1SOFTWARE ENGINEERING (Techmax

publications)Author name: M.A. Ansari, Anil
Prajapati.
2. SOFTWARE ENGINEERING Author name: Roger S.
Pressman
3. UNIFIED MODELING LANGUAGE
Author name: Gradi Booch, Ivar Jacobson
4. Tutorials – Java point.
www.javatpoint.com.
https://www.javatpoint.com