Human Resourse Management

FINAL YEAR PROJECT PROPOSAL
HUMAN RESOURSE MANAGEMENT SYSTEM

WEB BASED APPLICATION
Submitted By
ABDUL BASIT
Reg No: 1442-416024
Supervised By
Sir Rana Umar Aziz
PRESTON UNIVERSITY - ISLAMABAD CAMPUS

Session 2016-18
ABDUL BASIT (REG # 1442-416024) Page 1

HUMAN REASOURSE MANAGEMENT SYSYTEM
APPROVAL SHEET
This is to certify that the project titled “HUMAN RESOURSE MANGMENT

SYSTEM” is submitted by ABDUL BASIT MCS (4th Semester).
__________________
It is our judgment that this project is of sufficient standard to warrant its

acceptance for the award of MCS degree by the Department of Computer Sciences,
Preston University Islamabad.
COMMITTEE
1. External Examiner ________________________________
2. Internal Examiner ________________________________
3. Supervisor ________________________________
4. Head of Department ________________________________

Undertaking
I certify that research work titled “HUMAN RESOURSE MANGMENT SYSTEM”

is my own Effort. The work has not been presented elsewhere for assessment.
This is purely a final year project. Where material has been used from other
sources it has been properly acknowledged / referred.

ACKNOWLEDGEMENTS
All praise to Allah Almighty, the merciful and compassionate, who enabled me
to complete this project.
I am also thankful to our Prophet Hazrat Muhammad (PBUH), because, His life
was pattern for me to follow, so that, I have accomplished my task of completing this
project in time.
I also want to express our profound thanks to our Sir Umar Aziz Rana who
always encouraged me during this project to work with full determination and gave us
the true guidance in a very friendly and helpful manner throughout this project.
I feel pleasure to express my deepest affection for my parents and other family
members, who prayed for my success and encouraged us. Their love, care, appreciation
and trust gave me confidence.
And last but not the least, I would like to thank everyone whose names have not
been mentioned here but have guided us in one way or the other for the completion of
this project.
ABDUL BASIT ………………………………..

Declaration of MCS Project Report and Copyright
Author’s Full Name : ABDUL BASIT
Title : HRMS
Academic Session : 2016-2018
I declare that this report is classified as:

CONFIDENTIAL Contains confidential information under the Official Secret Act
1923.
RESTRICTED Contains restricted information, and may not be copied or circulated

without prior approval. Those who rightfully receive this
Document are entitled to copy or multiply this document only for internal use.
OPEN ACCESS Contains open access information, and can be copied or circulated
without prior approval.
I acknowledge that Preston University reserves the right as follows:
1. The report is the joint property of Preston University and Author.
2. The Examination Department of Preston University has the right to make copies of the
report for the purpose of evaluation.
3. The Library of Preston University has the right to make copies of the report for the
purpose of study.
4. The Faculty of Computer Sciences of Preston University has the right to make copies of
the report for the academic exchange.
Signature of Student Signature of Supervisor

ABDUL BASIT Mr. Umar Aziz Rana
Date: Date:

DEDICATION
Specially dedicated to my parents for their love, support

and sacrifice.

ABSTRACT
The project Human Resources Management System, HRMS is a web based

system.
It is based on employee and new user architecture.
“Human resource management is the process of determining
manpower requirements and the means for meeting those
requirements in order to carry out the integrated plan of the
organization”.
Human resource management is the process including forecasting,
developing and
Controlling by which a firm ensures that it has the right number of people
and the right
Kind of people at the right places, at the right time doing work for which
they are
Economically most useful.
ABDUL BASIT

Abdul Basit
+923335385931
abdulbasitawan11@gmail.com
About me
“May Allah have mercy on him who sends me my faults as a
present." (Hazrat Umar Farooq r.a.)
Education
1 B Tech
2 Intermediate
3 Matriculation
Master thesis
Human Recourse Management
Title System
Supervisor Mr. Umar Aziz Rana
Experience
1 Web Development
2 MS Office,
3 Software Troubleshooting
4 Office Management
Languages
English Speaking, Writing, Listening Professional language
Urdu Speaking, Writing, Listening Educational language
Punjabi Speaking, Writing, Listening Mother tongue
Computer skills
1 Web Development
2 MS Office,
3 Software Troubleshooting

PROJECT IN BRIEF
Project Title : HRMS
Supervised By : Sir Umar Aziz Rana
Date Started : Feb, 2018
Date Completed : June, 2018
Technologies Used : SQL, Php, HTML, CSS, Java Scrip, C#, bootstrap
Database Server : Xampp
Hardware Used : Computer system, Printer, computer networks

TABLE OF CONTENTS
Chapter 1 Introduction.................................................................................................................... 13
1.1 Introduction ........................................................................................................................... 14
1.2 Problem in Existing System ............................................................................................14
1.3 Proposed System ..................................................................................................................15
1.4 Scope of Human Recourse Management System.........................................................15
1.5 Main Modules....................................................................................................................... 15
1.6 Tools and Technology......................................................................................................... 16
1.6.1 Front-End Tools.................................................................................................................... 16
1.6.2 Back-End Tools .....................................................................................................................16
1.6.2 Project TimeLine: .................................................................................................................16
Chapter 2 REQUIREMENT ANALYSIS ..................................................................................17
2.1 Requirement Analysis.................................................................................................... 18
2.1.1 Functional Requirements ............................................................................................18

2.1.2 Non- Functional Requirements ....................................................................................18
CHAPTER 3 LITERATURE REVIEW.......................................................................................20
3.1 Graphical User Interface.................................................................................................21
3.2 Cascading Style Sheets....................................................................................................21
3.3 SQL Server Database: .....................................................................................................22
3.3.1 Enterprise Edition...........................................................................................................23

3.3.2 Standard Edition Edition...............................................................................................23
3.3.3 Business intelligence edition.......................................................................................24
3.3.4 Feature of Microsoft SQL..............................................................................................25
3.4 Sublime text ....................................................................................................................27
3.5 The Waterfall Model .......................................................................................................27
3.5.1 Advantages and Disadvantages ....................................................................................29

3.6 Incremental Model.......................................................................................................... 30
3.7 Agile …............................................................................................................................. 31
3.8 Connectivity and Database Set-up.................................................................................32
CHAPTER 4 METHODOLIGIES ...........................................................................................33
4.1 Proposed System ..............................................................................................................34
4.2 Software requirement system.........................................................................................34
4.3 Software Tool ...................................................................................................................33
4.4 Programming Language ..............................................................................................35

CHAPTER 5 DESIGNING .........................................................................................................37
5.1 UML Diagrams ...............................................................................................................38
5.2 Activity diagrams ............................................................................................................39
5.3 DATA FLOW DIAGRAM..................................................................................................39
5.4 Sequence Diagram (Administrator)…..........................................................................40
5.5 Activity Diagram….........................................................................................................42
5.5.1 Login .................................................................................................................................... 42
5.5.2 Password Recovery............................................................................................................ 42
5.5.3 Administrator Setup Profile......................................................................................... 43
5.5.4 Job Plans: .......................................................................................................................44
5.5.5 Administrator Logout ...................................................................................................... 44
5.5.6 Entity-Relationship Diagram........................................................................................45
5.5.7 Component Diagram ......................................................................................................46
CHAPTER 6 CODING .................................................................................................................47
6.1 LOGIN................................................................................................................................ 48
6.2 Home Page ..................................................................................................................... 49
6.3 ADD New JOB PLAN ......................................................................................................49
6.4 SEARCH ..........................................................................................................................50
6.5 Code................................................................................................................................51

CHAPTER 7 SYSTEM TESTING ........................................................................................54
7.1 Introduction ...........................................................................................................................55
7.1.1 Objectives .............................................................................................................................. 55
7.1.2 Scope ........................................................................................................................................55
7.1.3 Approach .................................................................................................................................55
7.2 Types of Testing ..................................................................................................................56
7.2.1 Unit Testing ............................................................................................................................56
7.2.2 Integration Testing ...............................................................................................................56
7.2.3 Validation Testing ................................................................................................................56
7.2.4 Verification Testing..............................................................................................................56
7.2.5 User Acceptance Testing ...............................................................................................56
Chapter 8 Conclusion ..............................................................................................................58
8.1 Conclusion ...........................................................................................................................59
8.2 Future Work ........................................................................................................................60
CHAPTER 9 References ...............................................................................................................61
9.1 Reference ..............................................................................................................................63
Appendix A – User Feedback Form ........................................................................................ 64

CHAPTER #1
INTRODUCTION

1.1 Introduction
“Human resource management is the process of determining manpower requirements
and the means for meeting those requirements in order to carry out the integrated plan
of the organization”.
Human resource management is the process including forecasting, developing and
controlling by which a firm ensures that it has the right number of people and the right
kind of people at the right places, at the right time doing work for which they are
economically most useful.
Human resources are regarded as the only dynamic factor of production. Other factors
like materials, methods, machines, money etc. are useless without their effective use by
the human resources. Thus, it is logical that there should be proper manpower or
human resource planning in the organization to use the other resources effectively.
Human resource planning is an integrated approach to performing the planning aspects
of the personnel function in order to have a sufficient supply of adequately developed
and motivated people to perform the duties and tasks required to meet organizational
objectives and satisfy the individual needs and goals of organizational members.
1.2 Problem in Existing System
Currently different organization has Manual system to maintain their records, which
requires a lot of time and waste of resources. By using manual system,
managing/planning/forecasting human and other resources is a big challenge. In
manual system manpower is not proper managed/planned/forecast and sometimes
becomes more hectic as it has a big impact to take appropriate or right decision at right
time. In this way organization performance is badly affected to compete with the
competitors.

1.3 Proposed System
This application has a two-phased process because manpower planning not

only analyses the current human resources but also makes manpower
forecasts and thereby draw employment programs. Resources planning is
advantageous to firm in following manner:
• Shortages and surpluses can be identified so that quick action can be

taken wherever required.
• All the recruitment and selection programs are based on manpower

planning.
• It helps the organization to realize the importance of manpower

management which ultimately helps in the stability of a concern.
1.4 SCOPE OF HUMAN RESOURSE MANGMENT

HRMS means determining the number and kind of personnel required to
fill various positions in the organizations.
• To make the list of current manpower.

• To check how much current manpower is being utilized.
• To find out how much manpower is required.
• Recruitment, selection, placement of personnel.
1.5 Main Modules

Cover main modules are:
• Analysing the current human resource inventory
• Making future manpower forecasts
• Developing employment programs

1.6 Tools and Technology
1.6.1 Front-End Tools
• HTML
• CSS
1.6.2 Back-End Tools
• SQL
• bootstrap
• php
• Java Script
• C#

CHAPTER 2
REQUIREMENT ANALYSIS

2.1 Requirement Analysis
A software requirements specification (SRS) completely describes the behaviour
of the system that is to be developed. It documents all necessary requirements of the
system.
A Software requirements specification (SRS), a requirements specification for a
software system, is a complete description of the behaviour of a system to be developed
and may include a set of use cases that describe interactions the users will have with the
software. In addition it also contains non-functional requirements. Non-functional
requirements impose constraints on the design or implementation (such as performance
engineering requirements, quality standards, or design constraints).
2.1.1 Functional Requirements

List all functional requirements of proposed system
Registration
Administrator has right to register by entering name, email id, address, phone
number and password user can easily registered.
Manage Login
By entering username and password Administrator can be login.
Roles Management
After registration different authorized users have different roles according to
their types
Manage Resources Inventory
Analysing the current manpower inventory
Making future manpower forecasts
The Manpower forecasting done by expert forecast, work load analysis, work
force analysis.
Developing employment programs
This will include recruitment, selection procedures and placement plans
2.1.2 Non- Functional Requirements
List all non-functional requirements of proposed system

Efficiency
Efficiency of any system is concerned with the minimum processing time as ill as the
optimal use of system resources in designing the proposed system; the efficiency factor
has been taken ill into consideration as online job portal system provides efficient inputs
with less resources.
Graphical User Interface
The interface of the system is designed and developed keeping in view that it
should be user friendly. Site will be fascinating as well as easy in usage. User friendly
interface.
Reliability Requirements
Reliability of this platform is very important in day-to-day operations. The end-users
who work with this platform must be able to trust on this system.
Accuracy
The system will provide accurate and error free information needed for the
decision-making. It will ensure efficient and accurate record keeping.
Data Security
The data required for decision-making is highly sensitive by and valuable,
therefore, reliability of the proposed system is secured by giving a regular and
guaranteed service to the user.

CHAPTER 3
LITERATURE REVIEW

3.1 GRAPHICAL USER INTERFACE:
HTML or Hyper Text Mark-up Language is the main mark-up language for creating
web pages and other information that can be displayed in a web browser. HTML is
written in the form of HTML elements consisting of tags enclosed in angle brackets (like
<html>), within the web page content.
HTML tags most commonly come in pairs like <h1> and </h1>, although some tags
represent empty elements and so are unpaired, for example <img>. The first tag in a pair
is the stars tag, and the second tag is the end tags (they are also called opening tags and
closing tags). In between these tags web designers can add text, further tags, comments
and other types of text-based content. The purpose of a web browser is to read HTML
documents and compose them into visible or audible web pages. The browser does not
display the HTML tags, but uses the tags to interpret the content of the page.
HTML elements form the building blocks of all websites. HTML allows images and
objects to be embedded and can be used to create interactive forms. It provides a means
to create structured documents by denoting structural semantics for text such as
headings, paragraphs, lists, links, quotes and other items. It can embed scripts written in
languages such as JavaScript which affect the behaviour of HTML web pages.
Html is a hypertext mark-up language that is understandable by the web browsers the
data while traveling in the network basically encrypted to avoid the future loss or
damage of the data so, the data is encrypted.
3.2 Cascading Style Sheets
Cascading Style Sheets (CSS) is a style sheet language used for describing the look and
formatting of a document written in a markup language. While most often used to style
web pages and interfaces written in HTML and XHTML, the language can be applied
to any kind of XML document, including plain XML, SVG and XUL.
CSS is designed primarily to enable the separation of document content from document
presentation, including elements such as the layout, colors, and fonts. This separation

can improve content accessibility, provide more flexibility and control in the
specification of presentation characteristics, enable multiple pages to share formatting,
and reduce complexity and repetition in the structural content (such as by allowing for
stableness).
CSS can also allow the same mark-up page to be presented in different styles for
different rendering methods, such as on-screen, in print, by voice (when read out by a
speech-based browser or screen reader) and on Braille-based, tactile devices. It can also
be used to allow the web page to display differently depending on the screen size or
device on which it is being viewed. While the author of a document typically links that
document to a CSS file, readers can use a different style sheet, perhaps one on their own
computer, to override the one the author has specified. However if the author or the
reader did not link the document to a specific style sheet the default style of the browser
will be applied.
CSS specifies a priority scheme to determine which style rules apply if more than one
rule matches against a particular element. In this so-called cascade, priorities or weights
are calculated and assigned to rules, so that the results are predictable.
3.3 SQL Server Database:
Microsoft SQL Server is an application used to create computer databases for the
Microsoft Windows family of server operating systems. Microsoft SQL Server provides
an environment used to generate databases that can be accessed from workstations, the
Internet, or other media such as a personal digital assistant
(PDA)Top Features of SQL Server 2012.
SQL Server 2012 is obtainable in three main editions. All three
editions have tighter alignment than their predecessors and
were designed to meet the needs of almost any customer with
an increased investment in business intelligence. Each edition
comes in a 32-bit and 64-bit version.
The main editions, as shown in Figure 1-7, are the following:

■ Standard edition
■ Business Intelligence edition
■ Enterprise edition
3.3.1 Enterprise Edition:
The Enterprise edition of SQL Server 2012 is the uppermost SKU; it is meant to meet the
highest demands of large-scale data centres and data warehouse solutions by providing
mission-critical performance and availability for Tier 1 applications, the ability to
deploy private-cloud, highly virtualized environments, and large centralized or
external-facing business-intelligence solutions.
The Enterprise edition features include the following:
■ Maximum number of cores is subject to the operating system being used
■ Advanced high availability can be achieved with Always On
■ Unlimited virtualization if the organization has software insurance
■ Support for the new column store indexing feature
■ Advanced auditing
■ Transparent Data Encryption (TDE)
■ Compression and partitioning
■ includes all of the Business Intelligence edition’s features and capabilities:
■ Reporting
■ Analytics
■ Multidimensional BI semantic model
■ Data-quality services
■ Master data services
■ In-memory tabular BI semantic model
■ Self-service business intelligence
3.3.2 Standard Edition:
The Standard edition is a data-management platform tailored toward departmental
databases and limited business-intelligence applications that are typically appropriate
for medium-class solutions, smaller organizations, or departmental solutions. It does

not include all the bells and whistles of the Enterprise and Business Intelligence
editions; however, it continues to offer best-in-class manageability and ease of use.
Compared to the Enterprise and Business Intelligence editions, the Standard edition
supports up to 16 cores and includes the following:
■ Spatial support
■ File Table
■ Policy-based management
■ Corporate business intelligence
■ Reporting
■ Analytics
■ Basic high availability can be achieved with Always On 2-Node Failover Clustering ■
Up to four processors, up to 64 GB of RAM, one virtual machine, and two failover
clustering nodes.
3.3.3 Business Intelligence Edition:
For the first time in the history of SQL Server, a Business Intelligence edition is offered.
The Business Intelligence edition offers organizations the full suite of powerful BI
capabilities such as scalable reporting and analytics, Power View, and Power Pivot. It is
tailored toward organizations trying to achieve corporate business intelligence and self
service capabilities, but that do not require the full online transactional processing
(OLTP) performance and scalability found in the Enterprise edition of SQL Server 2012.
Here is a high-level list of what the new Business Intelligence edition includes:
■ Up to a maximum of 16 cores for the Database Engine
■ Maximum number of cores for business intelligence processing
■ All of the features found in the Standard edition
■ Corporate business intelligence
■ Reporting
■ Analytics
■ Self-service capabilities

■ Alerting
■ Power View
■ PowerPivot for SharePoint Server
■ Enterprise data management
■ Data quality services
■ Master data services
■ In-memory tabular BI semantic model
■ Basic high availability can be achieved with Always On 2-Node Failover Clustering
3.3.4 FEATURES OF Microsoft SQL
Contained databases
Before the introduction of SQL Server 2012, when you moved or restored databases
from one instance of a SQL Server database engine to another, any server logins
associated with database users were not copied to the target instance automatically.
This left you with orphaned users and a database that would not work immediately
after migration. In order to get the database to function, you had to create and map
server logins associated with the database users in the target instance. Obviously, this
made the database less portable because database security depends on the instance of
the SQL Server database engine where the database is installed.
SQL Server 2012 addressed this problem with the introduction of contained database
authentication, which allows users to authenticate their database without having a login
on the instance of the SQL Server database engine where the database is installed. A
contained database can be moved easily between instances of SQL Server. It stores all
the settings and metadata required to define the database and has no configuration
dependencies on the instance of SQL Server where the database is installed. A contained
database is also isolated from other databases hosted on the same SQL Server instance.
It supports two types of users: SQL users with passwords and Windows Principal
without Login. Both types of users do not need to login in the master database. These
features make a SQL Server 2012 database much more portable than previous versions.

Always On Availability Groups
SQL Server 2012 introduced Always on Availability Groups, which enhances and
combines database mirroring and log shipping capabilities. It is a high availability and
disaster recovery solution for SQL Server databases that provides an enterprise-level
alternative to database mirroring. An availability group supports a primary database
and from one to four sets of corresponding secondary databases. These secondary
databases can be made available for read-only access or some backup operations.
File Tables
SQL Server 2012 introduces File Tables, which let you store files and directories in a
special table that builds on top of SQL Server FILESTREAM technology. A File Table
has a fixed schema, with each row representing a file or a directory. The main
advantage of File Table is that it supports Win32 APIs for file or directory management.
This means you can access file and directory hierarchy through a Windows Share and
database storage is transparent to a Win32 application. Files can be bulk loaded,
updated and managed in T-SQL like any other column. SQL Server 2012 also supports
backup and restore jobs for this feature.
User-defined server roles
SQL Server 2012 introduces user-defined server roles, which are similar to fixed server
roles. The only difference is that they are created by a SQL Server administrator. SQL
administrators can create, delete or manage these user-defined server roles using T-SQL
or SQL Server Management Studio. The main advantage of user-defined roles is that
they authorize user access based on job responsibilities.
Default schema for Windows Groups
Before SQL Server 2012 was introduced, you could not specify the default schema for
Windows Groups. As a result, when a user with access through Windows group
membership created database objects such as a table or view inside a database, SQL
Server automatically created a separate user (mapped to the Active Directory account),

and a schema with the same name in the database. Because of this security
manageability issue, databases included hundreds of users and schemas, which is a
managerial nightmare for database administrators. Hence, the SQL Server community
requested a fix for this security manageability issue via the Microsoft Connect site.
SQL Server 2012 addresses this security issue by allowing you to assign default schema
for Windows Groups, which helps organizations simplify database schema
administration.
3.4 Sublime text 03:
This information is useful for programmers. Other users just need to know that
Sublime Text enables users with programming skills to add their own features to the editor.
Sublime Text exposes its internals via an Application Programming Interface (API)
that programmers can interact with using the Python programming language.
An embedded Python interpreter is included in the editor.
The embedded interpreter is useful to inspect the editor’s settings
and to quickly test API calls while developing plugins.
Sublime Text and plugins output information to a console.
To open the console, press Ctrl+` or select View → Show Console from the main menu.
Sublime Syntax files are YAML files with a small header, followed by a list of contexts.
Each context has a list of patterns that describe how to highlight text in that context, and
how to change the current text.
3.5 The Waterfall Model

The most important aspect of the waterfall model is that unless a particular stage is
complete, the next stage cannot be started off with. Here, in this article, we will try to

understand a simple waterfall model, broken into six stages. Let us try to understand
each of these stages one by one.
Stage 1: Requirement Phase
Whether you design a small program to add two numbers or you are into developing a
software system for the automation of an entire airline company, this is the first stage
which can never be overridden. Unless you know what you are going to design, you
cannot approach the problem. Here, the specifications of the output or the final product
are studied and marked.
Stage 2: Specification Phase
With all the requirements and constraints in hand, a final view of how the product
should exactly be, is decided. The exact way in which the software should function is
mentioned in this stage.
Stage 3: Design Phase
Here the actual work begins. Every type of resource which will be required for the
smooth designing of the software, is mentioned here in this phase. What type of
database will be required, what type of data should be supported, etc. are some of the
important aspects that are decided in this phase. The algorithm of the process in which
the software needs to be designed, is made in this phase. This algorithm forms the
backbone for the actual coding process that takes place in the next phase.
Stage 4: Implementation and Testing Phase
Now starts the coding. Here, the software is coded as per the algorithm. Hence it
becomes very important that the algorithm should be properly designed. The software
designed, needs to go through constant software testing and error correction processes
to find out if there are any flaw or errors.
Stage 5: Integration and Testing Phase
Here the various codes designed by different programmers are integrated and is tested
if the software works as per the specifications provided. The setup of the final software
which needs to be installed at the clients system, is also designed and tested, so that the
client does not face any problem during the installation of the software. The product is
then handed over to the client

Stage 6: Maintenance Phase
The cycle of software development does not end with handing the software to the client.
Software designers may have to constantly provide support to the client to resolve any
issues which may arise. During the maintenance phase, support and debugging is
provided for all such problems.
Fig 3.2 Waterfall Model
3.5.1 Advantages and Disadvantages

Advantages
The waterfall model is the oldest and most widely used model in the field of software
development. There are certain advantages of this model, which makes it, one of the
most widely used models as yet. Some of them are:
• Being a linear model, it is very simple to implement.

• The amount of resources required to implement this model are minimal.
Documentation is produced at every stage of the software's development. This
makes understanding the product designing procedure, simpler.

• After every major stage of software coding, testing is done to check the correct
running of the code.
Disadvantages
The question that must be bothering you now is that with so many advantages at hand,
what could be the possible disadvantages of the waterfall model? Here are a few:
Ironically, the biggest disadvantage is one of its greatest advantages. You cannot go
back a step; if the design phase has gone wrong, things can get very complicated in the
implementation phase.
Often, the client is not very clear of what he exactly wants from the software. Any
changes that he mentions in between may cause a lot of confusion.
Small changes or errors that arise in the completed software may cause a lot of
problems.
Until the final stage of the development cycle is complete, a working model of the
software does not lie in the hands of the client. Thus, he is hardly in a position to inform
the developers, if what has been designed is exactly what he had asked for. So this, in
short, was all about waterfall model advantages and disadvantages. In spite of the cons,
the many pros of this model ensure that it remains one of the most popular models used
in the field of software development.
3.6 Incremental Model
Project functionality is delivering in increment. After each increment is delivered to the

customer their feedback is used to improve further increment. The whole requirement is
divided into various builds. Multiple development cycles take place here, making the
life cycle a “multi-waterfall” cycle.
Cycles are divided up into smaller, more easily managed modules. Each module passes
through the requirements, design, implementation and testing phases. A working
version of software is produced during the first module, so you have working software
early on during the software life cycle. Each subsequent release of the module adds
function to the previous release. The process continues till the complete system is
achieved.

The diagram below, courtesy of
Microsoft's MSF, clearly shows
how iterations are scheduled and
Fig 3.3 Incremental Model
delivered:
Fig 3.4: Software Development Life Cycle
3.7 Agile
Agile methodologies arose from the need to develop software applications that could
accommodate the fast-paced evolution of the Internet. Agile is, in some way, a variant
of iterative life cycle where deliverables are submitted in stages. The main difference is
that agile cuts delivery time from months to weeks. Companies practicing agile are
delivering software products and enhancements in weeks rather than in months.
Moreover, the agile manifesto covered development concepts aside from the delivery
life cycle, such as collaboration, documentation, and others. The diagram from
Microsoft MSF shows the various components of an agile life cycle:

Fig 3.5 SDLC
3.9 Connectivity and Database Set-up
In the present project we are connecting to SQL Server 2012. In order to connect to a
back end Database from PHP, we need to check connection for SQL Server 2012.
• This is clearly demonstrated in the fig below. PHP allows the following sources
of data to be accessed and used: Databases (e.g., Access, SQL Server, Oracle,
MySQL) XML ,documents Business Objects ,Flat files

CHAPTER# 4 METHODOLIGIES

This chapter includes technical requirements and specifications for proposed
Solution divided into various sections in order to explain pre-required data,
Technology specifications, users interface, backend technologies, development
Environment tools specifications etc.
4.1 Proposed System

After study of manual system a new system is built that can solve various
Problems in manual system
This proposed solution is computerized solution to the problem faced in the
Entry of visitors in organizations.
4.2 Software requirements specifications:
Front End
HTML, CSS, BOOTSTRAP, JQUERY, JavaScript
Back End
PHP, My SQL Database Management System
4.3 Software tools
XAMPP
Sublime Text 3
PHP My Admin
The database management tool used in this project was PhpMyAdmin.
It is an open source tool written in PHP. It realized the web database management
Instead of the traditional system implementation.
Sublime Text 3
It is code editor tool used with variety of feature like auto tags and
various PHP and html tag completion facility. It also enable to explore project by
using side bar. It work on PHP and used to design layout of website as well as PHP
coding for database connection
MY SQL
My SQL is a relational database Management system (RDBMS) that runs as a server
providing multi-user access to a number of databases. MySQL was designed for three

principles which are performance, reliability and usability. A Cheap distinctive
fast and efficient RDBMS was created by following those principles MySQL becomes
perfect tool for developers and administrators to establish maintain and configure
complex applications
4.4 Programming languages
The programming languages used for this project are HTML, PHP, CSS,
Boot Strap to design layout and connect with database server. Bootstrap mainly used
for the responsiveness of the system.
HTML is basically used as the base for the webpage. It actually creates the basic layout
of the webpage with the addition of CSS, JavaScript. Boot strap, PHP and J Query
quality of page can be improved and also page become responsive by the use of
Bootstrap means page can be view on small screens properly like Tablet, Smart Phone etc
Hard ware and software requirements
Hardware interface
Server side
 Processor minimum Pentium 4.0 or higher
 RAM minimum 512 KB
 Hard Drive 10 GB or more
Client side
 Operating System XP, WIN 7, 8 or higher
 Processor Pentium 4.0 or higher
 RAM minimum 512 KB
Software interface
Server side
XAMPP Server
Client Side
HTML
Web Browser
Communication interface
The costumer must connect to the internet to access the website

Dialup modem of 52 Kbps
Broadband Internet
Dialup or Broadband Connection with a Internet Provider.
UML Diagram Specification
UML stands for Unified Modeling Language that can be used to model an application
structures, behavior and even business processes. There are 14 UML diagram they can be
divided into tow main categories : structure diagram and behavioral diagrams.
Following UML Diagrams are used to expose the proposed system Design.
 Use Case Diagram
 Data flow diagram
 Entity Relationship Diagram
 System Architecture Diagram

Database Development Language
SQL is standard language for accessing and manipulating databases. SQL
stands for structured Query Language lets you access and manipulate databases. SQL
language provides simple clauses like ‘Select’. ‘Where”, “Insert Into”, “Update” and
“Delete” for query building in order to manipulate the database of connected server.
Some back Queries areas under for reference which I used in my Visitor Management
System for insertion of Data and updating of Database with sublime text 3.

CHAPTER# 5
DESIGNING

5.1 UML Diagrams
UML is not a methodology; it does not require any formal work products.
Yet it does provide several types of diagrams that, when used within a given
methodology, increase the ease of understanding an application under
development. There is more to UML than these diagrams, but for my purposes
here, the diagrams offer a good introduction to the language and the principles
behind its use. By placing standard UML diagrams in your methodology's work
products, you make it easier for UML-proficient people to join your project and
quickly become productive. The most useful, standard UML diagrams are: use
case diagram, class diagram, sequence diagram, state chart diagram, activity
diagram, component diagram, and deployment diagram.
Use case Diagrams
Use case illustrates a unit of functionality provided by the system. The
main purpose of the use-case diagram is to help development teams visualize the
functional requirements of a system, including the relationship of "actors"
(human beings who will interact with the system) to essential processes, as well
as the relationships among different use cases.
Sequence diagrams
Sequence diagrams show a detailed flow for a specific use case or even just
part of a specific use case. They are almost self-explanatory; they show the calls
between the different objects in their sequence and can show, at a detailed level,
different calls to different objects. A sequence diagram has two dimensions: The
vertical dimension shows the sequence of messages/calls in the time order that
they occur; the horizontal dimension shows the object instances to which the
messages are sent.

5.2 Activity diagrams
Activity diagrams show the procedural flow of control between two or
more class objects while processing an activity. Activity diagrams can be used to
model higher-level business process at the business unit level, or to model low
level internal class actions. In my experience, activity diagrams are best used to
model higher-level processes, such as how the company is currently doing
business, or how it would like to do business. This is because activity diagrams
are "less technical" in appearance, compared to sequence diagrams, and business
minded people tend to understand them more quickly.
An entity-relationship diagram (ERD) is a data modelling technique that
graphically illustrates an information system’s entities and the relationships
between those entities. An ERD is a conceptual and representational model of
data used to represent the entity framework infrastructure.
5.3 DATA FLOW DIAGRAM

The data flow diagram is one of the most improvement tools used by the system
analyst DeMacro (1978) Nad Gand Sarson (1979) popularized the use if the data flow
diagram as modelling tools through their structured system analysis methodologies.
A data flow diagram should be the first tool used by system analyst to model system
components. These components are the system processes; the data used by this
processes and external entities that interact with the system and the information flows
in the system.
There are four kinds of system components
Process
Process show what system does. Each process has one or more data inputs and
produce one or more data output, Circles in a data flow diagram represent process.
Each process has unique name and number. This name and number appear inside the
circle that represents the processes in a data flow diagram.
This process is represented as circle

Data Stores
File or data store is depositary of data. They contain data that is retained in the system.
Processes can enter the data into a data store or retrieve data from the data store. Each
data store is represented by thin line in the data flow diagram and each data store has a
unique name.
The data store is represented in form of a line
External Entities
External entities are outside the system but they either supply input data into the
system or use the system output, they are entities which the designer has no control.
Square or rectangle may represent external entities that supply data into a system or
sometimes called sources. External entities that use the system data are sometimes
called sinks.
Data Flows
Dataflow model the passage of data in the system and are represented lines joining
system components. An arrow indicates the direction of the flow and the line labeled
by the name of the data flow.

5.4 Sequence Diagram (Administrator):

5.5 Activity Diagram:
The following are the activity diagrams
5.5.1 Login
5.5.2 Password Recovery

5.5.3 Administrator Setup Profile
Click On Setup
Department
Section
Sub-Section
Position
Position Type
Work Category
Location
SPS

5.5.4 Job Plans
Click On Job Plans
New Emp
Search Emp
By Dept
By Section
By Position
5.5.5 Administrator Logout
Click Logout
Admin Must Logout

5.6 Entity-Relationship Diagram

5.7 Component Diagram
SQL Server
Database
User
Interface
5.8 Use Case Diagram
Log in
Department
Work
Section Category
Set UP SPS
Sub-Section
Position Type
Position
Location
Admin
( MMP ) Add Emp
By Dept
Job Plans
Search By Section
Emp
By
Position
Log Out

CHAPTER# 6
CODING AND DESIGN

6.1 SCREEN SHOTS
6. 1 LOGIN

6. 2 Home Page
6. 3 ADD New JOB PLAN

6. 4 SEARCH
6.5 CODE
<?php
session_start();
include_once 'dbconnect.php';
if(!isset($_SESSION['user']))
{
header("Location: index.php");
}
$res=mysql_query("SELECT * FROM login WHERE user_id=".$_SESSION['user']);
$userRow=mysql_fetch_array($res);
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Welcome - <?php echo $userRow['user_email']; ?></title>
<link rel="stylesheet" href="style.css" type="text/css" />
</head>
<body>
<div id="header">
<div id="left">
<label>Coding Cage</label>
</div>
<div id="right">
<div id="content">
hi' <?php echo $userRow['user_name']; ?> <a href="logout.php?logout">
Sign Out</a>
</div>
</div>
</div>
<div id="body">
<a href="http://www.codingcage.com/">Coding Cage - Programming Blog</a><br /><br />
<p>Focuses on PHP, MySQL, Ajax, jQuery, Web Design and more...</p>
</div>
</body>
</html>
<?php
session_start();
include_once 'dbconnect.php';
if(isset($_SESSION['user'])!="")
{

header("Location: ../dashboard.php");
}
if(isset($_POST['btn-login']))
{
$email = mysql_real_escape_string($_POST['email']);
$upass = mysql_real_escape_string($_POST['pass']);
$email = trim($email);
$upass = trim($upass);
$res=mysql_query("SELECT user_id, user_name, user_pas FROM login
WHERE user_name='$email'");
$row=mysql_fetch_array($res);
$count = mysql_num_rows($res); // if uname/pass correct it returns must be 1 row
if($count == 1)
{
$_SESSION['user'] = $row['user_id'];
header("Location: home.php");
}
else
{
?>
<script>alert('Username / Password Seems Wrong !');</script>
<?php
}
}
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Coding Cage - Login & Registration System</title>
<link rel="stylesheet" href="style.css" type="text/css" />
</head>
<body>
<center>
<div id="login-form">
<form method="post">
<table align="center" width="30%" border="0">
<tr>
<td><input type="text" name="email" placeholder="Your Email" required /></td>
</tr>
<tr>
<td><input type="password" name="pass" placeholder="Your Password" required /></td>
</tr>
<tr>
<td><button type="submit" name="btn-login">Sign In</button></td>
</tr>
<tr>
<td><a href="register.php">Sign Up Here</a></td>
</tr>
</table>
</form>
</div>
</center>
</body>
</html>
Note: Complete Code is in Attached CD

CHAPTER# 7
SYSTEM TESTING

7.1 Introduction
System testing involves user training system testing and successful running of
the developed proposed system. The user tests the developed system and changes are
made according to their needs. The testing phase involves the testing of developed
system using various kinds of data.
An elaborate testing of data is prepared and the system is tested using the test
data. While testing, errors are noted and the corrections are made. The corrections are
also noted for the future use. The users are trained to operate the developed system.
7.1.1 Objectives
The following system test plan for the “User behaviour Monitoring System” will
support the following objectives: o Identify the features of the project that need to be
tested.
 Define the testing approaches that will be used during testing.
 Define the pass/fail criteria for each item that would be tested.
 Define the suspension criteria and resumption technique for the same.
 Finally identify the deliverables of the testing process.
7.1.2 Scope
The document “System Testing” will cover all the items that need to be tested and all
the test approaches involved. It will also define the pass/fail criteria for each of the
items
7.1.3 Approach
System testing is the stage of implementation that is aimed at ensuring that the
system works accurately and efficiently before live operation commences. Testing is

vital to the success of the system. System testing makes logical assumption that if all the
parts of the system are correct, then the goal will be successfully achieved. A series of
testing are done for the proposed system before the system is ready for the user
acceptance testing.
7.2 The following are the types of Testing
1. Unit Testing
2. Integration Testing
3. Validation Testing
4. Verification testing
5. User acceptance testing
7.2.1 Unit Testing

Unit testing focuses verification efforts on the smallest unit of the software
design, the module. This is also known as “module testing”. The modules are tested
separately. This testing was carried out during programming stage itself. In this testing
each module is found to be working satisfactorily as regards to the expected output
from the module.
7.2.2 Integration Testing
Data can be lost across an interface: one module can have adverse efforts on
another. Integration testing is the systematic testing for construction of program
structure, while at the same time conducting tests to uncover errors associated within
the interface. Here correction is difficult because the isolation of cause is complicated by
the cast expense of the entire program. Thus in the integration testing step, all the errors
uncovered are corrected for the next testing steps.
7.2.3 Validation Testing

At the conclusion of integration testing, software is completely assembled as a
package, interfacing errors have been uncovered and corrected and a final series of

software tests begins validation test has been conducted one of the two possible
conditions exists. One is the function or performance characteristics confirm to
specification and are accepted and the other is deviation from specification is uncovered
and a deficiency list is created.
7.2.4 Verification Testing

Verification is a fundamental concept in software design. This is the bridge
between customer requirements and an implementation that satisfies those
requirements.
This is verifiable if it can be demonstrated that the testing will result in an
implementation that satisfies the customer requirements.
Inadequate testing or non-testing leads to errors that may appear few months
later. This will create two problems
 Time delay between the cause and appearance of the problem.
 The effect of the system errors on files and records within the system.
7.2.5 User Acceptance Testing

User acceptance testing of a system is the key factor of the success of any system.
The system under study is tested for the user acceptance by constantly keeping in touch
with the prospective system users at any time of developing and making changes
whenever required.

CHAPTER# 8
CONCLUSION AND FUTURE PLANS

8.1 CONCLUSION
It is concluded that the application works well and satisfy the company and
students. The application is tested very well and errors are properly debugged. The site
is simultaneously accessed from more than one system. Simultaneous login from more
than one place is tested.
The site works according to the restrictions provided in their respective browsers.
Further enhancements can be made to the application, so that the web site functions
very interactive and useful to existing application .The application satisfies both the
company and students by eliminating more input. The speed of the transactions become
more enough now.
I had a very good interaction with our internal supervisor, Mr Umar Aziz Rana
Sahib who helped me to develop the system ill in time. During the development of the
project. I have achieved the following benefits.
Project management and scheduling.
How to interact with the user.
System analysis and data collection.
A good knowledge of system designing and modelling.
Latest tools and technologies.
Testing strategies.
User documentation.
During the modelling phase I learnt.

8.2 FUTURE WORK
Every application has its own merits and demerits. The project has covered
almost all the requirements. Further requirements and improvements can easily be done
since the coding is mainly structured or modular in nature. Changing the existing
modules or adding new modules can append improvements. Further enhancements can
be made to the application, so that the web site functions very attractive and useful
manner than the present one

CHAPTER# 9
REFERENCES

9.1 REFERENCES
 http://en.wikipedia.org/wiki/
 Requirements Analysis
 http://en.wikipedia.org/wiki/Requirements_analysis
 SDLC Study
 http://en.wikipedia.org/wiki/Systems_Development_Life_Cycle
 Waterfall Model
 http://en.wikipedia.org/wiki/Waterfall_model
 http://en.wikipedia.org/wiki/IText
 Software Testing
 http://en.wikipedia.org/wiki/Software_testing
 Software Testing Help
 http://www.softwaretestinghelp.com/web-application-testing/
 Architecture of Php
 http://www.Php.net/manual/en/Mysqli.overview.Php
 http://msdn.microsoft.com/en-us/library/ms174173.aspx
 Introducing SQL Server Management Studio
 http://msdn.microsoft.com/en-us/library/ms174173.aspx
 2-tierArchitecture
 http://www.unmedu.com
 www.google.com

 www.w3schools.com
 http://msdn.microsoft.com/en-us/vstudio/hh341490.aspx
 http://www.thaicreate.com/
 www.tutorialspoint.com/asp.net/asp.net_database_access.htm
 http://www.techonthenet.com/sql/index.Php
 www.wikipedia.org/wiki/Microsoft_Visual_Studio
 http://www.davidchappell.com/writing/white_papers/Introducing_Visual_St
udio_2010_v1.0--Chappell.pdf
 www.blogs.msdn.microsoft.com/bethmassi/2012/04/19/working-with-sqlserver-localdb-in-
lightswitch-projects-in-visual-studio-2012/

Appendix A – User Feedback Form
Date: __________
Dear User,
I would appreciate it if you would take a few minutes to answer the questions below
regarding how this Software is going so far from your perspective. Please be as specific
as possible. I need to know what I am doing well, so I can keep doing it and also what
could be done for improvement. Your comments will be used to improve the Software
in future.
Thank you!
• Which aspects of my Software have you found to be the most useful to you so
far?
• Has anything in this software stalled your parking experience? If yes, please
explain and suggest what might be done differently.
• Has this software helped you and cover your requirements?
• Do you have any other suggestions?

Human Resourse Management

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Human Resourse Management

Diunggah oleh

Hak Cipta:

Format Tersedia

FINAL YEAR PROJECT PROPOSAL

HUMAN RESOURSE MANAGEMENT SYSTEM

PRESTON UNIVERSITY - ISLAMABAD CAMPUS

ABDUL BASIT (REG # 1442-416024) Page 1

This is to certify that the project titled “HUMAN RESOURSE MANGMENT

It is our judgment that this project is of sufficient standard to warrant its

1. External Examiner ________________________________

2. Internal Examiner ________________________________

4. Head of Department ________________________________

ABDUL BASIT (REG # 1442-416024) Page 2

I certify that research work titled “HUMAN RESOURSE MANGMENT SYSTEM”

ABDUL BASIT (REG # 1442-416024) Page 3

ABDUL BASIT ………………………………..

ABDUL BASIT (REG # 1442-416024) Page 4

Academic Session : 2016-2018

I declare that this report is classified as:

RESTRICTED Contains restricted information, and may not be copied or circulated

I acknowledge that Preston University reserves the right as follows:

1. The report is the joint property of Preston University and Author.

Signature of Student Signature of Supervisor

ABDUL BASIT (REG # 1442-416024) Page 5

Specially dedicated to my parents for their love, support

ABDUL BASIT (REG # 1442-416024) Page 6

The project Human Resources Management System, HRMS is a web based

ABDUL BASIT (REG # 1442-416024) Page 7

ABDUL BASIT (REG # 1442-416024) Page 8

Project Title : HRMS

Supervised By : Sir Umar Aziz Rana

Date Started : Feb, 2018

Date Completed : June, 2018

Database Server : Xampp

Hardware Used : Computer system, Printer, computer networks

ABDUL BASIT (REG # 1442-416024) Page 9

1.1 Introduction ........................................................................................................................... 14

1.2 Problem in Existing System ............................................................................................14

1.3 Proposed System ..................................................................................................................15

1.4 Scope of Human Recourse Management System.........................................................15

1.5 Main Modules....................................................................................................................... 15

1.6 Tools and Technology......................................................................................................... 16

1.6.1 Front-End Tools.................................................................................................................... 16

1.6.2 Back-End Tools .....................................................................................................................16

1.6.2 Project TimeLine: .................................................................................................................16

Chapter 2 REQUIREMENT ANALYSIS ..................................................................................17

2.1 Requirement Analysis.................................................................................................... 18

2.1.1 Functional Requirements ............................................................................................18

CHAPTER 3 LITERATURE REVIEW.......................................................................................20

3.1 Graphical User Interface.................................................................................................21

3.2 Cascading Style Sheets....................................................................................................21

3.3 SQL Server Database: .....................................................................................................22

3.3.1 Enterprise Edition...........................................................................................................23

3.5 The Waterfall Model .......................................................................................................27

3.5.1 Advantages and Disadvantages ....................................................................................29

ABDUL BASIT (REG # 1442-416024) Page 10

3.7 Agile …............................................................................................................................. 31

3.8 Connectivity and Database Set-up.................................................................................32

CHAPTER 4 METHODOLIGIES ...........................................................................................33

4.1 Proposed System ..............................................................................................................34

4.2 Software requirement system.........................................................................................34

4.3 Software Tool ...................................................................................................................33

4.4 Programming Language ..............................................................................................35

5.1 UML Diagrams ...............................................................................................................38

5.2 Activity diagrams ............................................................................................................39

5.3 DATA FLOW DIAGRAM..................................................................................................39