Employee work management system project using codeIgniter

1. A Project on
To Design & Develop Employee Management System
Using CodeIgniter Php Framework
A project paper is submitted to the Department of Information & Communication
Engineering for the partial fulfillment of the Degree of M.Sc. Final Examination 2015.
.
Supervised By
Dr. Md. Zahidul Islam
Professor,
Dept. of Information and Communication
Engineering
Islamic University,
Kushtia, Bangladesh.
Submitted By
Md. Shahinul Islam Shojan
Roll No: 141813
Reg No: 1343
Session: 2014-2015
Dept. of Information and Communication
Engineering
Islamic University.
Kushtia, Bangladesh .
----------------------------------------------------------------------------------------------------------
DEPARTMENT OF INFORMATION AND COMMUNICATION ENGINEERING
ISLAMIC UNIVERSITY, KUSHTIA, BANGLADESH.

2. 2
DDeeddiiccaatteedd ttoo…………
My Parents
&
Teachers

3. 3
ACKNOWLRDGEMENT
At first I would like to thank the Almighty Allah for completing such a project.
Regarding the outcome of my project, I would like to express my deepest sense of gratitude
and respective to my supervisor Dr.Md. Zahidul Islam, Professor, Department of
Information and Communication Engineering, Islamic University, Kushtia for his suggestion
to select the topic and constant guidance, great supervision , advice and other fruitful helps
throughout the duration of my project. His dedication, collaboration and interaction were key
factors in the success of my project. Without his active support and great supervision, I would
not be able to complete the project.
I also wish to acknowledge my parents and others teachers and some of my closed friends
and big brothers for their continued supports throughout the project.
Finally, I would to think Almighty Allah the deepest of my heart for making me able to finish
this project work.
Md. Shahinul Islam Shojan
March, 2018.
Islamic University, Kushtia.

4. 4
CERTIFICATE
It is my pleaser to certify that Md. Shahinul Islam Shojan, Examination Roll No.
141813 has performed a project entitled “To Design And Develop Employee
Management System Using CodeIgniter Php framwork” under my supervision in
the academic year 2014-2015 for the fulfillment of partial requirement of M. Sc. degree. So
far as I concern this is an original project work that he carried out for masters year in the
Department of Information & Communication Engineering, Islamic University, Kushtia,
Bangladesh.
I strongly declare that this project has not been copied from any of project or submitted to
elsewhere prior submission to this department.
I wish him to every success in life.
…………………..
Dr.Md. Zahidul Islam
Professor,
Dept. of Information and Communication Engineering
Islamic University, Kushtia, Bangladesh.

5. 5
ABSTRACT
Employees are the backbone of any company therefore their management plays a major
role in deciding the success of an organization [1]. Employees Management Software makes
it easy for the employer to keep track of all records. This software allows the administrator to
edit employees, add new employees, transfer/promote/terminate employees. Each employee
in the database is associated with a position can be added and edited when need arises.
Employees can be transferred between positions easily without having to retype back their
information in the database. You can check to see if there are duplicate positions/employees
in the database.
A flexible and easy to use Employee Management software solution for small and
medium sized companies provides modules for personnel information management thereby
organization and companies are able to manage the crucial organization asset – people [2].
The combination of these modules into one application assures the perfect platform for re-
engineering and aligning Human Resource processes along with the organizational goals.
This system brings about an easy way of maintaining the details of employees working in
any organization.
It is simple to understand and can be used by anyone who is not even familiar with
simple employees system. It is user friendly and just asks the user to follow step by step
operations by giving easy to follow options.
The goal of this project is to design and develop an employee management system to fill
existing gaps in the electronic management of employees.In this project works, a web site has
been designed for “To Design & Develop Employee Management System Using
CodeIgniter”. It is designed by using HTML and CSS. Server side Web scripting language
PHP has been used for developing the dynamic web pages. In future the implementation of
this project will be for all company of Bangladesh and will be converted to WEB site rapidly
growing browsing media.

6. 6
CONTENTS
Page No:
Chapter 1: Overview of the Project works
1.1 Problem statement 09
1.2 Objective of this project 09
1.3 Motivation of the works 10
1.4 Methodology of the project work 11
1.5 Requirements and constraints 12
1.5.1 Functional Requirements: 12
1.5.2 Non-Functional Requirements: 13
1.6 Strong & Weak Point of the Project 13
1.7 Summary 13
Chapter 2: Basic Concept of CodeIgniter
2.1 What is CodeIgniter 14
2.2 What is View 14
2.3 What is Controller 15
2.4 What is Model 15
2.5 What is Routing ? 15
Chapter 3: Designing And Developing Tools
3.1 Html 16
3.2 Css 16
3.3 Php 16
3.4 Mysql 17
3.5 Javascript 17
Chapter 4: System Analysis
4.1 Introduction 18
4.2 Software Development Methodology Of Choice 18

7. 7
4.3 System Design 19
4.3.1 Use case analysis 19
4.3.2 Use case diagrams 20
4.3.2 Class Diagram: 20
Chapter 5: Design
5.1 Introduction 21
5.2 Explanation Of The Proposed System 21
5.3 Entity Relationship Diagram (Erd) 22
5.4 Storyboard 23
5.4.1 Sequence Diagrams 23
Chapter 6: Result
6.1 Login page of the website. 24
6.2 Employee registration form. 25
6.3 Holiday registration form. 25
6.4 Work schedule registration form. 26
6.5 Salary registration page. 26
6.6 Employee attendance registration form 27
6.7 Employee can view holiday,work shcdule 27
attendance in the calander.
Chapter 7: System Testing And Verification
7.1 Introduction 28
7.2 Scope 28
7.3 Testing Goals 28
7.4 Confirmation Testing 28

8. 8
Chapter 8: Conclusion
8.1 Introduction 29
8.2 Results 29
8.3 Problems Faced 29
REFERENCE 30

9. 9
Chapter One
OVERVIEW OF THE PROJECT WORKS
1.1 Problem statement
Manual handling of employee information poses a number of challenges. This is evident
in procedures such as leave management where an employee is required to fill in a form
which may take several weeks or months to be approved. The use of paper work in handling
some of these processes could lead to human error, papers may end up in the wrong hands
and not forgetting the fact that this is time consuming. A number of current systems lack
employee self-service meaning employees are not able to access and manage their personal
information directly without having to go through their HR departments or their managers.
Another challenge is that multi-national companies will have all the employee information
stored at the headquarters of the company making it difficult to access the employee
information from remote places when needed at short notice.
The aforementioned problems can be tackled by designing and implementing a web based
HR management system. This system will maintain employee information in a database by
fully privacy and authority access. The project is aimed at setting up employee information
system about the status of the employee, the educational background and the work experience
in order to help monitor the performance and achievements of the employee through a
password protected system.
1.2 Objective of this project:
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. This project
simplifies the task of maintaining records because of its user friendly nature.

10. 10
The objective of this project is to provide a comprehensive approach towards the
management of employee information. This will be done by designing and implementing an
HR management system that will bring up a major paradigm shift in the way that employee
information is handled.
The objectives of this system include:
 Design of a web based HR management system to fulfill requirements such as project
management, leave management, report generation to assist in performance appraisal,
ESS and employee trainings.
 Well-designed database to store employee information.
 A user friendly front-end for the user to interact with the system.
1.3 Motivation of the works:
A computer based inventory and query system can decrease the management problem
and the processing time of the system with the increase of security as well as efficiency. A
relatively low cost computer will be sufficient for this work and will overcome the limitations
of the existing manual system. The authority can easily implement the computerized system.
The main objective of this software is to computerized the Bank Management System. This
project work is a step for the development of a completely computerized system as like as
expert and it is a step for computerized the total bank system and bringing more new
millennium people to the computer.
An expert system is sets of programs that manipulate encoded knowledge to solve
problems in a specialized domain that normally require human expertise. An expert system‟s
knowledge is obtained from expert sources and coded in a form suitable for the obtained from
specialist or other sources of expertise, such as texts, journal articles and database. These
types of knowledge usually require muss training and experience in some specialized field.
Once a sufficient body of expert system knowledge has been acquired, it must be encoded in
some form, loaded into a knowledge base, then tested and refine continually throughout the
like of the system.

11. 11
1.4 Methodology of the project work:
The methodology for developing the software was into different components. Which
are given bellow?
► Data study and analysis
► Building Entity-Relationship Diagram
► Data normalization and Table Design
► Database Creation
► Software and Interface Design
► Coding, Error Handling and Debugging
► Testing the Software
► Documentation and User‟s Manual Creation
1.5 requirements and constraints
1.5.1 Functional Requirements:
Authentication
 Login- The user can login to the HRMS system with his/her username and password.

 Logout- The user can log out from the HRMS system.

Login failure- If the user does not exist in the database or the user has not yet
being authorized by the HRMS admin.

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.

Process Data

 Display- User with defined roles can display the content of the database. Being
more specific, employee can only view his/her personal information. HOD can
not only see his/her personal information but also employee‟s information who
are under his/her department or school. Admin and HR can display their personal
information and all employees‟ information.

 Edit- A user with employee role can edit his/her specific personal information. Dean
or


12. 12
HOD can only edit employees‟ personal information that is under his/her coverage
except user role type. Admin can edit all information related to all employees‟
including their user role type.

 Search- User with Dean/HOD role can search the content of database for the employees‟
who are under his/her coverage. HR and admin roles can search all the employees‟
information in the database. Search feature works on specific keywords showing
employee‟s characteristics, peculiarities, skills, features, and etc. For example, HR wants
to find employees‟ who are well trained in “Php Programming Language”. He/she will
write the specific keyword in the search bar and press the available search button.
Afterwards, he/she will find a list of all the employees‟ who know “Java Programming”.

Update authentication- This feature can be used only by admin role type. Admin
can update the role type of a specific user. For example, an employee got promotion
and his role type will be changed from employee role id to HOD or Dean role.
Admin will be able to update this authentication mechanism.
1.5.2 Non-Functional Requirements:
Performance requirements
There is no restriction on the number of the users to be added to the database.
Hardware requirements
EMS should be able to work on a computer with the following minimum
hardware specifications:
OS: Windows XP/Vista/7/8 and Linux
CPU: Pentium III (700MHz) and above
Memory: 128 MB and above
Capacity: 4GB of hard drive
Others: Network interface card, mouse, keyboard, and monitor.
Software requirements

13. 13
Since EMS application is a web-based application, internet connection must be
established.
The EMS software personal database model will support MySQL environment as DBMS.
1.6 Strong & Weak Point of the Project
Strong point:
 Employee can update of his information from his place.
 Time Saving.
 Less complexity.
 Money Saving.
Weak point:
 Employee need to use the coputer.
 Employee need to use internet.
 Employee need to use website handle.
 Website security problem.
1.7 Summary
This chapter began by giving a brief overview of the entire project, the background of the
project and the scope. The problem definition and solution highlights the current problems
faced with the use of the systems that are in place and outlines briefly the solution system to
be developed. The next chapter will focus on the literature review. This is literature that
relates to the project and similar systems.

14. 14
Chapter Two
BASIC CONCEPT OF CODEIGNITER
2.1 What is CodeIgniter ?
CodeIgniter is an open-source software rapid development web framework,
for use in building dynamic web sites with PHP. CodeIgniter is loosely based on the
popularmodel–view–controller (MVC) development pattern. While controller classes
are a necessary part of development under CodeIgniter, models and views are
optional. Codeigniter can be also modified to use Hierarchical Model View Controller
(HMVC) which allows developers to maintain modular grouping of Controller,
Models and View arranged in a sub-directory format.
2.2 What is View ?
A view is simply a web page, or a page fragment, like a header, footer, sidebar,
etc. In fact, views can flexibly be embedded within other views (within other views, etc., etc.)
if you need this type of hierarchy.Views are never called directly, they must be loaded by a
controller. Remember that in an MVC framework, the Controller acts as the traffic cop, so it
is responsible for fetching a particular view. If you have not read the Controllers page you
should do so before continuing.
2.3 What is Controller ?
A controller is a simple class file. As the name suggests, it controls the whole
application by URI.
Simple example controller name „Test‟

15. 15
<?php
class Test extends CI_Controller {
public function index() {
echo "This is default function.";
}
public function hello() {
echo "This is hello function.";
}
}
?>
2.4 What is Model ?
Models classes are designed to work with information in the database. As an example,
if you are using CodeIgniter to manage users in your application then you must have model
class, which contains functions to insert, delete, update and retrieve your users‟ data.
2.5 What is Routing ?
CodeIgniter has user-friendly URI routing system, so that you can easily re-route URL.
Typically, there is a one-to-one relationship between a URL string and its corresponding
controller class/method. The segments in a URI normally follow this pattern −
your-domain.com/class/method/id/
 The first segment represents the controller class that should be invoked.
 The second segment represents the class function, or method, that should be called.
 The third, and any additional segments, represent the ID and any variables that will
be passed to the controller.

16. 16
Chapter Three
DESIGNING AND DEVELOPING TOOLS
3.1 Html
HyperText Markup Language, commonly referred to as HTML, is the standard markup
language used to create web pages.[1] It is written in the form of HTML elements consisting
of tags enclosed in angle brackets (like <html>). HTML tags most commonly come in pairs
like <h1> and </h1>, although some represent empty elements and so are unpaired, for
example <img>. The first tag in such a pair is the start tag, and the second is the end tag
(they are also called opening tags and closing tags).
Web browsers can read HTML files and render them into visible or audible web pages.
Browsers do not display the HTML tags and scripts, but use them to interpret the content of
the page. HTML elements form the building blocks of all websites. HTML allows images
and objects to be embedded and can be used to create interactive forms.
3.2 Css
Cascading Style Sheets (CSS) is a style sheet language used for describing the look and
formatting of a document written in amarkup language. While most often used to change the
style of web pages and user interfaces written in HTML and XHTML, the language can be
applied to any kind of XML document, including plain XML, SVG and XUL. Along with
HTML and JavaScript, CSS is a cornerstone technology used by most websites to create
visually engaging webpages, user interfaces for web applications, and user interfaces for
many mobile applications. CSS is designed primarily to enable the separation of document
content from document presentation, including elements such as the layout, colors, and fonts.
3.3 Php
PHP is a server-side scripting language designed for web development but also used as a
general-purpose programming language. As of January 2013, PHP was installed on more

17. 17
than 240 million websites (39% of those sampled) and 2.1 million web servers.[3]Originally
created by Rasmus Lerdorf in 1994,[4] the reference implementation of PHP (powered by
the Zend Engine) is now produced by The PHP Group.[5] While PHP originally stood for
Personal Home Page,[4] it now stands for PHP: Hypertext Preprocessor, which is a recursive
backronym.
3.4 MySQL
MySQL ( "My S-Q-L",[6] officially, but also called / "My Sequel") is (as of July 2013)
the world's second most[a] widely used relational database management system
(RDBMS)[9] and most widely used open-source RDBMS.[10] It is named after co-founder
Michael Widenius's daughter, My.[11] The SQL acronym stands for Structured Query
Language.
The MySQL development project has made its source code available under the terms of the
GNU General Public License, as well as under a variety of proprietary agreements. MySQL
was owned and sponsored by a single for-profit firm, the Swedishcompany MySQL AB,
now owned by Oracle Corporation.
The Main Features of MySQL
3.5 JavaScript
JavaScript, also known as ECMAScript (the untrademarked name used for the standard),
is a dynamic programming language. It is most commonly used as part of web browsers,
whose implementations allow client-side scripts tointeract with the user, control the browser,
communicate asynchronously, and alter the document content that is displayed. It is also
used in server-side network programming with runtime environments such as Node.js, game
development and the creation of desktop and mobile applications.
JavaScript is classified as a prototype-based scripting language with dynamic typing and
first-class functions. This mix of features makes it a multi-paradigm language, supporting
object-oriented, imperative, and functional programming styles.

18. 18
Chapter Four
SYSTEM ANALYSIS
4.1 Introduction
This chapter gives a detailed outline of the software development methodology used in
this project following up the various existing software development methodology discussed
in chapter two. The strength and weaknesses of the chosen methodology have been outlined.
Further, the functional and non-functional requirements of the system are explained in detail
and the use cases which are a list of steps, typically defining interactions between a role and
a system, to achieve a goal. Class diagrams have been given to show detailed data modeling
of the system which will be translated into code.
4.2 Software Development Methodology Of Choice
Having briefly discussed a few software development methodologies in
chapter two, the incremental method was favored for the following reasons:
• It allows for development of high-risk or major functions first
• Each release delivers an operational product
• Customer can respond to each build
• Uses “divide and conquer” breakdown of tasks
• Lowers initial delivery cost
• Initial product delivery is faster
• Customers get important functionality early
• Risk of changing requirements is reduced

19. 19
4.3 SYSTEM DESIGN
4.3.1 Use case analysis
A use case defines a goal-oriented set of interactions between external users and the
system under consideration or development. Thus a Use Case Scenario is a description that
illustrates, step by step, how a user is intending to use a system, essentially capturing the
system behavior from the user's point of view.
In order to create relevant use cases for the system, the following actors for the system have
been identified:
1. Employee (could be lecturers, accountants, technicians)
2. Admin
4.3.2 Use case diagrams
Fig: Use case diagram

20. 20
4.3.2 Class Diagram:
Fig: Class Diagram

21. 21
Chapter Five
DESIGN
5.1 Introduction
This chapter builds on the work done in the Analysis Chapter and gives documentation
for the Design of the Employee Management System. The EMS is modeled in terms of
objects and classes and their interactions with each other. Explanation of the proposed
system is done as well structure of the Entity Relationship Diagram (ERD). Design of the
User Interface is also discussed.
5.2 Explanation Of The Proposed System
The proposed system is designed to eliminate all the drawbacks of the existing
employee management software. The system shall be responsible for maintaining
information about employees, thus their personal profile. The system shall incorporate
leave management all the way from application to acceptance/rejection of leave requests
as well as all employee projects with close monitoring of the projects from creation to
completion and trainings to assist in monitoring active and inactive employees.

22. 22
5.3 Entity Relationship Diagram (Erd)
tt
5.4 Storyboard
5.4.1 Sequence Diagrams
Sequence diagrams help in the identification of a detailed level of the operations
required to implement the functionality depicted by a use case model.
tbl_employee tbl_holiday
the_salary the_shift the_attendance

23. 23
Scenario 1: Admin add new employee
1. The user logs in by providing correct username and password.
2. If username and password are not found on the database access into the system is
denied.
3. If the credentials are identical to the ones found on the database, access is granted.
4. User enters the details of the new employee.
5. The user input is written to the database.
Figure 4.5 Add new employee sequence diagram

24. 24
Chapter Six
RESULT
Design input form for insert different information into database:
The Client database is kept in record. We created data table called User Account. To insert
data in the table we designed an input form called User Account.
The new Account Holder form contains some command button, some tables, some texts and
a data control as follows.
Functions of the objects:
Save : Click on Save button to insert a record into the saving table we have to insert
data in the respective text fields.
Delete : To delete a record form the selects the target record and click on Delete
Button.
Edit : Click on Edit button to edit a record then save the record to save the data
into database.
6.1 Login page of the website.

25. 25
6.2 Employee registration form.
6.3 Holiday registration form.

26. 26
6.4 Work schedule registration form.
6.5 Salary registration page.

27. 27
6.6 Employee attendance registration form .
6.7 Employee can view holiday,work shcdule ,attendance in the calander.

28. 28
Chapter Seven
SYSTEM TESTING AND VERIFICATION
7.1 Introduction
Testing is very important and critical to the success of any project that aims at
delivering working software. There are many types of testing that a system may be
subjected to, however only the ones in the testing objectives will be carried out for this
system.
7.2 Scope
The overall purpose of testing is to ensure the Employee Management System meets
all of its functional and business requirements. The purpose of this chapter is to describe
the overall test plan and strategy for testing the system.
7.3 Testing Goals
The goals in testing this system include validating the quality, usability, reliability and
performance of the application. Testing will be performed from a black-box approach. Tests
will be designed around requirements and functionality.
7.4 Confirmation Testing
Confirmation testing or re-testing: When a test fails because of the defect then that
defect is reported and a new version of the software is expected that has had the defect fixed.
In this case we need to execute the test again to confirm that whether the defect got actually
fixed or not. This is known as confirmation testing and also known as re-testing. It is
important to ensure that the test is executed in exactly the same way it was the first time using
the same inputs, data and environments. [18]

29. 29
Chapter Eight
CONCLUSION
8.1 Introduction
The aim of this chapter is to draw conclusions of the work done or achieved and to
give an assessment of the completed system, discuss the Problems faced, limitations of the
system and give future recommendations on how the system can be improved.
8.2 Results
The software product produced was fairly good, it achieved most of the user
requirements, the user interface is good and is very easy to navigate, and even novice users
can find their way around the web application easily. The client side validation is excellent.
The lack of integration with a payroll system is the major drawback and the system was also
unable to generate structured reports i.e. reports based on specific information the Human
Resource is interested in.
8.3 Problems Faced
The biggest challenge faced was getting hold of employee information for Human
Resource. The project was initially aimed at implementing an HR system for UNZA but that
proved to be a challenge because employee information is very critical. This led to the
implementation of a generic system thereby drawing a few assumptions were possible
meaning that requirements kept on changing as different views were put into consideration as
compared to software which has a specific customer

30. 30
REFERENCES:
[1] OrangeHRM Open Source, Retrieved: November 4, 2013. From:
http://www.orangehrm.com/open-source-product-features-pim.shtml
[2] A.S.SyedNavaz, A.S.SyedFiaz, C.Prabhadevi, V.Sangeetha, S.Gopalakrishnan,
“Human Resource Management System”, IOSR Journal of Computer Engineering (IOSR-
JCE), Volume 8, Issue 4 (Jan. – Feb. 2013) Page 62-71.
[3] Julie Bulmash, “Human Resource Management and Technology”, Chapter 3
[4] TECH HRM (Human Resource Management System), Retrieved: November 4, 2013.
From: http://www.techjetsolutions.com/brochure/TECHHRM.pdf
[5] Renae Broderick, John W. Boudreau, “Human resource management, information
technology, and the competitive edge”, Academy of Management Executive, 1992 Vol. 6
No. 2
[6] Centralized Employee Information, Retrieved: July 8th
, 2014.
From: https://www.zoho.com/people/employee-management-
system.html
[7] HR and Employee Mnagement Software, Retrieved: July 8th
, 2014.
From: http://www.getapp.com/hr-employee-management-software
[8] Ian Sommerville, “Software Engineering”, 9th
Edition, Addison-Wesley, 2011.
[9] What is Enterprise Resource Planning (ERP)? Webopedia. Retrieved: January 17,
2014,
from: http://www.webopedia.com
[10] Avison, D. and Fitzgerald, G. (2003).Information systems Development
Methodologies, Techniques and Tools.3rd Edition. McGraw-Hill Education Limited
Bershire
[11] Zhiming, L, July 2002 ,Object-Oriented Software Development with UML Retrieved:

31. 31
July 16th
2010. From:
http://www.iist.unu.edu/www/docs/techreports/reports/report259
.pdf
[12] Juan Manuel Munoz Palacio, Information systems development methodologies for
Data-driven Decision Support Systems, 2010,
[13] Deitel, PJ & Deitel, HM, 2008, Internet & World Wide Web How To
Program, Dorling Kindersley, India
[14] Web design best practices checklist 2009. Retrieved: October 17, 2009,
from: http://terrymorris.net/bestpractices/
[16] Connolly, T, Begg, C, 2005, Database Systems A Practical Approach to
Design Implementation and Management, 4th Edition, Dorling Kindersley, India
[17] Avison, D. and Fitzgerald, G, 2003. Information systems Development
Methodologies, Techniques and Tools, 3rd Edition, McGraw-Hill Education Limited,
Berkshire
[18] ASP.NET, 2010. Retrieved: July 9th
2010,
from: http://www.startvbdotnet.com/aspsite/asp/
[19] Introducing JSON, Retrieved: June 21, 2014, from: http://www.json.org
[20] Employee Self Service, Retrieved: January 15, 2014, from:
http://en.wikipedia.org/wiki/Employee_self-service_%28web-based_application%29