FYP 2 REPORT AMIRUL ARIFF

WEB BASED METHOD FOR
STAFF MANAGEMENT
SYSTEM
AMIRUL ARIFF BIN ABDUL MALEK
SESSION 2015/2016
FACULTY OF INFORMATION SCIENCE & TECHNOLOGY
MULTIMEDIA UNIVERSITY
FEBRUARY 2016

WEB BASED METHOD FOR
STAFF MANAGEMENT
SYSTEM
BY
AMIRUL ARIFF BIN ABDUL MALEK
SESSION 2015/2016
THE PROJECT REPORT IS PREPARED FOR
IN PARTIAL FULFILLMENT
FOR
BACHELOR OF INFORMATION TECHNOLOGY
B.I.T. (HONS) SECURITY TECHNOLOGY
FEBRUARY 2016

II
© 2015 Universiti Telekom Sdn. Bhd. ALL RIGHTS RESERVED
Copyright of this report belongs to Universiti Telekom Sdn. Bhd as qualified by
Regulation 7.2 (c) of the Multimedia University Intellectual Property and
Commercialization policy. No part of this publication may be reproduced, stored in
or introduced into a retrieval system, or transmitted in any form or by any means
(electronic, mechanical, photocopying, recording, or otherwise), or for any purpose,
without the express written permission of Universiti Telekom Sdn. Bhd. Due
acknowledgement shall always be made of the use of any material contained in, or
derived from, this report.

III
DECLARATION
I hereby declare that the work have been done by myself and no portion of the work
contained in this thesis has been submitted in support of any application for any
other degree or qualification of this or any other university or institute of learning.
____________________
Amirul Ariff Bin Abdul Malek
Faculty of Information Science & Technology
Multimedia University
Date:

IV
ACKNOWLEDGEMENT
First of all, I would like to thank Allah SWT, The Almighty, a place where I
pray and surrender, who has given me strength and ability to complete the project on
time.
Next big thanks go to Mr. Mohammed Rajihuzzaman as my Supervisor for
this project and the opportunity given to me for doing my final year project. I also
would like to thank for his kind attention, great advices, brilliant ideas, and his
guidance for helping me to complete this project from the beginning until the end of
this project.
Not forgetting to Multimedia University especially Faculty of Information
Science and Technology for giving me chance to study here.
Last but not least, my deepest gratitude and thankfulness are dedicated to my
family for their prayers, support, and their encouragement to construct the project
successfully. Not forgetting to all of my friends and all the people who have helped,
support and contributed to complete this project. Without helps of the particular that
mentioned above, I would face many difficulties while doing this project.

V
ABSTRACT
Staff Management System is a distributed application, developed to maintain
the details of staffs working in any organization. It maintains the information about
the personal details of their staffs, also the details about the payroll system which
enable to generate the payslip. The application is actually a suite of applications
developed using website.
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 him few options. It is fast and can perform many
operations of a company.
The software is very user friendly. The package contains different modules
like Employee details. This version of the software has multi-user approach. For
further enhancement or development of the package, user’s feedback will be
considered.

VI
TABLE OF CONTENTS
DECLARATION .....................................................................................................III
ACKNOWLEDGEMENT ...................................................................................... IV
ABSTRACT ...............................................................................................................V
TABLE OF CONTENTS ........................................................................................ VI
LIST OF TABLES................................................................................................ VIII
LIST OF FIGURES................................................................................................. IX
LIST OF ABBREVIATIONS/ SYMBOLS ........................................................... XI
LIST OF APPENDICES ...................................................................................... XIII
CHAPTER 1 INTRODUCTION...............................................................................1
1.1 Overview ................................................Error! Bookmark not defined.
1.2 Problem Statement....................................................................................1
1.3 Project Objectives.....................................................................................2
1.4 Project Scope ............................................................................................2
1.5 Constraints................................................................................................3
CHAPTER 2 LITERATURE REVIEW ..................................................................4
2.1 Background...............................................................................................4
2.2 Definition..................................................................................................4
2.3 Review of Similar Page ............................................................................5
2.4 Differences of SMS compared to other system......................................10
CHAPTER 3 METHODOLOGIES........................................................................11
3.1 Project Management...............................................................................11
3.2 Software Engineering Life Cycle ...........................................................11
3.3 Development Environment.....................................................................16
CHAPTER 4 IMPLEMENTATION PLAN AND DESIGN ................................21
4.1 Background.............................................................................................21
4.2 Flowchart................................................................................................21
4.3 Unified Modeling Language (UML) ......................................................22

VII
4.4 Data Flow Diagram (DFD).....................................................................23
4.5 Business Rule .........................................................................................23
4.6 Database Design (ERD) .........................................................................24
4.7 Entity Structure.......................................................................................24
4.8 Gantt Chart .............................................................................................27
CHAPTER 5 TESTING...........................................................................................31
5.1 Overview ................................................................................................31
5.2 Testing and Evaluation...........................................................................31
5.3 Type of Errors.........................................................................................34
5.4 Method Used for Testing........................................................................34
5.5 Benefit of Testing...................................................................................36
CHAPTER 6 SOLUTION .......................................................................................37
6.1 User Interface .........................................................................................37
CHAPTER 7 CONCLUSION .................................................................................52
7.1 Conclusion Review.................................................................................52
7.2 Chapter Summary...................................................................................52
7.3 Conclusion..............................................................................................54
REFERENCES .........................................................................................................55
APPENDICES...........................................................................................................56

VIII
LIST OF TABLES
Table 4.1: Entity Structure......................................................................................24
Table 4.2: Gantt Chart First Phase.........................................................................27
Table 4.3: Gantt Chart Final Phase........................................................................29
Table 5.1: Testing and Evaluation ..........................................................................34

IX
LIST OF FIGURES
Figure 2.1: Snapshot of OrangeHRM interface.......................................................5
Figure 2.2: Snapshot of NEMR interface .................................................................7
Figure 2.3: Snapshot of EMS interface.....................................................................8
Figure 2.4: Snapshot of ShiftPlanning interface......................................................9
Figure 3.1: SDLC Model..........................................................................................11
Figure 3.2 Percentage of people who know about staff management system.....13
Figure 3.3 Percentage of people using online management system .....................13
Figure 3.4 Percentage of method use to communicate among workers ..............14
Figure 3.5 Percentage of staff willing to try online staff management system ...15
Figure 4.1: Flowchart Process...............................................................................221
Figure 4.2: Use Case Diagram.................................................................................23
Figure 4.3: Context Diagram...................................................................................23
Figure 4.4: Entity Relationship Diagram...............................................................23
Figure 5.1: Logic Error Found................................................................................34
Figure 6.1: Home Page .............................................................................................37
Figure 6.2: Gallery....................................................................................................38
Figure 6.3: Contact Us .............................................................................................38
Figure 6.4: About Us ................................................................................................39
Figure 6.5: Office Room and Machine ...................................................................40
Figure 6.6: Site Map.................................................................................................40
Figure 6.7: Admin Login..........................................................................................41
Figure 6.8: Admin - View User Comment..............................................................42
Figure 6.9: Admin - Monitor Staff Information....................................................42
Figure 6.10: Admin - View Staff Salary .................................................................43
Figure 6.11: Admin - View Malaysian Salary Rate...............................................43
Figure 6.12: Admin - Calculate Staff Salary..........................................................44
Figure 6.13: Admin - Monitor Staff Check-in .......................................................45
Figure 6.14: Admin - Monitor Staff Check-out .....................................................45
Figure 6.15: Admin - Leave Application Approval...............................................46
Figure 6.16: Staff - Login.........................................................................................47
Figure 6.17: Staff - Register.....................................................................................48

X
Figure 6.18: Staff - View Profile..............................................................................48
Figure 6.19: Staff - Check-in and Check-out .........................................................49
Figure 6.20: Staff - Malaysian Salary Rate............................................................49
Figure 6.21: Staff - Payslip ......................................................................................50
Figure 6.22: Staff - Leave Application....................................................................51
Figure 6.23: Staff - Leave Approval Result............................................................51

XI
LIST OF ABBREVIATIONS/ SYMBOLS
SMS Staff Management System
FIST Faculty of Information Science and Technology
FYP Final Year Project
MMU Multimedia University
Admin Administrator
PHP Hypertext Preprocessor
SQL Structured Query Language
TCO Total Cost of Ownership
SaaS Software as a Service
NEMR National Employee Management Resource
EMS Employee Management Service
SDLC System Development life Cycle
OS Operating System
ASP Active Server Page
HTML Hypertext Markup Language
XHTML Extensible Hypertext Markup Language
XML Extensible Markup Language
SVG Scalable Vector Graphic
XUL XML User Interface Language
CSS Cascading Style Sheet
WWW World Wide Web
W3C World Wide Web Consortium
DBMS Database Management System
RDBMS Relational Database Management System
GB Gigabyte
TB Terabyte
UML Unified Modeling Language
DFD Data Flow Diagram
RM Ringgit Malaysia
SOCSO Social Security Organization
EPF Employees' Provident Fund

XIII
LIST OF APPENDICES
Appendix A: Meeting Log........................................................................................56
Appendix B: Questionnaire ....................................................................................57

1
CHAPTER 1
INTRODUCTION
1.1 Overview
Staffs are the important role of any company therefore their management
plays a serious role in deciding the success of an organization. Staff Management
System (SMS) makes it easy for the staff to keep track of all records. This system
allows the administrator to edit staffs, add new staffs as well as evaluate staff’s
performance. Staffs can be managed efficiently without having to key-in back their
information in the database.
Staff management system refers to systems and processes at the intersection
between staff, management and information technology. An organization or
company with a very large number of staffs manages a greater volume of data. This
activity can be difficult without a more sophisticated tool to store and recover data.
1.2 Problem Statement
Staff administration has dependably been an issue, following along on the
working hours are still performed by utilizing the traditional strategy for punch cards
in some real associations. Manual handling of staff information poses a number of
challenges. This is obvious in methods, for example, leave administration where
staffs is obliged to fill in a structure which may take a few weeks or months to be
endorsed.
The utilization of paper work in taking care of some of these procedures
could prompt human lapse, papers may wind up in the wrong hands and not
overlooking the way that this is tedious. Various current frameworks need staff self-
administration importance staffs are not ready to get to and deal with their own data
straightforwardly without needing to experience their HR offices or their directors.

2
Another test is that multi-national organizations will have all the
representative data put away at the base camp of the organization making it hard to
get to the worker data from remote spots when required at short notice. Indeed, even
those which have moved up to a superior framework to record staffs working hours
etc, its application is still constrained. A staff booking framework should have the
capacity to calendar staff and administration faculty from a concentration area to
guarantee ideal staff plan. It also should cater in accounting the working hours of a
particular staff individually without any ambiguities.
1.3 Project Objectives
 To calculate staff salary and improved staff management system overcoming
the drawbacks fulfilled Malaysian working environment.
 To provide a monitoring system by staff check-in and check-out and
objective method to evaluate staffs.
 To provide a leave application system for tracking and managing staff
absence.
1.4 Project Scope
This proposed web based staff management system is able to calculate the
working hours and overtime hours of a staff. It also, keep track on their medical
leaves and annual leaves. Moreover, distribute work task and keep track on its
progress among all staff. This system can perform as a dynamic planner for the staff,
able to set reminder and take note on meetings and other agenda. It is to make staff
more alert to situation happen in office. Staff Management System can be used by
different walk of people. It includes the:
 Staff
 Admin
1.4.1 User
There will be two participants in the system, administrator and staff. The
administrator controls all the features in the system like assigning the encrypted

3
password to each staff, calculate the working hours of a staff, calculate the overtime
hours of a staff, keep track on their medical leaves and annual leaves, distribute work
task and keep track on its progress, set reminders, perform as a dynamic planner for
the staff, able to take note on meetings and other agenda.
Move on to the staff page, to access the system, the administrator will give
each user an encrypted password to their email. Only registered staff can get the
password. Moreover, after the registered staff got their password, they can login, get
an access to the system. However, staff can comment or give feedback about admin.
It make job become efficient.
1.5 Constraints
The main limitation in building the system is the software used and limitation
of skills. Only limited number of software will be used to create the system, such as
PHP as the main scripting language, MySQL as the database management system,
and JavaScript to validate the user and also be used as the user-side scripting
language. There are some programming language like Java, and C++ to make
complex algorithm. Because of limitation of skills, some programming languages
above are not used.

4
CHAPTER 2
LITERATURE REVIEW
2.1 Background
This chapter summarizes the assessment of the literature related to the Staff
Management System. It inspects theories, concepts, approaches, methods and
techniques related to the project. Similar existing technologies relating to the
development the Staff Management System are discussed.
2.2 Definition
2.2.1 Staff
Staffs are person who works in the service of another person under an express
or implied contract of hire, in which the manager has the right to control the details
of work performance (Black's Law Dictionary). Staffs are hired for a specific job or
to provide labour and who works in the service of someone else (the employer).
Normally, anybody who carries out services for an organization is a staff if the
organization can supervise what will be done and how it will be done.
2.2.2 Administrator
An administrator is a person who controls any utilization of something.
Admin is also a man who deals with the PC frameworks in an association. The duties
of a system administrator and network administrator frequently overlap. However,
the system administrator is more refer to the computer hardware and less on the
network, even though in many cases, system and network administrator are in the
same group, especially in little companies. A system administrator is involved with
operating system, hardware installations, and configurations and may be connected
with application upgrades and installations. System administrators also carry out
systems programmer activities.

5
2.3 Review of Similar Page
2.3.1 OrangeHRM
OrangeHRM is a powerhouse human resources tool that any small or midsize
business can benefit from using. With OrangeHRM, user can download and install
the system on hardware, or can purchase a hosted solving problem. To know prices
for that solution, user has to contact OrangeHRM from their request a quote page.
OrangeHRM's features include fully modular, add-ons for example, benefits, staff
self-service, training, budget, job, salary history, purchase, all standard HR functions
like staffs, leave, benefits, performance, and more.
The installation is very easy to understand. With a self extracting Windows
installer or full source installations for Linux, Mac, and Windows, user can get
OrangeHRM up and running on closely every platform. If users do not have the
hardware or the skills to set up Orange onsite, user can request a quote for a hosted
reference of OrangeHRM. User can also purchase support plans and customizations.
To view or learn how to use this website, please visit
http://enterprise.demo.orangehrmlive.com/admin/viewSystemUsers
Figure 2.1: Snapshot of OrangeHRM interface

6
2.3.1.1 OrangeHRM Strength
 Total cost of ownership (TCO) extremely low.
 Add-on, full customizations, and suit training workshops mean that
organizations can modify the software at any levels.
2.3.1.2 OrangeHRM Weakness
 Open-Source software, anyhow of application, suffer from a PR problem,
with companies frequently choose for commercial paid-for software that
delivers similar abilities.
 Although both the open-source platform and the software as a service
platform have to report modules, features like payroll, human capital analysis,
and the additional reporting and analysis capabilities needed for functions
like workforce planning are decidedly absent.
2.3.2 National Employee Management Resources
National Employee Management Resources function as full service shared
HR Department. This means NEMR control the non-income generating HR works
that are so required for every business to perform. NEMR team of integrity
professionals manage HR needs, provide benefits and benefits administration,
generate salary, maintain follow employee records, address safety issues, provide
risk management including employees compensation insurance and even handle staff
needs.
All of this supply a peace of mind gives user to focus on their
business development; sales, service and customer care which equal increased
income for any business.
http://www.simplifyinghr.com/#sthash.JMcLobGt.dpuf

7
Figure 2.2: Snapshot of NEMR interface
2.3.2.1 NEMR Strength
 Generate payroll
 Maintain compliant employee records
 Address safety issues
 Provide risk management including workers compensation insurance
 Handle what staff needs
2.3.2.2 NEMR Weakness
 High maintenance
 Need many workers to handle this system
2.3.3 Employee Management Service
Employee Management Services gives user freedom. EMS give user time to
focus on building business and making more value for the customers. EMS watch out
of the rest. By joining Employee Management Services to the team, user can
eliminate the difficulties and reduce the employment risks to any business.
http://www.emshro.com/home/

8
Figure 2.3: Snapshot of EMS interface
2.3.3.1 EMS Strength
 Managing and guiding the 24/7 business operations and worksite staffs in the
creation and delivery of any products and services.
 Providing office with the tools and safe place of work.
 Staff and boss relationship become better.
 Full service salary and required tax processing for the business.
2.3.3.2 EMS Weakness
 Only focusing in United States of America although have worldwide license.
 The cost of this system is a bit expensive.
2.3.4 ShiftPlanning
ShiftPlanning offers small to big business employee scheduling software that
works well for human resource staff, workers, owners and managers. There are many
features included that help scheduling easy, such as the setup application and the
ability to export and import data. Mobile applications let user to correct scheduling
issues faster or immediately. ShiftPlanning also provides good scheduling abilities. It
also includes a strongly reporting system that includes the ability to create custom
reports.

9
The staffs will get benefit from the scheduling software because it gives them
the ability to swap shifts and request time off online. They can also view their
schedules on their mobile device or any computer with an internet connection.
https://www.shiftplanning.com/
Figure 2.4: Snapshot of ShiftPlanning interface
2.3.4.1 ShiftPlanning Strength
 The system can easily access and manage schedules from any mobile or
computer device with internet connection.
2.3.4.2 ShiftPlanning Weakness
 Starting setup can be waste of time because of the search of employee
profiles.

10
2.4 Differences of SMS compared to other system
Since Staff Management System (SMS) is a new system it is different from
other staff system above. Other staff system like OrangeHRM, NEMR, EMS, and
ShiftPlanning only admin can manage about staffs information or status but staffs
cannot comment or condemn about the system. In Staff Management System (SMS),
staff can comment about admin or everything about the system. So, when admin read
the comment, admin can take action immediately. At the same time the system will
improve. It becomes two way communications. The system becomes better time to
time.
Among online staff system above, only admin and staff can use this system
except for EMS website. The system just belongs to insider which is staff and admin
in the company. Other people from outside company which is interested with the
company cannot view the information about company such as mission, vision, what
features that company provide how to contact the company and many more. Only
EMS website provide this features to the outsiders like "About Us", "EMS
Advantage", "Service and Resource", and "Connect With Us". It become user
friendly, moreover, it become attraction to outsiders to join or apply involve in the
company. It is same goes to Staff Management System, but in "Connect With Us"
feature, it not only state company address and contact number, it also state map of
company which is link to the Google Map. So, outsiders from inside or even outside
country which is not familiar with where the company place can come easily to the
company. It make Staff Management System globally attractive or popular website
among others.

11
CHAPTER 3
METHODOLOGIES
3.1 Project Management
To develop web based system there are some point that must be considered
such as system development approach, software that are going to be used, and the
system design. The software, system design, and the system development approach
will be explained in next subchapter.
3.2 Software Engineering Life Cycle
3.2.1 System Development Tools
System Development Life Cycle or (SDLC) are the most common
methodology being used to develop, maintain, and replace information system.
SDLC is a series of steps completed over a period of time by analysts in a system
development. SDLC is used to prepare, develop, and maintain the information during
the progress in making the project.
Figure 3.1: SDLC Model

12
3.2.1.1 Planning
Planning activity is the first phase in SDLC, as the first step, choosing the
title for the project and meet the supervisor is the most important part. Discuss with
the supervisor to define the objectives of the proposed system and establishes the
goals for the system development project. In this step, several tasks like finding some
relevant title in any website, journal, and reference book and do literature review to
get all information related to this project, makes this phase clear to do and give some
imagination about how the project would be, and what are the tools used in order to
complete this project.
In this phase, besides doing literature review part, the planning system is also
done during the introduction part. It gives a brief explanation about what the project
would be done to complete the objectives and what the next step that should be done
with the project to solve the problem.
3.2.1.2 Analysis
The second phase is the analysis phase; the major goal of system analysis is
to determine whether information is needed to support the system. In order to get the
information, interviewing and sending questionnaire among staff in different work
place are done. Results are used to analyze project goals to meet the system
requirements.
Survey was conducted to 30 staff through a questionnaire. It took five weeks
to complete. The type of question and how many percentages of the surveys are
explained one by one.

13
Figure 3.2 Percentage of people who know about staff management system
Figure 3.2 above shows the percentage of know about online staff
management system. This type of question gives information about how many
people knowing about online staff management system existence. About 83% of the
staffs know about this system while 17% says are not familiar with that system.
Figure 3.3 Percentage of people using online management system
Yes
17%
No
83%
People who know about online staff
management system
No
90%
Yes
10%
Using online staffmanagement system

14
Figure 3.3 above shows the percentage of staff using online staff management
system. This question explains the percentage of staff using online staff management
system in their company. About 90% of the staff say that they are using the online
staff management system in their company while 10% not using online staff
management system.
Figure 3.4 Percentage of method use to communicate among workers
Figure 3.4 above shows the percentage of method use to communicate among
workers or register form. This question explains the method used by the staff to
communicate among them and to register form. About 73% of the staffs say that they
fill up the form manually and submit to the responsive person while 20% using
online key in and other 7% are using email.
Onlinekey-in
20%
Usinge-mail
7%
Fill up manually
73%
Method use to fill up formor communicate
among workers

15
Figure 3.5 Percentage of staff willing to try online staff management system
Figure 3.5 above shows the percentage of willing to try online staff
management system. This question explains willingness of the staff to try automated
staff management system. About 96% of the staff says that they will try the system,
while other 4% are do not want to try the system.
3.2.1.3 Design
During the third phase which is design phase, design can be categorized in
two ways which are logical design and physical design. The logical design provides
the users view of the system, where physical design specifies the actual way to the
system that will be implemented. The logical design produced during the analysis is
turned into a physical design. The important goal of the logical design phase is to
synergize the knowledge of application and implementation it to produce a logical
model of the system to begin creating a system solution, while in physical design the
system will be implemented with programming or coding to support the result of the
logical design.
Yes
97%
No
3%
Staff willing to try online staff mangement
system

16
3.2.1.4 Implementation
The fourth phase is implementation phase. In this phase, the objectives and
goals of the system is fulfilled by executing the result of the design phase and then
programmed into a working system. Implementation of the system includes the
coding, testing, installation, and the interface of the system.
The project implementation of the system is not going to be built in phase
one. This phase one is only describes the system implementation plan on how to
design a system. The project implementation of the system will be held during the
final phase.
3.2.1.5 Maintenance
The last phase of SDLC is maintenance phase. Maintenance includes all the
activity after the installation of software that is performed to keep the system
operational. When a new technology is discovered, new changes will be
implemented, which is require system updates. Maintenance is also important part of
SDLC for changing and improving of the system to satisfy user requirement.
3.3 Development Environment
3.3.1 SelectedOperating System
To run a program successfully, we need to know what the entire software
requirements are to be run and which are the software that not compatible with the
Operating System (OS). This system is using Windows 7 Professional Edition. All
software like C#, ASP.NET, HTML, CSS, PHP, JavaScript, and MySQL are being
used in the system and will be discuss on next part.
3.3.2 SelectedProgramming Software Package
The Staff Management System is a web based system; therefore a web based
programming language will be used to build the website. In this project there are

17
some programming languages to be used which are C#, ASP.NET, HTML, CSS,
JavaScript, and PHP.
3.3.2.1 HTML
HTML which stands for Hypertext Markup Language is used to create
documents on the World Wide Web. Document structure and hypertext specification
language specified by the World Wide Web Consortium (W3C).
One of benefits using HTML is designed to specify logical structure of
information intended for presentation as Web pages text marked up with tags
defining document's logical units, like title, headings, paragraphs, and lists. HTML
also allows images and objects to be embedded and can be used to create interactive
forms.
3.3.2.2 CSS
CSS (Cascading Style Sheet) is one of web design programming languages
that control the display format of a web page that is written using a markup language.
Usually CSS is design for a HTML and XHTML pages, but now the CSS can be
applied to all XML document, including SVG and XUL.
CSS main purpose is to distinguish the content of the document and display
of the documents, with the creation or re-programming the web, making a web
design will be more easily performed. Features that include in web design are color,
size, and formatting.
3.3.2.3 JavaScript
JavaScript is a scripting language that is added to standard HTML to create
interactive documents. JavaScript is chosen to be the client-side scripting language
collaborating with PHP as the server-side scripting language. JavaScript is not the
same with

18
Java, but JavaScript borrows a lot of syntax from Java and C.
JavaScript could also create offline interactive pages, built-in feature in
modern web browsers, and it needs no created software required. Some features that
JavaScript can do are:
 Add scrolling or changing messages to the browser
 Validate the contents of a form and make calculations
 Display message to the user, either as part of a web page or in alert boxes
(pop-up message)
 Animate images or create images that change when you move the mouse over
them (rollover image)
 Can detect the browser in use and display different content for different
browsers
3.3.2.4 PHP
PHP (recursive acronym for PHP: Hypertext Preprocessor) is an "HTML-
embedded scripting language" primarily used for dynamic Web applications. The
first part of this definition means that PHP code can be interspersed with HTML
(nusphere.com). PHP is the main code to be used in creating the system. PHP is
chosen because of several advantages:
 PHP is open source and easily accessible because it is available for free
 PHP is easy to understand, learn, and use, especially for user with basic in
programming because there are many tutorial can be find on the net.
 PHP runs on all major operating systems.
 PHP has built-in support for several relational databases such as MySQL
3.3.2.5 C#
C# is a multi-paradigm programming language encompassing strong typing,
imperative, declarative, functional, generic, object-oriented (class-based), and
component-oriented programming disciplines.

19
3.3.2.6 ASP.NET
ASP.NET (Active Server Pages.NET) is a proprietary scripting language or
application framework developed by Microsoft used to create enterprise wide web
applications which can be accessible globally. The HTML produced by the
ASP.NET page is sent back to the browser. The application source code you write is
not sent and is not easily stolen. ASP.NET makes for easy utilization. There is no
need to register components because the arrangement information is already built
inside.
ASP.NET makes development of any web based application or system easier
and faster as it allows developers to drag and drop components and specify their
functions while code is automatically generated, as a result of this ease complex
applications can be developed in a short period of time even by programmers who
are not too familiar with the language. Despite ASP.NET being robust it has also
proven to be more expensive to implement and the fact that it’s not platform
independent limits the number of places in which it can be used.
3.3.3 Database Software
3.3.3.1 MySQL
MySQL is a relational database management system (RDBMS) that runs as a
server providing multi-user access to a number of databases (Wikipedia.org, 2010).
MySQL can be used for a variety of applications, but is most commonly found on
Web servers. The system will use MySQL as the database management system that
combine with PHP. In other words MySQL have enough feature to support the
system. There are some benefits using MySQL such as:
 MySQL is easy to use because only using basic knowledge of SQL. With
only a few easy SQL statements, user can interact and build with MySQL.
 MySQL is secure because using encrypted password and includes solid data
security layers that keep safe sensitive data from attackers.
 MySQL runs on many Operating System such as Microsoft Windows, Open
Solaris, Mac OS and many more.

20
 MySQL cost is less and almost can get it free of charge and available to
download free from MySQL Web site.

21
CHAPTER 4
IMPLEMENTATION PLAN AND DESIGN
4.1 Background
This chapter will discuss about the Flowchart, Unified Modeling Language
(UML) which contain Use Case Diagram and Data Flow Diagram (DFD) and the
software used in creating the system.
4.2 Flowchart
The design evolved lot during the initial part of the project. Finally, the
following design flow was generated.
Figure 4.1: Flowchart Process

22
4.3 Unified Modeling Language (UML)
UML is a standard notation for modeling object-oriented systems. UML is
used to specify, visualize, modify, construct and document the artifacts of an object-
oriented software intensive system under development (Wikipedia.org, 2010). The
purpose of designing the UML of the system is to get a clear picture on how the
system works.
4.3.1 Use Case Diagram
Use Case Diagram will show what processes can be accessed by the actors of
the system. As seen in the figure 4.2 below, the diagram contains two actors; Staff,
and Administrator who will have different accessible process. Staff will have limited
access to the system as the user while Administrator will control everything and have
unlimited access into the system.
Login
Registration
calculate salary
view payslip
view check-in, check-out
Admin delete staff Staff
check-in, check-out
apply leave
Figure 4.2: Use Case Diagram

23
4.4 Data Flow Diagram (DFD)
4.4.1 Context Diagram
Figure 4.3: Context Diagram
4.5 Business Rule
 Administrator must have a unique username and secret password to
authenticate.
 Each staff must have a unique username and secret password to authenticate.
 Staff can update and edit their profile.
 Administrator can delete staff profile.
 Only administrator can calculate the staff salary.
 Only admin can view users comment.

24
4.6 Database Design(ERD)
Figure 4.4: Entity Relationship Daigram
4.7 Entity Structure
Table
name
Entity
name
Data type Size Null? Key Description
Staff staff_id
firstname
lastname
address
city
zip
country
email
integer
varchar
varchar
varchar
varchar
integer
varchar
varchar
11
30
30
30
30
11
30
30
No
No
No
No
No
No
No
No
PK Staff ID
First name
Last name
Address
City
Zip code
Country
Email

25
contact
username
password
basic
allowance
otrate
othour
incometax
socso
epf
varchar
varchar
varchar
float
float
float
float
float
float
float
20
30
30
10
10
10
10
10
10
10
No
No
No
No
No
No
No
No
No
No
Contact
Username
Password
Basic salary
Allowance
Overtime rate
Overtime hour
Income tax
Socso deduct
EPF deduct
Admin admin_id
username
password
position
integer
varchar
varchar
varchar
11
30
30
30
No
No
No
No
PK
FK
FK
Admin ID
Username
Password
Post position
Comment comment_id
email
name
content
integer
varchar
varchar
text
11
30
30
100
No
No
No
No
PK Comment ID
Email address
Name
Content
Checkin checkin_id
username
date1
Time1
integer
varchar
date
time
11
30
No
No
No
No
PK
FK
Checkin ID
Username
Checkin date
Checkin time
Checkout checkout_id
username
firstname
lastname
date2
time2
integer
varchar
varchar
varchar
date
time
11
30
30
30
No
No
No
No
No
No
PK
FK
FK
FK
Checkout ID
Username
First name
Last name
Checkout date
Checkout time
Leave leave_id
startdate
enddate
typeleave
username
integer
date
date
varchar
varchar
11
20
30
No
No
No
No
No
PK
FK
Leave ID
Start date
End date
Leave type
Username

26
firstname
lastname
reason
approval
varchar
varchar
varchar
varchar
30
30
100
20
No
No
No
No
FK
FK
First name
Last name
Reason
Approval
Table 4.1: Entity Structure

27
4.8 Gantt Chart
4.8.1 Phase One
Task durations 2/7 12/7
22
/7
27/
7
1/
8
3/
8
13/
8
23/
8
2/
9
7/
9
14
/9
17/
9
2
0
/
9
Reviewing
chapter 10 days
Introduction 10 days
Background 5 days
Literature review
definition 5 days
Review on similar
page 2 days
Project
management 10 days
System
engineering life
cycle 10 days
Development
environment 10 days
Flowchart and
UML 5 days
Data flow
diagram 7 days
Gantt chart 3 days
conclusion 3 days
FYP due date and
presentation
Table 4.2: Gantt chart Phase One
Table 4.2 shows the Gantt chart for phase one. As can be seen that first task
was reviewing chapter by chapter. After that, editing some part in introduction and
background, and continuing by system implementation. As long as implement the
system takes, continuing do the report by edit some methodology and

28
implementation plan on mid of August. It took two weeks before begin testing and
evaluation. While system implementation is still continuing, conclusion part is done.
Do some system checking and reviews the entire chapters are done. This project
should be submitted on 17th September, before doing the final task, which was a
presentation.

29
4.8.2 Final Phase
Task durations
24
//11
4/
11
14/
11
19/
11
24/
11
26/
11
5/
12
15/
12
25/
12
30/
12
14
/9
17
/9
20/
9
Design home
page 10 days
Design contact
us andcomment
page 10 days
Design staff
login and
register page 5 days
Design admin
login and view
staff
information 5 days
Design admin
calculate staff
salary 2 days
Design staff
check-in and
check-out 10 days
Finalize website
system 10 days
Add testing and
debugging
chapter inthe
report 10 days
Add solution
chapter whichis
user interface 5 days
Edit all the
diagrams inthe
report 7 days
Finalize report 3 days
Check and
compare report
and system 3 days
FYP due date
and present
Table 4.3: Gantt Chart Final Phase

30
Table 4.2 shows the Gantt chart for final phase. As can be seen that first task
was design home page in the website. After that, designs contact us and comment
page. As long as implement the page takes, continuing design staff and admin login
page including register page and view staff information page on mid of November. It
took three weeks before finalize the website system. While system implementation in
the report is still continuing, conclusion part is done. Do some system checking and
reviews the entire system and report are done. This project should be submitted on
4th February, before doing the final task, which was a presentation.

31
CHAPTER 5
TESTING
5.1 Overview
In order to know how well the system performs, several tests are needed to
examine the performance of the system. A list of scenarios was tested into the
system. Each of the scenarios has expected output and hoped that the actual output
will be producing same result as the expected one. The table below shows each of the
scenarios, inputs, expected outputs, and the actual output of the scenario.
5.2 Testing and Evaluation
Scenario Input Expected Output Output/Result
Administrator login Administrator
username and
password
Successful login Successful
Administrator view
user comment
User comment Successful viewed
user comment
Successful
Administrator view
staff information
Staff information
like name, address,
country, email,
contact number,
and username
Successful viewed
staff information
Successful
Administrator
delete staff
Delete selected
staff
Selected staff is
deleted
Successful
Administrator view
salary rate
Salary rate Successful viewed
salary rate
Successful
Administrator View staff salary Successful viewed Successful

32
viewed staff salary information like
basic, allowances,
epf, socso,
insurance, income
tax, overtime, and
net salary
staff salary
Administrator
calculate staff
salary
Calculate staff
salary information
like basic,
allowances, epf,
socso, insurance,
income tax,
overtime, and net
salary
Staff salary
calculated
Successful
Administrator view
staff check-in
Check-in date and
time
Successful viewed
check-in date, time
and remark
Successful
Administrator view
staff check-out
Check-out date and
time
Successful viewed
check-out date and
time
Successful
Staff login Staff username and
password
Successful login Successful
Staff view his/her
information
View staff
information like
name, address,
country, email,
contact number,
and username
Successful viewed
staff information
Successful
Staff edit his/her
information
Edit staff
information like
name, address,
country, email,
contact number,
name, address,
country, email,
contact number,
and username are
save in database
Successful

33
and username
Staff check-in Check-in date, time
and remark
Check-in date,
time and remark
are save in
database
Successful
Staff check-out Check-out date and
time
Check-out date and
time are save in
database
Successful
Staff view salary
rate
Salary rate Successful viewed
salary rate
Successful
Staff print his/her
payslip
Staff payslip Successful print
his/her payslip
Successful
User comment
about website
User comment,
email and name
Comment are save
in database
Successful
Staff apply leave Leave type, start
date and end date
Leave are save in
database
Successful
Admin approved /
reject leave
Admin approval
and remark
Approval are save
in database
Successful
Staff view leave
approval
Admin approval Successful view
admin approval
leave
Successful
Table 5.1 Testing and Evaluation

34
5.3 Type of Errors
5.3.1 Logic Error
This system is not perfect system. There is some logic error found in making
this project. The output below shows the logic error has been made. As seen on
Figure 5.1. The SOCSO deduction up to three decimal places. It must be in two
decimal places because it is in currency calculation. This should not happen in order
to implement number format. This type of error can be solved using JavaScript
algorithm.
Figure 5.1: Logic Error Found
5.4 Method Used for Testing
For this section, sample code and explanation are given to give the
information what are the codes used for.
5.4.1 Verification and Validation
There are a lot of JavaScript functions in this system to validate and verify
the user. Below is one of examples to validate data using JavaScript including email
and phone number.

35
//email validation
function validateForm1()
{
var r=document.forms["log"]["email"].value;
var g=document.forms["log"]["password"].value;
var atpos=r.indexOf("@");
var dotpos=r.lastIndexOf(".");
if (atpos<1 || dotpos<atpos+2|| dotpos+2>=r.length)
{
alert("Not a valid e-mail address");
return false;
}
//phone number validation
if( e.which!=8 && e.which!=0 && (e.which<48 || e.which>57))
{
//display error message
$("#errmsg").html("Number Only").show().fadeOut("slow");
return false;
}
});
$("#cnumber").keypress(function (a)
{
//if the letter is not digit then display error and don't type anything
if( a.which!=8 && a.which!=0 && (a.which<48 || a.which>57))
{
//display error message
$("#errmsg1").html("Number Only").show().fadeOut("slow");
return false;
}
});
5.4.2 Software Testing Strategy
Testing is the process of exercising a program with the specific intent of
finding errors prior to delivery to the end user. [R.S. Pressman & Associates, Inc
(2005)]. The testing should shows error, requirements conformance, performance,

36
and an indication of quality. In general, testing strategy should cover introduction
and state testing objectives explicitly, an explanation of testing philosophy,
understand the users of the software, and develop a continuous improvement
approach for the testing process. There are four tests to perform testing strategy,
which are unit test, integration test, system test, and validation test. Based on
software testing strategy founded in the internet, this system is done through high
order testing. It includes validation testing, system testing, security testing, and
performance testing.
5.5 Benefit of Testing
Generally software testing is relegated to one phase of the software
development life cycle. [Johnson, K.N. (n.d.)]. There are some advantages by
perform early testing in this system, which are help to determine the feasibility of the
system, identify requirements that might not be testable, fixed some error, add some
security feature to protect the data, and add some functionalities to support the
system.

37
CHAPTER 6
SOLUTION
6.1 User Interface
6.1.1 User Part
Figure 6.1: Home Page
Home page is the introductory of a website. It is the first page visit by users.
It like a start up or default page for users. In Staff Management System home page,
users can pick whatever function they want to go. It is like a navigator to users.
Furthermore, users can view calendar and clock for their time management.

38
Figure 6.2: Gallery
When user choose gallery, they can view the scenery and room in the office
or company. It is for users' information. Users will know more about the company.
Moreover users can view larger if they click any one of the pictures in the gallery.
Figure 6.3: Contact Us
Contact us page is the information for users to communicate directly with the
company. There are telephone number, fax number, and mobile number if users want

39
to communicate through phone. The human resource management will entertain
them if they got some problem or give feedback about the system. Furthermore if
users do not have time to do that, they can directly give comment to the box given.
Admin will read it and try to improve the system if have any negative feedback.
Admin also can reply any comment if have to via email.
Figure 6.4: About Us
About us page is just the information about the Staff Management System. It
is the explanation about Staff Management System and the function of it.

40
Figure 6.5: Office Room and Machine
Office room and machine page is for users to know what the machine use in
the office and what are the type of room available in the office.
Figure 6.6: Site Map
Site map page is for users know where are the company located. It will
facilitate users to find out where the company located. At the same time it will attract
interest users to join or be a part of company's family.

41
6.1.2 Admin Part
Figure 6.7: Admin Login
Admin login is a page where admin have to key-in username and password to
continue to admin page. Any users and staffs cannot go in to admin page. Only
admin with the username and password can go in this page. It is for the security
purpose. It will make this website safer to surf.

42
Figure 6.8: Admin - View User Comment
The first thing when admin go in the admin page is admin can view all the
comment and feedback from users about this website. Admin can read it take the
comment seriously to improve Staff Management System. Moreover, admin can
reply the users comment via email. It is two way communications and makes the
system improve from time to time.
Figure 6.9: Admin - Monitor Staff Information

43
In the monitor staff information page, admin view all staffs and their
information which have been registered. Admin can delete the staff that no longer
work at the company.
Figure 6.10: Admin - View Staff Salary
In this page admin can view and monitor all the staffs’ salary information
including their earnings and deduction.
Figure 6.11: Admin - View Malaysia Salary Rate

44
In this page admin can view Malaysian Salary Rate. In this case admin can
refer to this when calculate the staff salary. In this page, it show that the deduction
based on their earnings.
Figure 6.12: Admin - Calculate Staff Salary
In this page, admin can key-in all the staff salary information such as basic
salary, allowances, insurance, socso, income tax, and overtime. After admin click
save, the system will calculate the net salary staff get after the earnings minus
deduction in then database including whatever salary information admin key-in
before this.

45
Figure 6.13: Admin - Monitor Staff Check-in
In this page, admin can view and monitor what time staff check-in and what
are the remark which is what job that staff do in that time. So, admin can monitor and
detect any late comers and lazy staff.
Figure 6.14: Admin - Monitor Staff Check-out
In this page, admin can view and monitor what time staff check-out. So,
admin can monitor and detect any staff that go back early.

46
Figure 6.15: Admin - Leave Application Approval
In this page, admin can view all the information about leave application.
Moreover, admin can choose whether to approve or reject the application that have
been made by staff. Admin also can write remark which is why admin took that
decision.

47
6.1.3 Staff Part
Figure 6.16: Staff - Login
Staff login is a page where staffs have to key-in username and password to
continue to admin page. Any users and admin cannot go into staff page. Only staff
with the username and password can go in this page. It is for the security purpose. It
will make this website safer to surf.

48
Figure 6.17: Staff - Register
In this page, staff can register for a new profile. Username and password that
been register can use it for login into staff profile.
Figure 6.18: Staff - View Profile
In this page, staff can view their profile that has been register. Moreover staff
can edit it if have any changes in their profile.

49
Figure 6.19: Staff - Check-in and Check-out
In this page, staff can check-in when they come or start the work and check-
out after they finished their work and go back home. Date and time for check-in and
check-out will be recorded for admin monitor.
Figure 6.20: Staff - Malaysian Salary Rate
In this page staff can view Malaysian Salary Rate. In this case staff can refer
to this when they check their salary. Is it same with what they get. In this page, it
show that the deduction based on their earnings.

50
Figure 6.21: Staff - Payslip
In this page, staff can print their payslip and they will know how much they
will get on that month. Staff also can know how much their earnings and deduction.

51
Figure 6.22: Staff - Leave Application
In this page, staff can apply for leave. The data of leave application will go to
admin. Admin will decide whether to approve or disapprove the application.
Figure 6.23: Staff - Leave Approval Result
In this page, staff can view their leave application whether it is approved or
rejected by admin. Furthermore, staff can view the admin remark which is why
admin took decision whether to approve or reject the application.

52
CHAPTER 7
CONCLUSION
7.1 Conclusion Review
Nowadays, almost all company in the world use online or internet to achieve
company performance goals like minimizing execution time, minimizing
communication delays, and maximizing resource utilization. A staff management
system is design to achieve the goals. The system will based on add, delete, edit,
register, valuation of staff and calculation method.
7.2 Chapter Summary
This first chapter which is introduction part gives clear explanation to the
readers what Staff Management System is, and what are the objectives to achieve for
both admin and staffs. A future enhancement, constraints, and a scope make readers
clear about this project. This chapter also explain some problems that staffs and
admin faced that can be solve by Staff Management System.
The literature review chapter gives explanation about type of scheduling
method and similar program that have been made by others. This chapter also shows
other system that similar to Staff Management System. The example of other system
is helping Staff Management System to enhance or improve than any previous
system. So it will make this system more quality and functional. Furthermore, it
consists of several studies to analyze the strengths and weaknesses of the current
existing systems to gain a better understanding of the problems faced by the current
staff management systems. Next, the objective and scope of the project are laid out
to identify the ideal key features that the staff management system should provide.
In order to achieve the objectives, methodology chapters which contain
Unified Modelling Language (UML), Data Flow Diagram (DFD), business rules,
and database design was explained. Several designs were drawn to model the

53
functions and database of the system. These phases have helped to plan the initial
requirements and designs for the staff management system. This is to shows how the
system works step by step. Moreover, selecting programming languages like HTML,
CSS, JavaScript, PHP and MySQL are also include in this chapter. All programming
languages are clearly explained with some advantages make readers clears about
programming language used in making this project. It also shows what are the
method uses to make the Staff Management System website run successfully.
Chapter four consists of proposed solution and implementation plan. This
chapter is made to complement previous chapter. Planning, analysis, and design are
more discuss in this chapter. Prototype of the system is also included in this chapter.
Some prototypes are explaining in detail. This is to make sure the readers clearly
about the running process and know how the prototype looks like. A Gantt chart
figure also shows detailed activity what kind of tasks done during the interim phase.
It shows the timeline from the beginning of this task until finish. It is consists two
Gantt chart which is first phase Gantt chart and final phase Gantt chart.
Chapter five consists of testing and evaluating the system. It briefly gives
some explanation about type of error happen on the system, source code of
validation, security, and assignation. Moreover, on the next part, some information
flows are given to know how the system assignation works.
Chapter six consists of solution which is the user interface of Staff
Management System. In information technology, the user interface (UI) is everything
designed into an information device with which a human being may interact
including display screen, keyboard, mouse, light pen, the appearance of a desktop,
illuminated characters, help messages, and how an application program or a Web site
invites interaction and responds to it. In early computers, there was very little user
interface except for a few buttons at an operator's console. The user interface was
largely in the form of punched card input and report output. In Staff Management
System, it shows that the screenshot of Staff Management System website. It shows
the what the users, administrator and staffs do when they are using the website. It is
like a guideline for people to know about the flow of the Staff Management System
website. It will be able to enhance the interaction between staffs, administrator and

54
users when they use the system to facilitate their learning experience.
7.3 Conclusion
This project is following System Development Life Cycle (SDLC). Staff
Management system used to automatically assign staff data. Admin also can monitor
the staff’s data. In order to achieve the goals, certain method is chosen such as PHP,
and the database chosen is MySQL. There are some limitations in this system
improvement and enhancement is needed to make the system better in the future.

55
REFERENCES
Answers.(n.d.). Retrieved from JavaScript: http://www.answers.com/topic/javascript
Employee management Service. (2015). Retrieved from Employee Management Service:
http://www.emshro.com/home/
Englander, I. (2000), The Architecture of computer hardware and systems software, John Wiley, New
York.
Forouzan, Behrouz A. (2007). Data Communication and Networking 4th Addition.
Figeiredo, P., McIllree. J. and Thomas, N. (1996), Introducing information technology, 2nd ed.,
Jacaranda Press, Singapore. Figeiredo, P., McIllree. J. and Thomas, N. (1996), Introducing
information technology,2nd ed., Jacaranda Press, Singapore.
K. Schwalbe, Information Technology Project Management, 3rd ed. Boston: Course Technology,
2004.
National Employee Management Resource. (2015). Retrieved from National Employee Management
Resource: http://www.simplifyinghr.com/
Novell. (2007). Retrieved April 2007, from Benefit of MySQL:
http://www.novell.com/documentation/oes/web_mysql/?page=/documentation/oe
s/web_mysql/data/aj5bj52.html
OrangeHRM. (2015). Retrieved from OrangeHRM:
http://enterprise.demo.orangehrmlive.com/admin/viewSystemUsers
SDLC Model. (2009). Prentice Hall
ShiftPlanning. (2015). Retrieved from ShiftPlanning:
https://www.shiftplanning.com/
U. J. Gelinas, Jr., S. G. Sutton,and J. Fedorowicz, Business Processes and Information Technology.
Cincinnati: South-Western/Thomson Learning, 2004.
Wikipedia. (2010). Retrieved from Unified Modelling Language:
http://en.wikipedia.org/wiki/Unified_Modeling_Language
Wikipedia. (2013). Retrieved from PHP:
https://en.wikipedia.org/wiki/PHP

56
APPENDICES
Appendix A: Meeting Log

57
Appendix B: Questionnaire
Introduction: I am Amirul Ariff Bin Abdul Malek from Faculty of Information Science and
Technology (FIST), a final year student who is doing on the FYP title “Staff Management System”.
We are proposing to develop this system to evaluate the staffs’ job. Furthermore it is to make the
communication between admin and workers easier.
1. Gender
□ MALE
□ FEMALE
2. Races
□ MALAY
□ CHINESE
□ INDIAN
□ OTHERS __________
3. How many years you have been working?
□ 1-5 YEARS
□ 6-10 YEARS
□ 11-15 YEARS
□ MORE THAN 15 YEARS
4. What post you occupied?
□ CEO
□ MANAGER
□ SUPERVISOR
□ GENERAL WORKER
□ OTHERS __________
5. In Which department you work?
□ INFORMATION TECHNOLOGY
□ ACCOUNTING
□ MARKETING
□ OTHERS: ________________
6. Academic qualification?
□ SECONDARY SCHOOL
□ DIPLOMA
□ DEGREE
□ HIGHER
7. Have you hear about online staff management system?
□ YES
□ NO

58
8. If your company use online staff management system?
□ YES
□ NO
9. If there is an online system for you to manage your work activities or handle your workers
stuff, will you have a try on it?
□ YES
□ NO. WHY? _______________
10. How you communicate with your boss/workeror register form?
□ USING E-MAIL
□ FILL UP MANUALLY
□ ONLINE KEY-IN
11. What are the functions you expect fromthis proposed system? Please list out as much as you
can.
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
----------------------------------*Thank you for your patience and participation*------------------------

FYP 2 REPORT AMIRUL ARIFF

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a FYP 2 REPORT AMIRUL ARIFF

Semelhante a FYP 2 REPORT AMIRUL ARIFF (20)

FYP 2 REPORT AMIRUL ARIFF