EMPLOYEE MANAGEMENT SYSTEM

BY
COTTON COLLECTION (PVT) LTD.

MOHAMED HUSSAINUDEEN RITHAF

(BT/HNDCSE/03/14)

A PROJECT PROPOSAL SUBMITTED TO

INTERNATIONAL COLLEGE OF BUSINESS AND TECHNOLOGY
(ICBT)
IN PARTIAL FULFILLMENT OF THE REQUIREMENTS
FOR THE
HND IN COMPUTER STUDIES
August 2019

International College of Business and Technology

(ICBT)

1|Page
International College of Business and Technology
(ICBT)

Statement of originality of submitted work

I...MOHAMED HUSSAINUDEEN RITHAF………….. (Student Name)

Student ID Number …………………...…………BT/HNDCSE/03/14………………………….

Module number…………………………..SED5214……………………………………

Here by confirm that the work presented here in this report, and in all other associated material,
is wholly my own work, and I agree to assessment for plagiarism

Signature……………………………………………

Date…………………………………………………

2|Page
 ABSTRACT
Our aim is to design and create an employee management system for a company of
COTTON COLLECTION (PVT) LTD Employee management is a function within an
organization which focuses mainly on the requirement of, management of a guidelines to the
manpower in a company. It is function of the company or the organization which deals with a
concern that are related to the staffs of the company in terms of compensation, performances,
safety, wellness and benefits.

The main target of this system is to reduce the effort of administrator to keep the daily
performances of administrator to keep the daily performances of company. This software
helps with the process of identifying the employees, recording their attendances hourly and
collective their effective payable hours or days.

This system should maintain the records of each staffs of company and their time spend in
company when they are Production Company selling all kind of cotton wears. Which can be
used for a formal assessment of employees.

Like that this software of Employee management system has a very user friendly interface.
Thus the user will feel very easy to work on it by using this system admin can concern and
manage a Human Resource Department in our company as well as customer also getting
more benefits by it.

3|Page
 EMPLOYEE MANAGEMENT SYSTEM

MOHAMED HUSSAINUDEEN RITHAF

HND in Computing
August2019

I certify that I have read this Project Proposal and that in my opinion it is fully adequate, in scope
and in quality, as a project for the HND in Computing.

Mr. Juwarajan Kalaivarman

(Supervisor/Lecturer)

4|Page
 ACKNOWLEDGMENT
I owe my deep gratitude to my project guide Mr. Juwarajan Kalaivarman lecturer ICBT
Campus,Batticoloa.I who took keen interest on my project work and guided me all along, till the
completion of my project work by providing all the necessary information for developing a good
system. I am extremely thankful to him for providing such a nice support and guidance.

And also in this shine moment I wish to thank my parents for their personal support or attention
who inspired me to go own way.

Thankyou…

5|Page
Contents
ABSTRACT....................................................................................................................................3
ACKNOWLEDGMENT.................................................................................................................5
CHAPTER 1:...................................................................................................................................9
INTRODUCTION OF COMPANY............................................................................................9
INTRODUCTION OF SYSTEM..............................................................................................10
PROBLEM STATEMENT.........................................................................................................11
LITERATURE REVIEW...........................................................................................................12
PROJECT OBJECTIVE............................................................................................................13
PROJECT SCOPE.....................................................................................................................14
LIMITATION OF THE STUDY...............................................................................................15
DESIGN OVERVIEW...............................................................................................................16
SYSTEM DESIGN....................................................................................................................16
User Analysis.........................................................................................................................16
Interface.................................................................................................................................16
WORK BREAK DOWN STRUCTURE (WBS)......................................................................17
GANTT CHART........................................................................................................................18
CHAPTER 2:.................................................................................................................................19
FEASIBILITY STUDY AND REQUIREMENTS GATHERING............................................19
FEASIBILITY STUDY.........................................................................................................19
REQUIREMENTS GATHERING.........................................................................................21
REQUIREMENT SPECIFICATION.....................................................................................24
USER REQUIREMENT.......................................................................................................24
FUNCTIONAL REQUIREMENT........................................................................................25
TECHNICAL REQUIREMENT...........................................................................................26
COMMON FUNCTIONALITY REQUIREMENT..............................................................27
NON-FUNCTIONAL REQUIREMENTS............................................................................27
PRODUCT REQUIREMENTS.............................................................................................29
OPERATIONAL REQUIREMENTS....................................................................................29
RESOURCE IDENTIFICATION..............................................................................................30
HARDWARE.........................................................................................................................30
SOFTWARE..........................................................................................................................30
THE SOFTWARE PROCESS MODEL....................................................................................31
Waterfall Model.....................................................................................................................31
6|Page
CHAPTER 3:.................................................................................................................................35
DOMAIN INVESTIGATION...................................................................................................35
DECISION SUPPORT TOOLS.................................................................................................35
DECISION THEORY............................................................................................................35
DECISION TREE..................................................................................................................35
TECHNICAL RESEARCH.......................................................................................................36
TECHNICAL RESEARCHING WILL BE HAVING THE FOLLOWS:..............................36
PROGRAMMING LANGUAGE..........................................................................................36
PHP........................................................................................................................................36
CSS........................................................................................................................................36
JAVASCRIPT.........................................................................................................................37
DATABASE...........................................................................................................................37
DESIGNS TOOLS.................................................................................................................37
DEVELOPMENT ENVIRONMENT- SUBLIME TEXT3...................................................38
METHODOLOGY................................................................................................................38
CHAPTER 4: DESIGN.................................................................................................................39
SOFTWARE SYSTEM DESIGN..............................................................................................39
CONTEXT DIAGRAM.............................................................................................................39
0TH LEVEL DFD....................................................................................................................39
1ST LEVEL DFD....................................................................................................................40
USE CASE DIAGRAM........................................................................................................41
CLASS DIAGRAM...............................................................................................................42
SEQUENCE DIAGRAM......................................................................................................43
ACTIVITY DIAGRAM........................................................................................................44
COLLABORATE DIAGRAM..............................................................................................45
INTRODUCTION TO DATABASE DESIGN..........................................................................46
ENTITY RELATIONSHIP DIAGRAM (ERD)...................................................................46
CHAPTER 5:.................................................................................................................................47
IMPLEMENTATION................................................................................................................47
STAGES / TYPES OF SYSTEM IMPLEMENTATION..........................................................47
DIRECT IMPLEMENTATION.............................................................................................48
PHASE IMPLEMENTATION...................................................................................................49
PARALLEL IMPLEMENTATION...........................................................................................50
USER INTERFACE DESIGNS.................................................................................................51

7|Page
 CODINGS..................................................................................................................................63
CHAPTER 6..................................................................................................................................69
TESTING...................................................................................................................................69
TESTING OVERVIEW.............................................................................................................69
TEST TECHNIQUES SELECTION.........................................................................................69
BLACK-BOX TESTING......................................................................................................70
White-Box Testing.................................................................................................................70
TEST PLAN..............................................................................................................................71
TEST CASES............................................................................................................................71
CHAPTER 7..................................................................................................................................72
MAINTENANCE......................................................................................................................72
SYSTEM MAINTENANCE.....................................................................................................72
CORRECTIVE MAINTENANCE: -....................................................................................72
ADAPTIVE MAINTENANCE:............................................................................................72
PERFECTIVE MAINTENANCE:........................................................................................72
PREVENTIVE MAINTENANCE........................................................................................73
SYSTEM MAINTENANCE PROCESS MODELS.................................................................73
QUICK-FIX MODEL............................................................................................................73
CHAPTER 8..................................................................................................................................75
CRITICAL EVALUATION AND CONCLUSION...................................................................75
SUMMARY OF THE PROJECT..............................................................................................75
LIMITATIONS OF THE SYSTEM...........................................................................................77
FUTURE ENHANCEMENTS..................................................................................................78
FUTURE IMPROVEMENTS AND FUTURE AVENUE.....................................................78
PHASE I- SUGGESTION FOR FUTURE WORK..............................................................78
PHASE II - SUGGESTION FOR FUTURE WORK............................................................78
CONCLUSION..........................................................................................................................79
REFERENCES..........................................................................................................................81
APPENDIX A: TEST CASES AND RESULTS........................................................................82

8|Page
 CHAPTER 1:
INTRODUCTION OF COMPANY

In this global world, all the industries depend on computers and computer based solutions.
Therefore COTTON COLLECTION (PVT) LTD also need computerized Management system
for manage employees, so COTTON COLLECTION (PVT) LTD at Maruthamunai will require
this service.
It intends to reduce the time and complexity of work in the admin (staff) s of the COTTON
COLLECTION (PVT) LTD in one perspective. Employee details in this system can be entered
and can be more relax. The project is started to develop software to the COTTON
COLLECTION (PVT) LTD to manage the Employees details. So this system helping to manage
employees details very easy. Therefore COTTON COLLECTION (PVT) LTD admin staffs are
able to handle huge amount of employees very quickly.

This chapter provides an introduction about the existing system and proposed system in briefly.
Motivation factors of the proposed system, function of the existing system and its drawbacks are
included. The objective of the proposed system and its functionalities are also described. Further
this chapter outlines the brief description of the software and hardware specification to develop
the employee management, development methodology and the time period to complete the
proposed system successfully, including Gantt chart and work breakdown structure and timeline
calendar
This COTTON COLLECTION (PVT) LTD is situated in Maruthamunai.
The company has been earning excellent reputation for reliability. This is
reflected in the quality of the products and timeliness The Company holding
limited business skills with methodical and old approaches to management
and training.

9|Page
 INTRODUCTION OF SYSTEM

The entire System of Employee Management (EMS) is designed to remove problems in

existing system and the organization will meet its specific aims. One of the most important
aims from the system is to provide detail profile of each employee. As a result the system is
most important for improving other systems of organization like human resources
management.
The role of EMS is to centralize the repository of staff data including recruitment, attendance
and salary. An effective Employee Management System helps to generate accurate and timely
employee information to fulfill the objectives.
EMS keeps the record of employee joining date, leaving date, assets provided. It manages salary
of employee according to the attendance. It also focuses on the capabilities and facilities
provided by the company. Without an employee management system it is tedious to control
employees. Some of the manual records are,
 Employee information record
 Report generation record
 Attendance maintaining record
 Leave Details
 Tour Funds details.

This EMS is a web based system and using this system means securing the activities of the
company Management. The vision is to provide a progressive and expandable information
service to company administration. By automating EMS documents that took up many large.

10 | P a g e
 PROBLEM STATEMENT

Existing system is manual, so it is hard to find information quickly. Slow and waste of time,
because the staffs need to go through each and every file to find single information. More
physical space are used to keep all the files. There is no enough security in manual system in
maintaining data, so that everyone can go through or alter the important data. Changing or
making corrections in the data are difficult, as it is not nice to cut or correcting with fluid and
write over it. So the current system has number of problems and drawbacks.
Searching information is difficult and time consuming,

The main problem faced by the admin is the difficulty to access the employee details for various
needs. For example if the admin needs to gather particular employee details. He would have to
get through all of the records one by one and copy down the selected information another paper
and wants to get the information.
Most of the work done by call through,

The system administrator calls through and get all the required information and input it in
another system after get verification.
Waste of time and money.

The administrator wasting time to manage details manually, spending time for manage. And
repetition of work done by the administrator.
It is very hard to find the employee details.

It is difficult to provide guidance without maintaining a proper management system. Finding

employee details is very difficult because the details are recorded in a same table without proper
classification of categories, saved in various different type of place and methods and there isn’t
any proper method for the recording details.
If they want to get an employee details they can’t get it easy,

The employee details are not classified position wisely. So employee details they can’t get it easy

11 | P a g e
 LITERATURE REVIEW

Employees not only need guidance from their managers or leaders, but they also need to know
that they will be there to help them when they need them or to help put things back on the right
track. Leadership need not imply that a leader is, by nature, wise, and inspirational. Darker forces
sometimes drive leaders as well as their followers. Bad leadership is as ubiquitous as it is
insidious (Kellerman, 2007, Pg. 17).
Kellerman (2007) further points out that, “Like good leaders, bad leaders are characterized by
traits such as intelligence, high energy, strong drive for power and achievement, decisiveness,
and determination. Bad leaders have a skill set that ranges from being good at communicating to
being good decision making. Kellerman (2007) also describes bad leaders as, “incompetent,
rigid, intemperate, callous, corrupt, insular, and evil” (Kellerman, 2007, Pg. 17). McGowan
(2010) also notes, “Leadership can’t lead if it can’t see” (McGowan, 2010, Pg. 3)

12 | P a g e
 PROJECT OBJECTIVE

General Objective

The main objective of this project is to develop an employee management system for COTTON
COLLECTION (PVT) LTD at Maruthamunai.

The Specific Objectives

This system overcomes the problems faced in the existing system. More time consuming to
search the necessary information about employee details in old method. It can minimize the
redundancy of the files and the time consuming when proposed system is used.

13 | P a g e
 PROJECT SCOPE

Scope of this project is to provide employee management system for COTTON COLLECTION
(PVT) LTD at Maruthamunai. It enables admin to insert, delete, edit, store, retrieve, analyze, and
summarize details. This system uses PHPMyadmin.MY SQphpmyadmin is the suitable
application program to access and manipulate data in a database when a user just clicks and
moves the mouse to communicate with the system. The interface is designed to be user friendly
so that the user will feel convenient and it is easy to understand the application. Here are the
scopes for this system that can be divided into two groups

Admin

The target admin for this system is the employees of COTTON COLLECTION (PVT) LTD who
is responsible for the Administrative, IT and other section. This system enables to manage all the
activities held in Administrative and other Branch.

System

This is a relational database management system which is built using phpmyadmin which
enables to run on all the computers. Which is has localhost servers

14 | P a g e
 LIMITATION OF THE STUDY

LIMITATIONS IN THE OLD SYSTEM

Searching information is difficult and time consuming,

The main problem faced by the admin is the difficulty to access the Employee details for various
needs. For example if the admin needs to gather particular Employees details. The user would
have to get through all of the records one by one and copy down the selected information another
paper and wants to get the information.

They need to check many times.

All the required information is called through by the admin and input it in another system after
the verification.
Most of the work done by call through,
It is unable to register all the information in online due to unavailable and lack of facilities. So
the administrative is forced to get the telephone numbers and contact them to get all the
information and input them another system.
Wastage of time and money.
The admin is wasting time in manual Details Storing, money spent for verification. And
repetition of work done by the admin.
It is very hard to find the Employee details.
It is difficult to provide guidance without maintaining a proper management system. Finding
Employee details is very difficult because the details are recorded in a same table without proper
classification of categories, saved in various different type of place and methods and future there
isn’t any proper method for the recording details.
If they want to get an Employee details they can’t get it easy,
The Employee details are not classified. So it is difficult to get the employee details easily. All
are very important problems faced by this garment with their system. And also they face
analyzing problem from this current system.

15 | P a g e
 DESIGN OVERVIEW
SYSTEM DESIGN
Administrative parties can add, edit, delete& update the particular details. Also they can fully
control this system.
User Analysis
According to the user analysis, this process is able to gathering information about manual
system, able to identifying its strength, problems & analyzing them to produce a concept for
the new system. The goal of this analysis stage is to truly understand the requirements for the
new system & develop a system concept that addresses them.
Interface
System has following features
Log in system –Administrator

Employee

 Add Employee

Personal Details

Leave’ Details and Tour Details

Help
Login in system-Employee

 View profile

Employee List

Personal Details

Attendance Details

Leave Details

leave Details and Tour details

Disciplinary Action Detail

 Edit profile
 Help

16 | P a g e
 WORK BREAK DOWN STRUCTURE (WBS)

The main purpose of Work Breakdown Structure is that firstly, it helps to define and organize the
scope of the total project more accurately and specifically. The most common way this is done is
by using a hierarchical tree structure. Each level of this structure breaks the project deliverables
or objectives down to more specific and measurable chunks. The second reason for using a Work
Breakdown Structure in projects is to help with assigning responsibilities, resource allocation,
monitoring the project, and controlling the project. Deliverables are made more precise and
concrete by COTTON COLLECTION (PVT) LTD so that the project team knows exactly what
has to be accomplished within each deliverable.
Better estimating of cost, risk, and time because we can work from the smaller tasks back up to
the level of the entire project are also allowed. Finally, it allows double check all the deliverables'
specifics with the stakeholders and make sure there is nothing missing.

Figure 1

17 | P a g e
 GANTT CHART
Type of bar-chart, shows both the scheduled and the completed work over a period. A time-scale
is given on the chart's horizontal axis and each activity is shown as a separate horizontal
rectangle (bar) whose length is proportional to the time required (or taken) for the activity's
completion. In project planning, these charts show start and finish dates, critical and non-critical
activities, slack time, and predecessor-successor relationships.

Figure 2

18 | P a g e
CHAPTER 2:
FEASIBILITY STUDY AND REQUIREMENTS GATHERING

FEASIBILITY STUDY

Feasibility study is the measure of how beneficial or practical the development of an information
system will be to an organization and ability to meet needs and effective use of the resources.
The feasibility study is preliminary study undertaken before the real work of a project starts to
Employee management system for Garment success. It is an analysis of all possible solutions to a
problem and a recommendation on the best solution to use. It involves evaluation how the
solution will fit into the corporation.

The purpose of a feasibility study is to determine whether or not the purpose of a new system can
be justified. It is important that we concern about the practicability of the implementation of the
above proposed Employee Management System. I have done mainly four feasibility study.

COST FEASIBILITY

The expenses of the proposed system which is developed, operated and maintained are taken in
to consideration under economic feasibility. The development cost includes system analysis,
design and installation. The operational costs indicates staff payments. The operation and
maintenance cost includes the system services. That has a computer but the management asked to
provide new computer with will performance. Technical intumesce computer, software, printer,
wires and some other equipment are required. Identification of cost and benefit factors of
developing agrarian service system are important.

19 | P a g e
TECHNICAL FEASIBILITY

This is the cotton collection (pvt) ltd, that they are normally feasible in technical side. Here it
specifies whether the system that has enough resources to develop and install in their Garment.
The availability and the provision of resources should be considered. Here the level of
technology consists of the programming language, the hardware resources, other software tools,
Network capability, reliability, and availability. The Garment has printer and personal computer,
they just need to buy a high capacity hard disk and scanner. Training is needed for the employees
to work with a system.
If latest computer are taken into consideration all the features are available for execute this
system.

OPERATIONAL FEASIBILITY

An evaluation to determine whether the system is operationally acceptable, and define whether,
the proposed system will fit in with the current operation. The determination of how the new
system will work with the Garment and whether it would fit with current operation is must
necessary. Also the trainings for user are needed to be considered. According to the performance
of the new system there is a necessity to check whether it works properly with the Garment
functions. Such as update the student, staff, registration information and course details of the
Centre is a user friendly system which has more benefits compared to the current manual
certificates issue system which is in operation in the Garment the computerized system which is
to be implemented consist a less burden on the users when compared to the manual system.

20 | P a g e
 REQUIREMENTS GATHERING

SELECTING THE SUITABLE FACT GATHERING TECHNIQUE

This module is specified for the purpose of the report generation for the HR on his desired
requests.
A database developer normally uses several fact-finding techniques during a single database
project.

There are five commonly used fact-finding techniques:

 Examining documentation

 Interviewing

 Observing the enterprise in action

 Research

 Questionnaires

EXAMINING DOCUMENTATION

Examining documentation can be helpful when you try to gain some insight as to how the
requirement for a database arose. You may also find that documentation can help to
acquire information on the part of the enterprise associated with the problem. If the
problem relates to the current system, there should have to be documents associated with
that system. By examining documents, forms, reports, and files associated with the
current system, you can quickly gain some thoughtful concepts out of the system.

21 | P a g e
INTERVIEWING

Interviewing is the most frequently used, and usually most useful, fact-finding procedure
used. We can interview to collect information from person face-to-face. There can be
several objectives for using interviewing such as finding out facts, verifying those facts,
clarifying these released facts, generating enthusiasm, getting the end-user involved,
identifying requirements, and gathering ideas and opinions. However, using the
interviewing practice must require proper communication skills for dealing effectively
with people who have different values, priorities, opinions, motivations, and
personalities.

Interview questions: -
1. What Kind of Website Should You Need?
 Statics

 Dynamic

2. What are your website features?

 How many pages should be included?

 Online Website or offline website

 Location

 Contact us

 Dynamic gallery and home page

3. You're going to create a website for any purpose.

 A system

 For business purposes

 For personal purpose.

4. Want the user login page on your website?

 No

22 | P a g e
  Yes

OBSERVING THE ENTERPRISE IN ACTION

Observing the enterprise in action Observation is one of the most successful fact-finding
techniques carried out for understanding a system. Using this technique, it is achievable to
either participate in or observe a person perform activities to learn about the system.

RESEARCH

A useful fact-finding technique is to research the application or the problem that you are
dealing with and want to put within a database. Computer trade journals, reference books,
and the Internet are good sources of information which can make available of huge
quantity of information on how others have solved similar problems/issues plus whether
or not any software packages exist to resolve or even partially solve your current
problem.

QUEATIONNAIRES

Another fabulous fact-finding method is to conduct surveys through questionnaires.

Questionnaires are special-purpose documents that allow facts to be gathered from a large
number of people while upholding some control over their responses. When dealing with
a large number of listeners or audience, no other fact- finding technique can tabulate the
same facts so efficiently. There are two types of questions that can be asked in a
questionnaire namely free-format and fixed-format. Free-format questions offer the
respondent greater freedom inputting answers. Fixed-format questions require specific

23 | P a g e
 responses from individuals, and for the given question, the respondent must choose from
the available answers.

REQUIREMENT SPECIFICATION

The Software Requirements Specification (SRS) describes the system requirements and system
actions. Once Employee Management System development progresses to the design activities, it
focuses our attention primarily on the question, how does the system do what it is supposed to
do? A SRS is a complete description of the behavior of the system to be developed.

This includes a set of use cases that describe all of the interactions that the users will have with
the software. A software requirements specification is a complete description of the behavior of
the system to be developed. This includes a set of use cases that describe all of the interactions
that the users will have with the software. Registration activities can be performed easily using
this system.
The four key points under Requirement Specifications include: user requirement, functional
requirement, technical requirement and common functional requirement

USER REQUIREMENT

The user requirement specifies user requirements specify what should be expected from the
software user expects to be constructed in a software project. An important and difficult step in
designing a software product is determining what the customer actually wants to do.

This is because often the customer is not able to communicate the entirety of their needs and
wants, and the information they provide may also be incomplete, inaccurate and self-conflicting.
The responsibility of completely understanding what the customer wants then falls on the

24 | P a g e
providers of the product. User requirements of Employee Management System can list these out
as follows.

Completeness-: contains all the information that is needed to define the system function.

Consistent-: does not conflict with other requirements in the requirement specification.

Verifiable Requirements-: is stated in such a way that it can be tested by inspection or analysis
of demonstration.

Clear and Concise Requirements-: must be easily read and understood by non-technical
people.

Traceable Requirements-: is easily traceable through specification design and testing.

Viable Requirements-: can be achieved within the budget and schedule.

Necessary Requirements-: must be present to meet system objectives.

Implementation free Requirements-: defines what functions are provided by the system.

FUNCTIONAL REQUIREMENT

To develop a fully tested update process, it is asked that the application should allow the user to
add, edit and find details and handle customer. To accomplish this, it is required to create php
and my sql forms. So it is asked to design the necessary interfaces using php to fulfill the above

25 | P a g e
requirement. Employee management System this process directed my efforts and created a
program which is coming out here.

Adding details to database: when an Employee comes to register, the system will add his
details to database. Update and delete data on added data.

Speed: the software of the computer is selected to perform fast work. Taking into consideration
all the factors mentioned above it is clearly recognized that the new system will increase the
effectiveness of the Centre. This shows that time spend on doing work is greatly reduced.

Search: if any Employee details are requested the system will allow to find the details from
related database using searches function over the internet.

Security: the computerized system will be password protected, so only authorized users who are
permitted to use the system can access.

Design: The system should be able to accept data from users through use of interface and
interactive forms. After a thorough analysis of the present system some solution to the problem
was identified. Below are listed some of the techniques for the proposed solutions.

TECHNICAL REQUIREMENT

The technical requirements are giving the information to the developers as to what the system
must adhere to. They are more often just facts that have to be true about the final system. The
technical requirement should give an insight as to what is being required basically from the
client. Most of the technical requirements can be converted to functional requirements by very
good questioning. Technical requirements for the proposed system are:

Domain name: for a web application, domain name is an address. The domain name is string of
text that has something at the end of it. Depending on the goal of the web application, should
choose the domain name that reflects the business.

Webhosting: it is physical location on the internet where the web application lives.

26 | P a g e
Web application page: so the final requirement for this web application to be online is to have
web application pages for the web application visitors to view.

COMMON FUNCTIONALITY REQUIREMENT

The common functionality requirement of the proposed system describes the efficient of the web
application functionalities. The common functions described what are the operations going to use
the web application, updating process, main deliverables of the web app and process of user
access control. The proposed Employee Management for Garment has above common
functionalities.

NON-FUNCTIONAL REQUIREMENTS

Although this equipment is not directly related with the system to be developed, they are very
important factors to take in to consideration for the development and successful implementation
of the system. A Non-Functional Requirement is usually some form of constraint or restriction
that must be considered when designing the solution. Under this section it identify non-
functional requirement within the projects scope. Non-Functional requirements of the virtual
learning environment are as follows

ACCESSIBILITY

The user should have the ability to access and benefit from the system at any time the
requirement is not to be confused with usability which is used to describe the extent to which a

27 | P a g e
system can be applied by specified users to achieve specified goals with effectiveness, efficiency
and satisfaction in a specified context of use.

AVAILABILITY

Simply put, availability is the proportion of time a system is in a functioning condition. This is
often described as a mission capable rate. Mathematically, this is expressed as 1 minus
unavailability. Does this represent? Finish the sentence what.

MAINTAINABILITY

Maintainability involves a system of continuous improvement - learning from the past in order to
improve the ability to maintain systems, or improving reliability of systems based on
maintenance experience. Maintainability is the ease with which a system can be maintained in
order to: isolate defects or their cause, correct defects or their cause, meet new requirements,
make future maintenance easier, or cope with a changed environment.

OPERABILITY

Operability is the ability to keep a system or a whole Garment installation in a safe and reliable
functioning condition, according to pre-defined operational requirements. In a computing
systems’ environment with multiple systems, this includes the ability of systems and processes to
work together to accomplish a common task such as finding and returning availability of
information.

INTEROPERABILITY

28 | P a g e
Interoperability is a property referring to the ability of diverse systems and organizations to work
together (inter-operate). Interoperability is a property of a system, whose interfaces are
completely understood, to work with other systems, present or future, without any restricted
access or implementation.

PRODUCT REQUIREMENTS

Product requirements are the requirements for one or more new features for an existing system.
Currently, Garment uses a manual system to perform all activities; thus, it can often face
complexity problems. Therefore the new system should have following new features.

All Employee registration recordings of transactions are managed in this Employee Management
System (name, Registration NO, Department details, Employee personal details).

Variety of reports are generated.(Employee Leave report)

New details can be added, deleted, updated and saved.

User can store all valuable data by using different database tables.

OPERATIONAL REQUIREMENTS

Operational requirements are qualities which influence a new system's entire development cycle.
It concentrates on three of the most important operational requirements:

Reliability

Growth

29 | P a g e
Availability

Accommodation of these requirements is based on an approach to functional decomposition

involving representation in terms of potential independent process or called virtual machines.
Functional requirements may be accommodated through hierarchical decomposition of virtual
machines, while performance requirements may be associated with individual virtual machines.
Virtual machines may then be mapped to a representation of a configuration of physical
resources so that performance requirements may be reconciled with available performance
characteristics

RESOURCE IDENTIFICATION

Software and hardware requirements describe that what are the software and hardware needed to
implement the proposed system. It is very vital to choose the best and recommended tools to
develop a system in a proper manner. System development actually needs bunch lines of code
and some data containers along with some architectural designs. Software and hardware
requirements for the proposed system are listed below.

HARDWARE
Hardware specifications: Hardware requirements for the personal computer to develop the
agrarian service system.
-Computer with 2 GB RAM complete with Windows operating system

- It should be at least an Dual core and above,

- US system of keyboard and a hard disk of 128 GB.-

-Network card/wifi.

30 | P a g e
SOFTWARE

MS Project 2012- to track the project

- MS Word 2013 - to document the work software applications needed.

- Dreamweaver to develop the system and

- Xampp Server with MySQL to implement the database will be required.

THE SOFTWARE PROCESS MODEL

Waterfall Model

Subdividing the process of system development procedures is known as a life cycle model. Like
all living things have the development stages from its conception, information systems also have
the development stages. Various project life cycles can be applied to information systems in
development. Waterfall model is selected by me as a life cycle model for the development of
employee’s management system. The simplest system development life cycle model is the
waterfall model, which states that the phases are organized in a linear order. A project begins
with requirement analysis. The design starts after the requirements analysis IS done. And coding
beings after the designing is done. After the complement of part of programming, the code will
be integrated and tested. On successful completion of testing, the system is installed. After this
the regular operation and maintenance of the system takes place.

31 | P a g e
Reasons for Choosing the Waterfall Model

Easy to explain to the user

Stages and activities are well defined

Helps to plan and schedule the project

Verification at each stage ensures early detection of errors / misunderstanding

It allows compartmentalizing the life cycle into various phases, which allows planning the
resources and effort required through the development process.

It enforces testing in every stage in the form of reviews and unit testing. Can conduct design
reviews, code reviews, unit testing, and integration testing during the stages of the life cycle.

It allows setting expectations for deliverables after each phase

Requirement Analysis: This phase does description of the techniques that will be employed
to gather the requirements for the proposed system. The various requirements gathering in
techniques that will be employed including the following:

32 | P a g e
Reading: This particular technique will be employed that enable to read some of the
guiding documents that the Centre does use to come up with the required rates of the various
Process and service in the Garment

Questionnaire: This technique will be used to attain the format of the current system because it
provides the chance to collect information from respondents who are conversant with the whole
system understudy. These were used to catch a wide scope of employees because it was going to
be difficult to manage all employees details since they come. The system will help you manage
employees details clearly. Sometime employees also can register their details. The questionnaires
also helped to fill their details orderly.

Observation: This method will be also employed so that researcher acknowledges the flow
of activities. An observation was also carried out which helped me to know and understand how
the information flows in the manual registration systems and the morale, mood, ethics and
culture of those involved in the recording of employees details were also examined and analyzed.

Design: The requirements of the proposed system will be derived from the data that consists
inputs like employees details with reports. The data flow diagrams, context diagrams and entity
relationship diagrams will be fully employed. All these models will give the conceptual view and
validate analyzed end-user requirements. As a major modeling tool, organizing the data in the
project into entities and also

define the relationships among the entities are helped by the entity relationship diagram. This
process will enable the analyst to understand database structure so that data can be stored and
retrieved in a most efficient manner. The flow of data from external entities into the system is
shown by DFDs. data moving from one process to another as well as its logical storage is also
shown.

33 | P a g e
Implementation: In order to develop the front-end of the system, latest Integrated
Development Environment from Microsoft called Sublime2 will be used. The front-end is based
on web application for the back-end database, another product from Microsoft for database
management, Phpmyadmin. They will be used. For report development Crystal Reports for php
will be used.

Testing and Deployment: The system will be deployed as a package it is created for using
the Sublime2. The package wizard will collect all the program files which are needed to run the
system. As long as the database it concerned, Phpmyadmin will be installed. For the reports the
user must have the same database software and connectivity setup configured as in the
development computer. If they don’t, the reports in our application will fail or we will need to
dynamically configure the database the report is using via the Automation Server.

System Analysis Methodology: The main methodology involves in this research are
collecting data and employee management system development. Collecting data method is to
gather data needed to develop the system. The system will be developed using a relational
database which is phpmyadmin. This research methodology chart shown below.

34 | P a g e
CHAPTER 3:
DOMAIN INVESTIGATION

DECISION SUPPORT TOOLS

DECISION THEORY
Decision theory (or the theory of choice not to be confused with choice theory) is the study
of an agent's choices. Decision theory can be broken into two branches: normative decision
theory, which analyzes the outcomes of decisions or determines the optimal decisions given
constraints and assumptions, and descriptive decision theory, which analyzes how agents
actually make the decisions they do.

Decision theory is closely related to the field of game theory and is an interdisciplinary
topic, studied by economists, statisticians, psychologists, biologists, political and other
social scientists, philosophers, and computer scientists.

Empirical applications of this rich theory are usually done with the help
of statistical and econometric methods.

35 | P a g e
DECISION TREE

A decision tree is a decision support tool that uses a tree-like graph or model of decisions and
their possible consequences, including chance event outcomes, resource costs, and utility. It is one
way to display an algorithm that only contains conditional control statements.

A decision tree is a flowchart-like structure in which each internal node represents a “test” on an
attribute (e.g. whether a coin flip comes up heads or tails), each branch represents the outcome of
the test, and each leaf node represents a class label (decision taken after computing all attributes).
The paths from root to leaf represent classification rules.

TECHNICAL RESEARCH

TECHNICAL RESEARCHING WILL BE HAVING THE FOLLOWS:

PROGRAMMING LANGUAGE

The successful development of the proposed system is requiring such as good and strong
programming tools to create a system supports as many as users simultaneously. There are
three different types of programming languages are playing in the field of the proposed
system to choose later on the appropriate one for implementation.

PHP

PHP is a server-side scripting language designed for web development but also used as a
general-purpose programming language. PHP stands for PHP: Hypertext Preprocessor.
Hypertext refers to files linked together using hyperlinks, such as HTML (Hyper Text
Markup Language) files. Preprocessing is executing instructions that modify the output.
36 | P a g e
 Taken directly from PHP's home, PHP.net, "PHP is an HTML embedded scripting language.
Much of its syntax is borrowed from C, Java and Perl with a couple of unique PHP-specific
features thrown in. The goal of the language is to allow web developers to write
dynamically generated pages and reports quickly

CSS

Cascading Style Sheets (CSS) is a style sheet language used to describe the presentation
semantics (the look and formatting) of a document written in a markup language. It’s most
common application is to style web pages written in HTML and XHTML. CSS is designed
primarily to enable the separation of document

By using CSS one could separate HTML content from its appearance, distinguishing style
from structure. CSS gives the following advantages.

Control layout of many documents from one single style sheet more precise control of
layout.

JAVASCRIPT
JavaScript is primarily used as part of a web browser in order to provide enhanced user interfaces
and dynamic websites. This enables programmatic access to computational objects within a host
environment. It is used to enhance the usability through providing more interactive, speedy
environment and to implement the client side validation as well.

DATABASE
The development of the database is another task for the developer. It is because; it involves
design and technical issue of the system database development.

37 | P a g e
The technical issue might be some occurred problems during the development like a database
may not be able to link to another database which is relevant. It may fail to perform the functions
from what was required. The design of it is an important to determine the flow of information.
The purpose of that is to know how to address the problems during the development of the
database system.

DESIGNS TOOLS
User Requirements: - A research has been carried out through researches of users’ requirements
for the new proposed system development and has determined a result that was based on the
summary report that generates from all research methods as follows:
System must be easy to get started
The selection point must be clear
The system must be fast in response time
The system must be easy to use
Users would always know what the system is doing
Users would always be able to control the operation from time to time
The screen design must be consistent in order to minimize confusion.

DEVELOPMENT ENVIRONMENT- SUBLIME TEXT3

Sublime text3 is a web design and development application that provides a code editor with
standard features such as syntax highlighting, code completion, and code collapsing as well as
more sophisticated features such as real time syntax checking and code introspection for
generating code hints to assist the user in writing code.
The Design view facilitates rapid layout design and code generation as it allows users to quickly
create and manipulate the layout of HTML elements. Sublime Text3 features an integrated
browser for previewing developed webpages. Allowing content to be open in locally installed
web browsers.

METHODOLOGY

38 | P a g e
According to Bassil 2012, “the process of building computer software and information system
are always dictated by different methodologies and development techniques, which provides
framework that is used to plan manage and control information system development process.
Formally SDLC has many utilities in several industrial and engineering such as mechanical
engineering, process engineering, software and system engineering. All SDLC model consists of
sequence of phases that must be followed and completed by system designers and developers to
deliver the final product for utility".
So the web-based Employee management system help full to manage & maintain all their
company administrative activities because information will be rightly available and in a correct
format to company

39 | P a g e
 CHAPTER 4: DESIGN
SOFTWARE SYSTEM DESIGN

CONTEXT DIAGRAM

The top-level diagram is often called a “context diagram”. It contains a single process, but it
plays a very important role in studying the current system. The context diagram defines the
system that will be studied in the sense that it determines the boundaries. Anything that is not
inside the process identified in the context diagram will not be part of the system study. It
represents the entire software element as a single bubble with input and output data indicated by
incoming and outgoing arrows respectively.

0TH LEVEL DFD

Context Flow Diagram gives us the complete details about the inputs and outputs for a given
system. In the above system the main task is to identify a criminal face. So, the operator and
eyewitness are the inputs to our system and criminal face is desired output.

LOGIN PROCESS

LOGIN User Id PROCESS SCREEN

Password

ERROR IN INPUT

40 | P a g e
1ST LEVEL DFD

Description:
The inputs to the process are User Id and Password given by the developer to allow the software
available for the Admin environment. After giving the inputs the details, checks whether the
entered ones are valid are not. It displays screen if match occurs otherwise error message if they
are not matched.
MAIN SCREEN PROCESS

MAIN SCREEN
ADMIN Add Emp

Add Skill
Reports

Add
Placement

Add Training
Report

Add
Compensation

41 | P a g e
42 | P a g e
USE CASE DIAGRAM

Login

Administrator

Check Emp Details

Employee

Add Emp details

Check Training Details

Add training details

Check Compensation

Add Compensation details

Logout

43 | P a g e
CLASS DIAGRAM

Emp login

HR Administration
Hr Name
Hr ID
Add Details
Add Emp Details()
Add Training Details()
Add Compensation()
Login()
Check Training Details()
Check Compensation()
Check Employee()
Employee Details
Dept Assigned()
Date of Joining()
Emp Details()
Emp Component()

Training deatils
Dept
Location
Compensation
Emp Name
Skill Details
Compensation Amt()
Skill Content() Year of work()
Training Assign() Skill Report()
Duration()

SEQUENCE DIAGRAM

44 | P a g e
 Training Compensation Placement Skill Emp deatils
HR Admin Employee

1. login

2. verify

3. Add emp details

4. Add skills Report

5. Add Placement report

6. Add Training Report

7. Add Compensation Report

8. log out

9.Check emp deatils

10.Check employee skills report

11.Check employee placement report

12. check emp compensation report

13.check employee training report

14.Logout

ACTIVITY DIAGRAM

45 | P a g e
46 | P a g e
COLLABORATE DIAGRAM

Emp login
Check
Hr Admin
Training

Check Emp Check

Detail Compensatiopn
Add
Training

Add
compensation

Add Emp
Details

47 | P a g e
INTRODUCTION TO DATABASE DESIGN

ENTITY RELATIONSHIP DIAGRAM (ERD)

CHAPTER 5:
IMPLEMENTATION

48 | P a g e
 The implementation is the final and important phase. It involves User training, system
testing and successful running of the developed system. The users test the developed system
when changes are made according to the needs. The testing phase involves the testing of the
developed system using various kinds of data. An elaborate testing of data is prepared and
system is tested using the tests data.

Implementation is the stage where theoretical design turned into a working system.
Implementation is planed carefully to propose system to avoid unanticipated problems. Many
preparations involved before and during the implementation of proposed system. The system
needed to be plugged in to the organization’s network then it could be accessed from anywhere,
after a user logins into the portal. The tasks that had to be done to implement the system were to
create the database tables in the organization database domain. Then the administrator was
granted his role so that the system could be accessed.

The next phase in the implementation was to educate the system. A demonstration
of all the functions that can be carried out by the system was given to examination
department person, who will make extensive use of the system

STAGES / TYPES OF SYSTEM IMPLEMENTATION

The term implementation can be defined as the act of accomplishing some aim or executing
some order, and if you consider the context of its use in system development, you will
understand what the task implementation does exactly. The act of implementation in software
development is nothing but installing the software other than the developing environment or in
the actual client’s environment to deploy the software. There are three strategies that can be used
to do this: direct, phased or parallel running.

DIRECT IMPLEMENTATION

This involves taking the old system offline and putting the new system. This is cheap but also
quick, allowing new features to be put to use immediately. This usually takes place on a set date,

49 | P a g e
often after a break in production or a holiday period so that time can be used to get the hardware
and software for the new system installed without causing too much disruption.

ADVANTAGES:

The most rapid of all the strategies provided it works.

Less risk of confusion between old and new systems.

DISADVANTAGES:

Most stressful for the users - the old system has gone so there is no going back if they have
difficulties.

Most difficult to train staff on as the new system was not in place to learn on before the
changeover.

Most stressful for the developers - all the data and files from the old system will have to
Be converted ready for use on the new one.

PHASE IMPLEMENTATION

This involves taking offline parts of the old system and replacing them with the corresponding
parts of the new system. The actually conversion from the old parts of the system to the new

50 | P a g e
parts may be either parallel or direct. This provides a compromise between parallel and direct
conversion.

ADVANTAGES:

Very structured, each phase can be fully evaluated before moving onto the next one.

Lower risk, a well-planned and controlled introduction of the new system.

Easy to train staff by letting they learn new skills on each phase as it is introduced.

DISADVANTAGES:

Slower than direct implementation.

Although each phase is easy to evaluate, you have to wait until all the phases are complete before
you can evaluate the whole change over.

PARALLEL IMPLEMENTATION
Parallel conversion involves keeping the old system running alongside the new system for the
first couple of weeks or months after the introduction of the new system. This means that any
problems with the new system will not affect the continuation of the business. The problem with
parallel implementation is that it costs more to run both systems and it also means data has to be

51 | P a g e
entered twice which take more time and is liable to errors. During changeover, a new system and an
existing system run side by side. To input the same data and perform the same processes, compare
their output and prove the reliability of the new system. If the new system is accepted, the existing
system will stop running and will be replaced by the new one.

ADVANTAGES:
If there are initial problems with the new system then the old one can still be used.

Both systems can easily be compared.

Easy to train staff by letting they learn new skills on the parallel system.

Easy to evaluate because the new and old systems are both running.

DISADVANTAGES:
Expensive - both systems are being run as fully operating versions so both are doing the same
job. This may mean duplication of staff and hardware.
Some risk - there is a greater chance of confusion or errors if the two different systems are being
run side-by-side.
It has been decided to implement the developed virtual learning environment using the parallel
implementation until the users become familiar with the new system. Because of this, the
problems occurred in the new system will not affect the day to day activities of Global
Information Technology.

USER INTERFACE DESIGNS

Employee Management System covers many functional areas in order to handle Institute day to
day activities efficiently. In this chapter describes the general guidelines to use the System
correctly with System interfaces and appropriate explanations. The most acceptable way to

52 | P a g e
understand the process flow of the system is to navigate the help file which is embedded with the
system. Anyhow, following section outlines user manual with screen shot.

53 | P a g e
54 | P a g e
55 | P a g e
56 | P a g e
57 | P a g e
58 | P a g e
59 | P a g e
60 | P a g e
61 | P a g e
62 | P a g e
63 | P a g e
CODINGS
Coding for home page

64 | P a g e
Coding for login page

65 | P a g e
66 | P a g e
Coding for Employee Add page

67 | P a g e
68 | P a g e
Coding for Leave Form

69 | P a g e
70 | P a g e
CHAPTER 6:
TESTING
This chapter will provide the details of Testing and System Debugging for the proposed system.
It will cover Difference Test cases, Type of Testing in to Unit testing and integration Testing
Further Software Testing Strategies in to Black-box testing and white box testing and Debugging
Method/approaches for system debugging

TESTING OVERVIEW
TEST TECHNIQUES SELECTION
Software test strategy is an outline that describes the testing approach of the software
development cycle. It is created to inform project managers, testers, and developers about some
key issues of the testing process. This includes the testing objective, methods of testing new
functions, total time and resources required for the project, and the testing environment.

Test strategies describe how the product risks of the stakeholders are mitigated at the test-level,
which types of test are to be performed, and which entry and exit criteria apply. They are created
based on development design documents. System design documents are primarily used and
occasionally, conceptual design documents may be referred to. Design documents describe the
functionality of the software to be enabled in the upcoming release. For every stage of
development design, a corresponding test strategy should be created to test the new feature sets.

Reviews, walkthroughs, or inspections are referred to as static testing, whereas actually

executing programmed code with a given set of test cases is referred to as dynamic testing. Static
testing can be omitted, and unfortunately in practice often is. Dynamic testing takes place when
the program itself is used. And also Box approach testing Strategy Software testing methods are
traditionally divided into white- and black-box testing. These two approaches are used to
describe the point of view that a test engineer takes when designing test cases.

71 | P a g e
BLACK-BOX TESTING

Black-box testing, also called behavioral testing, focuses on the functional requirements of the
software. That is, black-box testing enables the software engineer to derive sets of input
conditions that will fully exercise all functional requirements for a program. Black-box testing is
not an alternative to white-box techniques. Rather, it is a complementary approach that is likely
to uncover a different class of errors than white-box methods. Black-box testing attempts to find
errors in the following categories. Incorrect or missing functions, interface errors, errors in data
structures or external database access, behavior or performance errors, and, Initialization and
termination errors.

The Employee system represents a new approach to security auditing. Employee Management
System does not need the source code to analyze and uncover vulnerabilities. Black-box testing
treats the software as a “black box”, examining functionality without any knowledge of internal
implementation. The tester is only aware of what the software is supposed to do, not how it does
it. Black box test no required any knowledge of the inner design of the code or logic. It also
known as functional testing will only focus on the programmed interface. The interfaces only
include the inputs and outputs of a particular program.
White-Box Testing

While white-box testing can be applied at the unit, integration and system levels of the software
testing process, it is usually done at the unit level. It can test paths within a unit, paths between
units during integration, and between subsystems during a system–level test. Though this method
of test design can uncover many errors or problems, it might not detect unimplemented parts of
the specification or missing requirements.

White Box Testing is the testing of a software solution’s internal coding and infrastructure. It
focuses primarily on strengthening security, the flow of inputs and outputs through the
application, and improving design and usability. White box testing is also known as clear, open,
structural, and glass box testing. It is one of two parts of the “box testing” approach of
software testing. White box testing is based on the inner workings of an application and revolves

72 | P a g e
around internal testing. The term “white box” was used because of the see-through box concept.
The clear box or white box name symbolizes the ability to see through the software’s outer shell
(or “box”) into its inner workings.
White box test is a test type which based on an analysis of internal workings and structure of a
piece of software. To do the white box test proper knowledge of the inner design of the code or
logic is required. This is the main difference of black box testing and white box testing.

TEST PLAN

TEST CASES

A test case has components that describe an input, action or event and an expected response, to
determine if a feature of an application is working correctly. Test cases are often referred to as
test scripts, particularly when written. Written test cases are usually collected into test suites.
After design virtual learning environment. It is testing with test cases. I divided test cases into
basically two cases,

Positive Test case: System is doing what it supposed to do, it’s called positive Test case.

Negative: System is not doing what it shouldn't supposed to do that, it's called negative Test case.

And also different test cases are can mention with four types (integration test case, Functional
Test case, Non-Functional Test cases (which include security, performance and usability), User
Acceptance Test cases (end to end scenario)

73 | P a g e
CHAPTER 7
MAINTENANCE

SYSTEM MAINTENANCE

Software maintenance is a very broad activity that includes error corrections, enhancements of
capabilities, deletion of obsolete capabilities, and optimization. Because change is inevitable,
mechanism must be developed for evaluation, controlling and making modifications. So any
work done to change the software after it is in 86
operation is considered to be maintenance work. The purpose is to preserve the value of software
over the time. The value can be enhanced by expanding the customer base, meeting additional
requirements, becoming easier to use, more efficient and employing newer technology. There are
four types of system maintenance.

CORRECTIVE MAINTENANCE: -
This type of maintenance implies removing errors in a program, which might have crept in the
system due to faulty design or wrong assumptions. Thus, in corrective maintenance, processing
or performance failures are repaired.

ADAPTIVE MAINTENANCE: -
In adaptive maintenance, program functions are changed to enable the information system to
satisfy the information needs of the user. This type of maintenance may become necessary
because of organizational changes which may include Change in the organizational procedures,
Change in organizational objectives, goals, policies, Change in forms, Change in information
needs of managers.

PERFECTIVE MAINTENANCE: -
Perfective maintenance means adding new programs or modifying the existing programs to
enhance the performance of the information system. This type of maintenance undertaken to
respond to user’s additional needs which may be due to the changes within or outside of the
organization.

74 | P a g e
PREVENTIVE MAINTENANCE: -
Preventive maintenance involves changes made to a system to reduce the chance of future
system failure. An example of preventive maintenance might be to increase the number of
records that a system can process far beyond what is currently needed or to generalize how a
system sends report information to a printer so that the system can adapt to changes in printer
technology.

SYSTEM MAINTENANCE PROCESS MODELS

There are many types of software maintenance process models such as,

Waterfall Model

Spiral Model

Quick-Fix Model

Iterative Enhancement Model

There are several approaches to software maintenance. These approaches have different features. The
selection of software maintenance approach is done based on specific needs of the maintenance
problem. It has been decided to perform the System Maintenance for developed system through the
Quick-Fix model.

QUICK-FIX MODEL

A typical approach to software maintenance is to work on code first, and then make the
necessary changes to the accompanying documentation. This approach is captured by the quick-
fix model. The model is preferred for projects involving small reworks where the code is
changed directly and the changes are reflected in the relevant documents later. In this approach,
the project starts by gathering the requirements for changes. The requirements are next analyzed
to formulate the strategies to be adopted for code change. This is usually done by associating a
few members of the original development team. The availability of a working old system

75 | P a g e
facilitates the task of the maintenance team as they get a good insight into the working of the old
system. They can also compare the working of their modified system with the old system. Also,
debugging of error becomes easy as the program traces of both the systems can be compared to
localize the bugs.

76 | P a g e
 CHAPTER 8
CRITICAL EVALUATION AND CONCLUSION

SUMMARY OF THE PROJECT

Chapter Title Description

Chapter -01 Introduction It provides the introduction of project,
details of project background, problem
statement, literature review, objectives of
project, project scope, limitation of the
study, design over view, work breakdown
structure Gantt chart, significant of my
project.
Chapter -02 Feasibility study and This chapter will describe the initial
requirement gathering investigation the survey will be expanded
to a more detailed feasibility study
whether the project feasible or not. This
will considered economic, technical and
behavioral factors in the system
development. Requirement gathering
techniques that will be employed to gather
the requirements for the web- based
employee management system. It describe
the functional requirement, non-
functional requirements, user
requirements, and system requirements.
Chapter -03 Domain investigations This chapter involves the systematic
identification, locating and analysis of
documents containing information related
to the research problem being
investigated. Such as Domain Research as
well as Technical Research that each will
be giving an explanation of its scope and
where will be up to of process
Chapter -04 Design This chapter describes how the
requirements of this system will be
derived from the data collected in the
Requirement Analysis chapter. It is also
about the components of hardware and
software configurations. That will be

77 | P a g e
 explained by use case diagram, activity
diagram, dataflow diagram, sequence
diagram, and ER diagram. And also it
describes the databases design which are
included in this system.
Chapter– implementation This chapter describes how this system
05 will be physically implemented. And also
will be shown the process of accessing
and while interacting with the system how
it will goes with the features, orders, and
actions. At every action, there will be a
respond for it that will leads to where the
user will willing to go. It will includes
codes of this system, and screenshots of
this system..
Chapter– System Testing Testing chapter will emphasize on this
06 system’s functionalities to make sure that
all functions will be well functioning
Testing will include unit, integration,
components and system testing parts.

Deployment part describe the how I will

deploy my system in the real environment
Chapter -07 Maintenance This chapter describes maintenance and
over view of maintenance.
Chapter -08 Critical evaluation and This chapter will described total
conclusion conclusions of web-based employee
management system and what are the
further recommendation and what future
enhancement of this system are.

LIMITATIONS OF THE SYSTEM

78 | P a g e
First shortcoming of this project is all about a temporal factor; the time schedule which has been
given in the first chapter is not being followed by me since the examination time table had made
a big impact when make my own schedule to work with the system. But still I have left the
schedule for reality.
However one of the important security or database integrity aspects still lies in the system and
which can make relatively minimal problems in the integrity of the data in the database. There is
no more filtering in the front end of the system and which can cause serious problem if the user
unintentionally enters some erroneous data in the fields. There will be no issues provided that the
user carefully insert new records or updates exiting records with appropriate data in to the
database components.
This specific shortcoming and other lacking things will be ratified in the future upgrading and
more further advancements will also take place to make the software as a professional one in
future , if god wills.

79 | P a g e
 FUTURE ENHANCEMENTS

FUTURE IMPROVEMENTS AND FUTURE AVENUE

As with many project that have been undertaken do far, the “Finalized” solution is quite often
open to additions. When considering this project under the above aspect, there are number of
possible improvements that better take place which will improve the performance and quality of
this system. Decided future works are below

PHASE I- SUGGESTION FOR FUTURE WORK

In this first phase it has been decided to develop the system overall Institute Management
Process. Through this improvement it can provide overall human resources details and physical
resources storage and functionalities. Also provide a chance to EMS.
PHASE II - SUGGESTION FOR FUTURE WORK

In the second phase it has decided to provide Employee Management System services to
Employee and Staff. So it will be a better opportunity to adapt with modern technology and in
future many facilities and benefits wants add into system.

80 | P a g e
CONCLUSION

As describe throughout this document the main purpose of implementing the Employee
Management System is to provide our User easy, economic, efficient and accurate software
based solution to help in their routine activities. Hence my main and biggest objective was to
come up with a complete computerized, automated system and to fulfill all the requirements of
new system in order to enhance efficiency and increase accuracy.

Mostly, a Garments use paper base document to do their routine work and it is more tedious
work to handle large number of documents. Other firms that use computers are only use simple
office automation applications such as MS Word, MS Excel to store details about people and
other documents and that is inappropriate way to store details, it is too hard when search details
or update (change) data and leads to inconsistent information.

To make sure that this works which helps us to understand existing level of technology and
drawbacks of those systems.

After the gathering of requirements the next step was to analyze the gathered requirements.
Analysis of the gathered requirements was also done with a lot of care and paid a lot of attention
in bringing out the requirements. In this step I clarify all the problems and misunderstandings
about what should be the requirements (problems) I should solve throughout this project.

After a complete analysis of all the gathered requirements I moved to the design phase. I broke
down the whole process into smaller sub systems and divide responsibility over the members in
the group to handle particular parts of the system such as Patient records handling, Employee
record handling, Staff record handling, Leaving and Travel Sheet record handling and report
generation so that it would be much easier for us to design perfect design and even the smallest
errors can be noticed. I did through requirements specification and design solutions using UML
diagrams such as use case diagrams, activity diagrams to get function wise good design and to
map whole solution as one, entity relationship diagram and class diagrams have used and those
diagrams are appended to this document.

81 | P a g e
This project gave me the opportunity to get knowledge about many new programming languages
and programming practices. I gained lots of knowledge about the programming and software
development process and also about modeling methods, and improve my project management
skills as well.
In conclusion, I must mention that this project were able to fulfill all the requirements that client
expected and additional features to easy their tasks in day to day work. This document was
prepared in order to give the reader a fairly well knowledge of the background of this Employee
Management System for Garment.

82 | P a g e
REFERENCES

Scribd. (2019). Scribd - Read books, audiobooks, and more. [online] Available at:
https://www.scribd.com/ [Accessed 1 Oct. 2019].

GanttPRO. (2019). Online Gantt Chart Software for Project Planning | GanttPRO. [online]
Available at: https://ganttpro.com [Accessed 1 Oct. 2019].

Employee Management System Project . [online] Slideshare.net. Available at:

https://www.slideshare.net/SyedJunaid33/employee-management-system-project-propsal
[Accessed 1 Oct. 2019].

UK Essays. November 2018. A Review Of Employee Management Systems Information

Technology Essay. [online]. Available from: https://www.ukessays.com/essays/information-
technology/a-review-of-employee-management-systems-information-technology-essay.php?
vref=1 [Accessed 1 October 2019].

En.wikipedia.org. (2019). Decision theory. [online] Available at:

https://en.wikipedia.org/wiki/Decision_theory [Accessed 1 Oct. 2019]

Decision Trees — A simple way to visualize a decision. [online] Available at:

https://medium.com/greyatom/decision-trees-a-simple-way-to-visualize-a-decision. [Accessed 1
Oct. 2019

83 | P a g e
APPENDIX A: TEST CASES AND RESULTS
Test Case for Admin Login Process

Test Case for Employee Login Process

84 | P a g e