Upload
engrmuzammaljanjua
View
44
Download
0
Tags:
Embed Size (px)
DESCRIPTION
Human Resrouce Management system is a Final Year Project in which different modules are targeted like 1- Induction2- Employee Detail3- Attendace4- PayrollAll these are handle using RFID
Citation preview
Automated Human Resource Information System
Using
Biometrics and RFID
A ThesisPresented to
The Academic Faculty
by
M.Muzammal Naseer Janjua(1339/FUIMCS/BBSSE-2004)
In Partial Fulfillmentof the Requirements for the DegreeBachelors in Software Engineering
Department Of Software Engineering And Computer ScienceFoundation University Institute of Management & Computer Sciences
October, 6th 2008
Automated Human Resource Information System
Using
Biometrics and RFID
Approved by:
Professor Dr. Tough, Committee Chair
Professor Dr. Genius, Adviser
Professor Anti-Plagiarism
Professor Originality-Checker(Another Department)
Professor Verifier
Asst. Professor Muaz Niazi(Coordinator Senior Design Projects)
Date Approved
Starting With The Name of Allmighty Allah
Who is Mercifull and Beneficial.
To my wonderful parents with Deepest gratitude,
Whose Love,and prayers have
always been a source of stregnth for me
Who have tolerated my excesses,
and guided and nurtured throughout my live.
& To my honorable faculty members
Whom I hope to please with My show of
year-long efforts!
iii
PREFACE
When Something can be Read without effort,
Great effort has gone into writing
Enrique Jardiel poncela
The present time demands from Universities and Researchers to Develop, to think and to
work on according to most modern and demanded Technology . Especially in Computer
Sciences fields, every day a new technology is coming. And every eve is going to off a
technology . It has been identified that Developing Countries progress, their technology ,
and their approaches are far away from the modern world and modern technologies. In the
19s Century it was a quote that
Developing Countries are far away from Developed Countries from 80 to
100 years
Now the time has been changed. World has become global village. The era of is mov-
ing from wired to wireless to reduce the copper burden. With the emerging technologies
communication is becoming faster and faster reducing the time between data transmission.
From placing one file to another place by hand to Bar Code and now moved to Radio Fre-
quencies to remove the need of line of sight bound.The need to change the old manual system
led us in automation of different system,to give reliablity and user friendly envirnoment to
uers.Thats why it was said that
We are becoming the servants in thought, as in action, of the machine we
have created to serve us. John Kenneth Galbraith
The Purposed Project Automated Human Resource Information System Using RFID and
Biometrice is based upon new and most demanded technology that is Radio Frequency and
thumb identification,these technologies are used for automation and authentication.The
iv
AHRIS has a enormous Software which has got many options for the automation of the
system.The detailed project is dicussed later in this report.
Organization and Overview of Chapters
Chapter 1 Introduction :I start by giving an introductory chapter which talks about
entire work in Introduction Chapter. Starting from basic introduction of project to all
desrciption of project,this chapter covers all modules of the project with their benifits and
feutures.It is tried that main scenarios of the project and main theme of the project should
cover in this chapter.
Chapter 2 Background : This chapter give a detail view of the background behind
developing this software and work on this project.The project is for Defence Housing Au-
thority(DHA),so the whole study,survay and drawback of the systems being used by them
are covered in this chapter.Literature view from different existing projects is also included
in this chapter.
Chapter 3 Requirements and Analysis:For developing and working on project it
is needed to have a very good requirment and project analysis using different Software
Engineering cases.Use cases and Flowchart of the use cases with basic system diagram and
association of diagram is covered in this chapter.
Chapter 4 Design :Designing is the core part of the project,as a project of Software
engineering course,it is highly focused to design the project using UML diagrams.As it is
said Pictures Says All or figures speaks more then words.Different designing techniques
are used,like Squence Diagrams,State chart diagrams,class diagram,component diagram etc.
Chapter 5 Implementation :This chapter describe the tools and technologies used
to make this project happen and implemented in reality.chunks of Algorithms are also
discussed to cover the main implementation of modules.
Chapter 6 Testing :Testing is another core part and critical part of the project,it is
highly recommended for the Final year project.Different testing techniques are used to test
AHRIS.
Chapter 7 Conclusion :This chapter is about what is concluded at the end of this
project.What has been delivered and how it is benificial for the industry.
v
ABSTRACT
The ongoing growth of technology has necessitated the use of more simpler and
effective systems as a replacement to the existing ones.World of communication has long
before migrated from wired to wireless so as to minimize the dependency of copper from
the field of communication. RFID and Biometrice developed thereof are the products of
these migration. These devices are easy to install,and maintain.
AHRIS Using Biometrice and RFID Stands for Automated Human Resource Information
System Using Biometrice and RFID device(Case-Study Of DHAi).Its automated Solution
to the manual management Systems which are still in many organizations and departments.
The first rule of any technology used in a business is that automation ap-
plied to an efficient operation will magnify the efficiency. The second is that
automation applied to an inefficient operation will magnify the inefficiency.Bill
Gates
AHRIS is basically integration of management systems,it is not only Human Resource man-
agement System.It has Employee Management System,Electonic Documents Management
System,Payroll Management System and Attendance System.This system will enable the
managers and the teams working on several projects at different sites to keep themselves
well-versed of the updated information.
RFID and Biometrice Devices are used for Authentication and Automation of Attendance
System of Registered Employees.Both Technologies are very much secured and not easy to
hack or break.By using these as hardware, encourage to develope a software which automate
the entries and departure with real time manner.
AHRIS provides functionality of viewing detailed reports of diverse nature. The system
has a number of reports that are developed in Crystal Reports, which gives the better view
of Employeess progress and activities at any stage. The comprehensive reporting system
facilitates in timely and accurate decision making.
vi
ACKNOWLEDGEMENTS
Above all,thankful to Allah, The All Mighty. It was for Him, that
I choose this project and it is Him, who has to reward me for this effort.
To all those who helped us and
contributed for completion of the project,
our sincere gratitude and appreciation with special thanks goes to:
Mr.Abdullah Bin Qadeer
Mr.Mubashir, Telenor Pakistan
for their intellectual supervision and
absolute guidance in solving all problems and difficulties
Dr Aftab Ahmed, Dean and Director
Foundation University Islamabad Pakistan
for his ethical, administrative, highly skilled leadership and
provision of conducive environment in the University
for project accomplishment.
The Faculty of Computer Science and staff at FUIMCS
for cooperation and assistance in this project
My beloved parents who,
through their unparallel support,
love & affection, sacrifices and prayers,
provided comforts and care
for completing this project
To above mentioned and to others whome i may have missed to mention, My sincerest
thanks and acknowledgement.
vii
Abbreviations
Abbreviation MeaningRF Radio FrequencyEDMS Electronic Data Management SystemBM BioMetricsPS Payroll SystemAS Attendance SystemAAS Automated Attendance SystemDFD Data Flow DiagramCFD Control Flow DiagramFUIMCS Foundation University institute of Management&
Computer ScienceHRIS Human Resource Information SystemRFID Radio Frequency idnetification SystemUML Unified Modeling LanguageHR Human ResourceDHA Defence Housing AuthorityDEO Data Entry OperatorVB Visual BasicGUI Graphical User InterfaceDBS DataBase Systemmb MegabyteGb Giga byteVLF Very Low FrequencyOOA Object oriented AnaylsisE-R Entity RelationshipDFD Data Flow DiagramPDM Project Domain ModelAM Analysis ModelSDLC Software Develpoment Life CycleSQA Software Quality AssuranceBLL Buisness Logic LayerULL User Logic LayerDLL Data Logic LayerDAL Data Access Layer
Table 1: Abbreviations
viii
TABLE OF CONTENTS
DEDICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
ABSTRACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
LIST OF TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
LIST OF FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
I INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Project in Breif . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.1 Project Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.2 Project Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.3 Problem Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.4 Supervisors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Literature Review of existing system from some universities . . . . . . . . 3
1.3 Introduction to Organization(DHA) . . . . . . . . . . . . . . . . . . . . . . 5
1.3.1 Projects of Orgranization . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.2 Organizational Chart . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.3 Human Resource System . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 The Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4.1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4.2 Project Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4.3 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.5 Developement Process Model . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.6 Proposed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.6.1 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.6.2 Proposed system benefits . . . . . . . . . . . . . . . . . . . . . . . . 14
1.6.3 Proposed System Features . . . . . . . . . . . . . . . . . . . . . . . 15
1.7 Project Overall Description . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.7.1 Basic System Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 18
ix
1.7.2 System Operational Modules . . . . . . . . . . . . . . . . . . . . . . 18
1.7.3 System Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7.4 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.7.5 Hardware Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.7.6 Software Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.7.7 Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.7.8 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.7.9 Site Adaption Requirment . . . . . . . . . . . . . . . . . . . . . . . 22
1.7.10 User characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.7.11 Software System Attributes . . . . . . . . . . . . . . . . . . . . . . 22
II BACKGROUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.1 Detailed Study of Existing System . . . . . . . . . . . . . . . . . . . . . . . 24
2.2 Survey of the Existing Systems at DHA isb . . . . . . . . . . . . . . . . . 24
2.2.1 Attendance System . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.2 Recruitment System(HR Department) . . . . . . . . . . . . . . . . 25
2.2.3 Employees Record System . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.4 Reporting System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.5 Documents System . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.6 Payroll System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.7 Security System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3 Draw backs in existing system . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3.1 List of Drawbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.4 Literature Review of The Existing System and Technologies . . . . . . . . 30
2.4.1 Biometrice Technology . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4.2 Existing Technologies and need of RFID . . . . . . . . . . . . . . . 33
2.4.3 RFID Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.4.4 List of Observed Needs . . . . . . . . . . . . . . . . . . . . . . . . . 36
III REQUIRMENTS & ANALYSIS . . . . . . . . . . . . . . . . . . . . . . . . 38
3.1 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.2 Non Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 39
x
3.2.1 Usability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.2.2 Human Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.2.3 Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.2.4 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.2.5 Implementation Constraints . . . . . . . . . . . . . . . . . . . . . . 40
3.2.6 Documentation and Help . . . . . . . . . . . . . . . . . . . . . . . . 40
3.2.7 Noteworthy Hardware . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.2.8 Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.3 Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.4 System Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.5 Use Cases Description(flow-chart) . . . . . . . . . . . . . . . . . . . . . . . 43
3.6 Analysis Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.7 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.8 Project Domain Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.9 Data Flow Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.10 E-R Analysis Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
3.11 Subsystem Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
3.12 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
IV DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.1 System Module Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.1.1 Modules of AHRIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.2 Database Model Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.2.1 Design Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.2.2 Normalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.2.3 List of DB Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.2.4 E-R Database model Diagrams . . . . . . . . . . . . . . . . . . . . 94
4.3 Software Architecture Design . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.3.1 Software Architecure Diagram . . . . . . . . . . . . . . . . . . . . . 100
4.4 Sequence Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.5 State-chart Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.6 Collaboration Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
xi
4.7 Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
4.8 Deployement Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
V IMPLEMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
5.1 Tools and Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.2 Methods Used for Implementation . . . . . . . . . . . . . . . . . . . . . . . 128
5.3 Software Components: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
5.3.1 ULL and BLL Methods: . . . . . . . . . . . . . . . . . . . . . . . . 130
5.3.2 BLL Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
5.3.3 DAL Methods: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
VI TESTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
6.1 Testing Techniques & Strategies . . . . . . . . . . . . . . . . . . . . . . . . 140
6.1.1 Black Box Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
6.1.2 White Box Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
6.1.3 Path Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.1.4 Regression Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.1.5 Unit Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.1.6 System Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.1.7 Acceptance Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.2 Deriving Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.3 Test Cases for AHRIS using RFID and Biometrics . . . . . . . . . . . . . . 142
VII CONCLUSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
7.1 Pros & Cons of System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
7.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
7.3 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
APPENDIX A SOME ANCILLARY STUFF(GUI) . . . . . . . . . . . 157
APPENDIX B SOURCE CODE . . . . . . . . . . . . . . . . . . . . . . . 188
REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
VITA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
xii
LIST OF TABLES
1 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
2 Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3 TableHRIS001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4 TableHRIS002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5 TableHRIS003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6 TableHRIS004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7 TableHRIS005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8 TableHRIS006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
9 TableHRIS007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
10 TableHRIS008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
11 TableHRIS009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
12 TableHRIS010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
13 TableHRIS011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
14 TableHRIS012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
15 TableHRIS013 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
16 TableHRIS014 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
17 TableHRIS015 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
18 TableHRIS016 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
19 List of DB Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
20 TableTC01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
21 Table::Test Case 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
22 Table::Test Case 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
23 Table::Test Case 03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
24 Table::Test Case 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
25 Table::Test Case 05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
26 Table::Test Case 06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
27 Table::Test Case 07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
28 Table::Test Case 08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
29 Table::Test Case 09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
xiii
30 Table::Test Case 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
31 Table::Test Case 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
32 Table::Test Case 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
33 Table::Test Case 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
34 Table::Test Case 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
35 Table::Test Case 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
36 Table::Test Case 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
37 Table::Test Case 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
38 Table::Test Case 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
39 Table::Test Case 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
40 Table::Test Case 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
41 Table::Test Case 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
42 Table::Test Case 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
xiv
LIST OF FIGURES
1 Organization Chart of DHA . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 HR Information System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Basic AHRIS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4 Spiral Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5 Propose System Basic Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 18
6 System Interface1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
7 System Interface2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8 Biometrics Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9 Working of Biometrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
10 Typical RFID System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
11 Basic System Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
12 Flowchart1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
13 Flowchart2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
14 Flowchart3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
15 Flowchart4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
16 Flowchart5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
17 Flowchart6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
18 Flowchart7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
19 Flowchart8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
20 Flowchart9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
21 Flowchart10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
22 Flowchart11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
23 Flowchart12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
24 Flowchart13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
25 Flowchart14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
26 Flowchart15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
27 Flowchart16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
28 Analysis Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
29 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
xv
30 Project Domain Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
31 Data Flow Diagram level 0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 78
32 Det Data Flow Diagram level 0 . . . . . . . . . . . . . . . . . . . . . . . . . 79
33 data flow diagram level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
34 Control Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
35 E-R Analysis of HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
36 E-R Analysis of Employee . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
37 E-R Analysis of AHRIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
38 Subsystem Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
39 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
40 Modules of AHRIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
41 AS AHRIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
42 ES Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
43 PS Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
44 HRM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
45 EDMS Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
46 E-R Diagram of AHRIS 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
47 Detailed E-R Diagram 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
48 Software Architecture Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 100
49 Squence::Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
50 Squence::Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
51 Squence::Registering Employees . . . . . . . . . . . . . . . . . . . . . . . . . 102
52 Squence::Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
53 Squence::Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
54 Squence::Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
55 Squence::Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
56 Squence::Print reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
57 Squence::Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
58 Squence::Attendance manager . . . . . . . . . . . . . . . . . . . . . . . . . . 106
59 Squence::EDMS login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
60 Squence::Browse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
xvi
61 Squence::Zooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
62 Squence::Logout/exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
63 Squence::Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
64 Squence::Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
65 Statechart::Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
66 Statechart::Change-Password . . . . . . . . . . . . . . . . . . . . . . . . . . 111
67 Statechart::Registering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
68 Statechart::Data-handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
69 Statechart::Searching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
70 Statechart::EDMS-Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
71 Statechart::Attendance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
72 Statechart::Zoom-Browse . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
73 Statechart::Exit/Logoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
74 Statechart::Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
75 Collaboration::User Auth . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
76 Collaboration::Change pswd . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
77 Collaboration::Registeration . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
78 Collaboration::Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
79 Collaboration::Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
80 Collaboration::Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
81 Collaboration::Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
82 Collaboration::Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
83 Collaboration::Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
84 Collaboration::Man Attendance . . . . . . . . . . . . . . . . . . . . . . . . . 121
85 Collaboration::EDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
86 Collaboration::browse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
87 Collaboration::zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
88 Collaboration::logout/exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
89 Collaboration::connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
90 Collaboration::Dc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
91 Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
xvii
92 Deployement Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
93 Basic implemented Work Flow of AHRIS . . . . . . . . . . . . . . . . . . . 127
94 GUI::CLick . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
95 GUI::Splash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
96 GUI::authentication1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
97 GUI::authentication2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
98 GUI::main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
99 GUI::main1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
100 GUI::changePassword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
101 GUI::changepswd2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
102 GUI::changepswd3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
103 GUI::main11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
104 GUI::CAlc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
105 GUI::mainmenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
106 GUI::logoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
107 GUI::definations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
108 GUI::definations1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
109 GUI::Recruitment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
110 GUI::Applicantions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
111 GUI::main21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
112 GUI::Applicants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
113 GUI::Selectedapp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
114 GUI::EmpRec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
115 GUI::Emprec1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
116 GUI::Emprec2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
117 GUI::Emprec3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
118 GUI::Leave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
119 GUI::Leave1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
120 GUI::Attendance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
121 GUI::Attendance1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
122 GUI::EmpPerf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
xviii
123 GUI::EmpPerf1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
124 GUI::EmpPerf2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
125 GUI::EmpPerf3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
126 GUI::EmpPerf4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
127 GUI::EmpPerf5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
128 GUI::Payroll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
129 GUI::Payroll1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
130 GUI::Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
131 GUI::Search1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
132 GUI::Search2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
133 GUI::Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
134 GUI::Reports1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
135 GUI::Reports2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
136 GUI-Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
137 GUI-Report3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
138 GUI-Report4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
139 GUI-Report5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
140 GUI-Report6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
141 GUI-EDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
142 GUI-EDMS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
143 GUI-EDMS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
144 GUI-EDMS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
145 GUI::Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
146 GUI::Admin1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
147 GUI::Admin2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
148 GUI::Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
149 GUI::Help2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
150 GUI::Help3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
151 GUI::Help4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
152 GUI::Help5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
153 GUI::Attmngt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
xix
154 GUI::Attmngt1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
xx
DECLARATIONS !
The Purposed Project Automated Human Resource Information Using RFID and Biomet-
rics is based upon new and most demanded technology that is Radio Frequency Identification
(RFID) and Thumb Identification using Biometrics. That fulfills requirements of Defence Hous-
ing Authority (Islamabad Region) HR,Attendance and Payroll System. DHA may enjoy a lot of
advantages with this technology. One of them is DHA may enhance this technology by using
on their own product, having front of them a model of this project.
This project uses RFID Kit and some other hard wares to successful implementation. So
it has been confirmed and written statement has been got that MINIMUM HARDWARE cost
will be fulfill by the DHA. After completion of Project Hardware would be property of DHA and
software would be freely available ONLY for DHA. It also has been discussed with student (Mr.
Muzammal Naseer Janjua) have copy right reserved for this software. Hardware and general
information about organization would be available as students desire.
It is also declares that as software is developed as Senior Design Project,So there will be no
cost or sale of this project.DHAs data is used for analysis purpose,the software is not only used
in single Organization.It is a general Software which can be implemented by any organization.
xxi
CHAPTER I
INTRODUCTION
In this chapter first of all i will introduce system and its brief overview and objectives.After
that proposed system will describe and the scope of the project. Then the implementation
methodology, adopted throughout the development cycle will be explained.
1.1 Project in Breif
1.1.1 Project Title
Automated Human Resource Information System(AHRIS) Using RFID and Biometrice.
1.1.2 Project Area
This project belongs to the broad area of Software developement and Engineering . More
specifically it lies in the domain of Wireless Communication,Security and Database Man-
agement.
1.1.3 Problem Definition
This Project is a case study of well known organization DHA Islamabad.To create a soft-
ware which automate the different systems and provide high level authentication to the
firms and organization.It focuses on the main systems of any organization
1)Human Resource Manager
2)Employee Record Manager
3)Payroll System
4)Authentication and Security
5)Automated/manual Attendance System
6)Reporting
1
1.1.4 Supervisors
External Supervisor:
Mr.Abdullah Bin Qadeer
(Doing Phd(in progress))
Head of Nettech Technologies pvt limited.
Contact No: 0323-6388324
2
1.2 Literature Review of existing system from some uni-versities
In this section literature review from some of the projects from universities,these projects
have a co relation with this proposed project.
Project 1 : ATTENDANCE & PAYROLL SYSTEM FOR MIA ENTER-PRISES THROUGH RFID(MCS FYP)
Developed by:
Muhammad Abid(Reg. # 998-CS/MCS/05) Khurram Nazir(Reg. # 987-CS/MCS/04)
Department of Computer Science,Faculty of Applied Sciences,
International Islamic University Islamabad (2007)
Abstract : Authenticate and manage Attendance and Payroll through RFID.OnlyRFID !
Project 2 : Record Management System of Shah Traders (MCS FYP)
Developed By:Rafhan Quereshi
Amir Murtaza
Department of Computer Science,Allama Iqbal Open University, H-8, Islamabad 2006
Abstract : To keep and manage record of a orgranization.No Authentication !
Project 3 : ACCESS CONTROL AND SECURITY SYSTEM USINGRFID
Submitted by
G.GOVARDHAN REDDY, M.PRASHANTH, P.SURESH RAJ, P.VINOTH,
3
Department of E & computer Science,ANNA university chennai.2006
AbstracT:To allocate RF tags and identify Users.
Proposed project is....
Automated HR information System Using RFID and Biometrics
Submitted by
M.Muzammal Naseer Janjua
(1339-FUIMCS-BSSE04)
Department Of Software Engineering And Computer Science Foundation University
,Pakistan
AbstracT:To Automate Flow of information system in organization of HR depart-ment with authentication using RFID and Biometrics.To organize automation of At-
tendance System with Recruitement department,Employees,Electronic Data organi-
zation.
For Further Detail : Refer to Abstract Section [Page Vi] of this Document.
4
1.3 Introduction to Organization(DHA)
An Housing and Engineering base Organization DHA(Defence Housing Authority) a Pri-
vate Limited Company incorporated in 2002 as DHI.It became authority in 2005,so its
known as DHA now. Organization has different branches in different cities of Pakistan and
also in Middle East. Its corporate office exists in Islamabad.
DHA islamabad concerned with developing an applying different approach in the field
of Housing and Plotting disciplines. It provides the solution and fulfills the most demanded
and valuable contemporary demands of public.
An Housing & Plotting based organization provides total solutions for Residential, Com-
mercial as well as Industrial Livings,with all necassary needs of living.DHA Have a healthy
amount of skilled workers, brilliant team of professionals dedicated to Business Manage-
ment, Finance and Engineering Services.
DHAs Vision
To be a dynamic and Leading Organization with Vision & Strengths of quality.
To be an ultimate choice of the customer with reliable product at affordable cost.
A total customer satisfaction, is pre-determined goal, focused by the management,to make it thus attainable.
In order to ensure full utility and comfort to the customers, a team of qualified &factory trained Engineers are working.
1.3.1 Projects of Orgranization
1. Phase-1 Compromize of....2000 plots
2. Pahse-2 Compromize of....8000 plots
3. Phase 1 ext
4. Phase 2 ext
5. Overseas Sector
5
Recently launched Project by DHA
1. DHA Villas
2. DHA Valley
3. DHA Valley overseas Sector
4. DHA Homes
5. DHA Buisness Bay
DHA has established different department to fulfill the desired needs of Organization.So
to manage all the need of mainpower,HR department was established for smooth functioning
of organization.
1.3.2 Organizational Chart
Figure 1: Organization Chart of DHA
This is the Main Departments Organizational chart of DHA,in this project we are only
covering automation of HR department.
6
1.3.3 Human Resource System
The Human Resources Management (HRM) includes a variety of activities, and key among
them is deciding what staffing needs you have and whether to use independent contractors or
hire employees to fill these needs, recruiting and training the best employees, ensuring they
are high performers, dealing with performance issues, and ensuring your personnel and
management practices conform to various regulations. Activities also include managing
your approach to employee benefits and compensation, employee records and personnel
policies. Usually small businesses (for-profit or nonprofit) have to carry out these activities
themselves because they cant yet afford part- or full-time help. However, they should
always ensure that employees have and are aware of personnel policies which conform
to current regulations. These policies are often in the form of employee manuals, which all
employees have.[7]
Figure 2: HR Information System
The HRM have undergone tremendous change over the past 20-30 years. Many years
ago, large organizations looked to the Personnel Department, mostly to manage the pa-
perwork around hiring and paying people. More recently, organizations consider the HR
Department as playing a major role in staffing, training and helping to manage people so
that people and the organization are performing at maximum capability in a highly fulfilling
manner.
HR in DHA
Currently HR dept in DHA has manual system or Excel management system.This de-
partment need automation for quick process of work and smooth functioning to the orga-
nization regarding multiple aspects.HR Department as playing a major role in staffing,
7
training and helping to manage people so that people and the organization are performing
at maximum capability in a highly fulfilling mannener.
So, to achieve all the required needs of this department which are discussed in Back-
ground chapter,AHRIS using RFID and BM is proposed and it works on
1. Applications
2. Applicants
3. Employee Manager
4. Leave Manager
5. Payroll Manager
6. Attendance Manager
7. Desicpline Manager
8. Reporting Manager
8
1.4 The Project
1.4.1 Objectives
The objective of this project is to develop a Automated management system which im-
plements the ideology of different Management System and the most advance Electronic
Documents Management System with Automation of Attendance System to produce more
reliability to organizations . It will be an easy to use management tool to help todays man-
agers to successfully built record and monitor Employees. Main objective of the projects
are:
Human Resource Management System,which enroll new employees and also checkwhether the employee is still in organization or resigned.
EDMS , which stands for Electronic Documents Management System.All scannedorginal Documents are kept in this management system.
Payroll System , Daily,Weekly and Monthly report of Employees generated.PayrollSystem will ensure the exact calculation for the monthly salary of Employees.
To develope Automated Attendance System,When a registered user entered in theprimises of the organization he / she may have to authenticate him/her self through
Biometrice and RFID device.
To provide GUI (Graphical User Interface) to help users to easily use the software tomanage their projects.
9
1.4.2 Project Overview
This system is designed and developed based on the following organizational requirements.
The software will be only be used by authorized person. i.e. administrator or usercreated by the administrator.
Attendance can be marked with or without RF cards.
The reports which produce not only be automatic but the user will be able to selecta choice for the report generation.
The software will be capable of having Encrypted information of an employee.
Having manual and automatic Attendance options
Computer generated reports
No need to show/Swap RF cards, no need more registers. *(Depends H/W Range)
The System will have a single centralized database and all of its module will be connected
with each other through that database.
Figure 3: Basic AHRIS System
10
1.4.3 Project Scope
The scope of this project Automated HR Information System using RFID and Biometrice is
very immense.This system will enable the managers and teams working on several projects
at different sites to keep themselves well-versed of the updated information.This System
has many capabilities to resolve different scenarios in a well organized envirnoment.
Also using wireless and Thumb identification technology make the project more industrial
and worth keeping.The System Also provide Different reports of recorts on Daily,weekly
and monthly bases by using the most advanced tool Crystal Reports.So Reporting is easily
available for Admins.When an employee enters will show his card then attendance will mark
with time , date etc and also application will show the status of the employee. (Either this
will IN or OUT, while first time when employee show his card then status will IN and at
the second time this will OUT).
AHRIS is capable of
1-Software
i -Automated Attendance System.
ii -More Secured using Thumb identification.
iii-Human Resource Management System(HRMS).
iv -Payroll System(PS).
v -Electronic Documents Management System(EDMS).
2-Hardware
i - RFID for Authentication and Enrollment.
ii - Biometrice(Thumb Identification) for Authentication.
11
1.5 Developement Process Model
The process model used for the development of HRIS using RFID and Biometrics System is
Spiral Model. The Spiral Model was designed to include the best features from the Waterfall
and Prototyping Models, and introduces a new component - risk-assessment. The term
spiral is used to describe the process that is followed as the development of the system
takes place. Similar to the Prototyping Model, an initial version of the system is developed,
and then repetitively modified based on input received from customer evaluations. Unlike
the Prototyping Model, however, the development of each version of the system is carefully
designed using the steps involved in the Waterfall Model. With each iteration around the
spiral (beginning at the center and working outward), progressively more complete versions
of the system are built. [14]
Figure 4: Spiral Model
Risk assessment is included as a step in the development process as a means of evaluating
each version of the system to determine whether or not development should continue. If
the customer decides that any identified risks are too great, the project may be halted. For
example, if a substantial increase in cost or project completion time is identified during one
phase of risk assessment, the customer or the developer may decide that it does not make
sense to continue with the project, since the increased cost or lengthened timeframe may
make continuation of the project impractical or unfeasible.
The Spiral Model is made up of the following steps:
Project Objectives. Similar to the system conception phase of the Waterfall Model.Objectives are determined, possible obstacles are identified and alternative approaches
are weighed.
12
Risk Assessment. Possible alternatives are examined by the developer, and associ-ated risks/problems are identified. Resolutions of the risks are evaluated and weighed
in the consideration of project continuation. Sometimes prototyping is used to clarify
needs.
Engineering & Production. Detailed requirements are determined and the soft-ware is developed.
Planning and Management. The customer is given an opportunity to analyzethe results of the version created in the Engineering step and to offer feedback to the
developer.
Throughout the development of this Project spiral model has been followed after ana-
lyzing its benefits in use and problems it addresses.
1.6 Proposed System
1.6.1 Motivation
21st Century make a great change in the technology and to live in this world,one have to
keep in touch with emerging technologies round the globe.In Computer Science and Software
Engineering field changes are not on daily bases they are on millisecond bases.So,keeping in
mind this motivate to automate the manual system and to provide more secure and reliable
systems to clients.With reliablity one has to keep in mind to make it validity and availibility
very long.
Though the globalization has change the world in many aspects,but still implementation is
the main need to improve old systems.Manual Systems are changed in to Dynamicity but
still not reliability.Bar Codes,touch screen and many other technologies are now converted
into wireless and Softwares are more intelligent,they interact with the hardware and catch
the changes provided by hardware.
Old manual systems though they are computerized but still not automated motivate me
to develope this projectAutomated Human Resourse information System Using Biometrice
and RFID which resolve many problems which are faced by organizations.This covers the
13
Wireless technology with thumb identification and covers a huge area of Software Science
which is used to develope a integrated Management System.
1.6.2 Proposed system benefits
In AHR & MS Biometrice & RFID all the tasks are being completed in manual system will
be able to perform in computerized fashion. This automated system has lots of benefits as
compare to manual system. Some of these major benefits are,
User friendly automated environment
RFID Layers are not dangerous for Health
Double Authentication System
Thumb Identification System for Biometrice
Short Listing of Selected Candidates
Easy to Installation of hardware
Abstract Data Security
An Evolvable/Portable/Verifiable Standard Long life Hardware/Software
A Completely Robust Software
A Complete Reliable Auto Attendance Management System
Every time Updated Information available
A 100% Reliable System
Having Manual and Automatic Attendance options
User defined pay cycles for time card entry
User defined voluntary deductions and taxable status
14
User defined deduction schedule and yearly progress
Detailed employees history
Less Electricity (Power )Consumption
No more Signatures / files and 2nd time Attendance Registers
A Standard/valuable/new technology meeting software
No need to Show/Swap cards, No need more registers
1.6.3 Proposed System Features
These are only software related features,(excluding Automation of Attendance features)
Security Manager
login
Password
Definations
Religion
Sector
Rank
Qualification pay
Allownces
Leave types
Cources
Appoinments
15
Domicile
Performance pay
Directorates
Applications Manager
Job Applications
Short-list Applicants
Selected Applicants
Employee Manager
Personal Details
Education History
Employee ID card
Employement Record
Employee contract
Leave/Attendace Manager
Leave Application
Attendance
Employee Performance Manager
Verification
Descipline
Suitability Report
16
Employee Performance review
Search Manager
Employee general query
Leave query
EDMS Manager
Electronic Data Management System
Reporting Manager
Appoinment
Applicants
Employee personal record
Employee report
No of years Report
Employee service calculator
Leave reports
Attendance reports
17
1.7 Project Overall Description
This section describe Project overall description as well as with software specification of the
system.The idea of the whole system is shown in basic system diagram.
1.7.1 Basic System Diagram
Figure 5: Propose System Basic Diagram
1.7.2 System Operational Modules
Module #01: Receptionist View
RF reader has embedded antenna that transmits radio rays continuously, whenever em-
ployees with RF tag enters in the organization. He/She passes card from RF reader. Dumb
devices (Reader/Monitors) would be in working condition at main entrance/Reception or
any place as well in HR department. Readers antenna read these numbers. And Update
statuses of employees by displaying IN/OUT title with speaking facility according to his/her
18
enter/exit status.All process is automatically done.
Module #02: Biometric Authentication
When a registered Employee enters into the arena,he/she may have to authenticate him/herself
through Biometrics Thumb identification device.This device uses database of registered em-
ployees at backend,it identify the thumb and allow the employee to enter into arena.
Module #03: Allocation of RF Tags
Processed Form by the DEO is available for HR work. HR verified/match the enter
data with form. He may reject a form for again DEO phase. In-case of allocation of RF tag
HR can assign a valid RF tag to this form. He can allocate an Encrypted Tag id to this
form (for feature addition).
Module #04: EDMS Hall
Newly entered employee get there job/department by the Administrator.Electronic Data
Management System (EDMS) scan their images and upload it into database.This hall has
scanner available for this purpose,Only administrator can view,edit and scan these images.
Module #05: HR Server Room
This server has got almost all the available options,all subsytem are directly connected to
this system to perform their desired actions.Employees records,Payroll,deductions,attendance,desciplanary
cases etc are available here.All automation is updated in this server room.At any time or
at the end of a month a user can check his attendance and pay details.
Module #06: Data Entry Halls
Data Entry operators are available in Data entry halls,all data related to employ-
ees,applicants etc will be entered by Data entry operators.DEO have limites access to the
database and have only those rights which are assigned by the Administrator.
19
1.7.3 System Interfaces
The product has the following system interfaces:
A system interface for launching the application at the server side. In the screenshotbelow the application can be launched by clicking the PjHRIS icon.
Figure 6: System Interface1
A system interface after launching the application. In the screenshot below the appli-cation can be launched by clicking the PjHRIS icon.
Figure 7: System Interface2
20
1.7.4 User Interfaces
For Detailed User interfaces Refer To Section User Manual Starting from Page : 155
1.7.5 Hardware Interfaces
Following are the hardware interfaces of our system:
Thumb Identification: Biometrics use Thumb identification,as every person will haveits own thumb identification.
RF ID: A unique RF ID will be assigned to each User.
RFID Card: A Radio Frequency identification card is a punch card which connectsto a RFID system,it connects with reader wirelessly.
1.7.6 Software Interfaces
The system will consist of a software interface that will provide connectivity with the
database management system (MS Access or ORACLE). The database will used for storing
user information, user records,etc.
1.7.7 Memory
The memory requirements for the server and client are as follows:
Server
The server should have at least 256mb of primary memory for efficient working and20mb of secondary memory (excluding Database memory requirements).
40 Gb of Harddisk.
1.7.8 Operations
The basis operations of the system are as follows:
All basic operations like authentication,automation of attendance,payroll,employeesrecord,employee history,Cases etc.
21
All basic Searching operations like Searching by name,searching by ID etc.
Records saving on the server.
1.7.9 Site Adaption Requirment
Since the communication in the project is based on Radio Frequency waves, so it is necessary
to have a site which is free of RF noise.
An environment having high voltage power lines, high voltage transformer,boosters or
generators will generate a lot of RF noise which might lead to problems in communication
between the users and the authentication server.
1.7.10 User characteristics
The product is aimed for users who have enough knowledge of using a Desktop Applications
or a Database applications .As this product is specifically for DHA,so it is required for them
to hire desired persons.
1.7.11 Software System Attributes
Reliability
To provide reliable communication and avoiding noise, we will not use the wireless carrier
to its full capabilities in terms of range.Mark attendance and also manage record should be
handled automatically as well as manually and data will be consistent.
Availability
To make all the features of the system available to the legitimate user, we will limit the
number of simultaneous rights. This will ensure the availability of all the services to the
active user. Again the number of simultaneous rigthts can be increased by the administrator
at any time.
Security
Following are the points which will ensure security of the system:
22
Each user will be authenticated with a help of a username and password.
The built in security facility of the Thumb identification will also be used.
Since the availability of the service is limited to an organizational users, so this factalso reduces the security threats to the system.
Maintainability
The system will be designed and implemented on the principles of Object Oriented Software
Engineering. Following the Paradigm will increase System Maintainability.
23
CHAPTER II
BACKGROUND
2.1 Detailed Study of Existing System
The detail study of the Existing System was carried out through a series of meetings with
the manager and staff workers of the departments of the organization.Beside that also
the existing system documents was thoroughly studied to understand the existing manuals
systems of DHA islamabad .
To understand the complexity of the existing system, not only adopted the functional
analysis approach, but the entity analysis considerations were also applied. This combina-
tion of modern analytical techniques provides in depth understanding of the existing system.
Following are the guiding principle of the methodology:-
Interaction with the managers and the related persons handling the manual system.
Observations of actual working in the office.
Inspection of routine documentation and records.
2.2 Survey of the Existing Systems at DHA isb
Afterwards,keeping in mind the background of the company a survey of the existing system
is arranged.This survey was taken for different departments to fullfill the required need of
the company.
Although the DHA Islamabad is a big company with different departments,every de-
partment need different softwares to manage the system.But due to less time,i focused on
their some systems,whih require a need to meet the ongoing technology.SO,in this survey
following systems were focused and observed .
24
2.2.1 Attendance System
Manual Attendance system,which itself leads to many problems. Manual system is dif-
ficult to manage as will as difficult to maintain.A register was placed on reception ta-
ble and every employee has to mark his attendance with signature,which is very old sys-
tem.Beside that,there is no security else the availabity of the person on the reception table
is must.otherwise attendance can be marked by other person very easily.
So,the need was to computerize the Attendance system,but also make an Automated
Attendance System which fullfill the requirment of the security with automation of the
attendance.which may or maynot require any operator to authenticate the users.
2.2.2 Recruitment System(HR Department)
Human Resource Department plays very important role in any organization or company.Many
Tasks depends on this department.Current sytem in DHAs HR department has manual sys-
tem for taking Applications from the applicats and processing them.The manual process is
very slower. All the processes including approval takes a handsome amount of time.
Though it is computerized in Excel sheet ,but its not reliable nor sufficient.So the need
was to develope a application which is user friendly to the department and which is able
to fulfill all the needs.So some meetings are taken with the department and different works
are observed to come across some good solution.
2.2.3 Employees Record System
Moving to the Record system of employees,all employees were listed in a register and in a
excel sheet files.There was no secure managed system for the record,so in case of physical
damaged to the data, which is most precious, asset of an organization, there is no mean
(backup and recovery procedure) to recapture the damaged data. All employees Personal
Details,Educational history etc was manually stored somewhere,and The data stored is
insecure in files and ledgers. Anyone can modify the entries in the Vouchers or Ledgers
in manual system. Data can be stolen from files or files can physically be misplaced or
damaged.
25
2.2.4 Reporting System
In manual system reports preparation is very laborious job. Moreover adhoc reports required
by the organization in certain situations, manual system gives no provision for adhoc re-
ports.Reporting is very essential for managers and heads to keep in track all the employees
but in manual system is very difficult job.So a need was to have a very good reporting
system which have daily,weekly and monthly reporting system.
2.2.5 Documents System
The current manual system is not efficient. A lot of time is being spent for searching even
a single record. General and high priority documents that need frequently attention are
also treated haphazardly. No one can find out the desired document easily without the
concerned person. It is because that each record has to be checked. Moreover, if a report is
needed to generate, it takes a long time due to manual searching and processing of records.
In manual system the same information is stored at more than one place. Same data
are recorded at many different places. This not only leads to invalid data processing but
also consumes the data storage place. The data can be updated at one place while there
is another place where same data is placed but not updated. This causes weaknesses in
system.
2.2.6 Payroll System
Payroll System has many mathematical calculations and also depends on other factors,for
example on attendance basis etc.But in manual systems All the mathematical calculations
are carried out manually that can cause errors. The result complied by the individuals have
errors that, when detected take a lot of time for corrections and chance of errors increases
with the increment of data.
2.2.7 Security System
DHA Islamabad has army personnels which act as security,but what about security of
departments?What if the right person is entering in wrong department?These questions
cause insecurity in manual system. The security is very poor in the manual system. There
26
is no security to protect the illegal users to the secret and important data, even the data
storing files of paper can physically be misplaced or damaged.
Authentiation is the necassity of the deparments,so that only the registered persons can
entered into their departments.All deparments need some sort of secured enteries,and for
that hardware an automated software is needed which act accordingly and managed the
system.
2.3 Draw backs in existing system
2.3.1 List of Drawbacks
The following are the major drawback of existing system.
2.3.1.1 Exhaustive and time consuming system
DHA has a healthy amount of employees that are divided into different Departments. Nor-
mally labours located in Warehouse department while other remains in Engineering,IT,
Managements and Finance departments. Managing Human Resource ,Payroll and Atten-
dance in all departments is really a very critical and exhaustive job.
2.3.1.2 Not detailed system
DHA has its manual Employee Attendance System. An employee must have to sign on a
particular register for proving his availability in the Organization. There is no proper check
and balance system (Coming and Out going time) for an employee.
2.3.1.3 Manual system
DHA has health amount of employees. Organization also has friendly atmosphere with
different options for their employee to late sitting, voluntarily sitting and late with paid
sitting. In Contemporary situation managing pays and attendance is being performed into
to TWO Registers or Excel Sheets. One Register is reserved for morning attendance and
other one is for after noon (after Lunch).
27
2.3.1.4 Does not maintains history
There are different categories of employees in the organization few one are technical and
others are in finance/management. Monthly salary is being paid by manuals system. There
is a standard amount that is being paid by hand to its employee. And other one is getting
paid by their banks after deduction of taxes, sur-charges and etc. Existing system does not
provide ordinary checks/slips and monthly details.
2.3.1.5 Employees availability problem
According to Organization internal departments a Staff may be available at different time
on different departments or even out of Organization. Often seeker/visitor faces problems
to meet with particular employees.
2.3.1.6 Not proper check and balance
Different departments have different kind of staff some one have Only Contractual and some
one are Permanent. DHA has its manually Employee Attendance System. According to
Job status person are being paid. While contractual employees in/out time Organization
demands critically. Still there is no proper check and balance system just having few
registers.
2.3.1.7 Does not satisfies organization standard
DHA has well name in the name of national and International Organizations. So Orga-
nization must meet with its Standard. Like Auto Attendance/Online product/Employee
Management System.
2.3.1.8 More chances of errors
There may be mathematical errors while generating bills manually therefore customers and
department may suffer. In manual system errors are very common.
28
2.3.1.9 Inconsistent Data
Due to redundancy inconsistency arises when data item is changed at one place and this
change is not reflected at all other redundant places.
2.3.1.10 Not Online/web supported
Existing system is exhaustive/time consuming, Not web supported and not detailed.
2.3.1.11 Un-reliable/Obsolete system
Obsolete/un-reliable i.e. old system managing user data/attendance on Registers/Papers.
29
2.4 Literature Review of The Existing System and Tech-nologies
Before moving forward,it is better to have a quick literature review of the existing systems
and technologies.
2.4.1 Biometrice Technology
Biometrics refers to two very different fields of study and application. The first, which is the
older and is used in biological studies, including forestry, is the collection, synthesis, analysis
and management of quantitative data on biological communities such as forests. Biometrics
in reference to biological sciences has been studied and applied for several generations and
is somewhat simply viewed as biological statistics. [12]
More recently and incongruently, the terms meaning has been broadened to include the
study of methods for uniquely recognizing humans based upon one or more intrinsic physical
or behavioral traits. Biometrics are used to identify the input sample when compared to a
Figure 8: Biometrics Chart
template, used in cases to identify specific people by certain characteristics.
possession-based
using one specific token such as a security tag or a card
knowledge-based
the use of a code or password.
A biometric system can provide the following two functions:
30
Verification
Authenticates its users in conjunction with a smart card, username or ID number. The
biometric template captured is compared with that stored against the registered user either
on a smart card or database for verification.
Identification
Authenticates its users from the biometric characteristic alone without the use of smart
cards, usernames or ID numbers. The biometric template is compared to all records within
the database and a closest match score is returned. The closest match within the allowed
threshold is deemed the individual and authenticated. [12]
Figure 9: Working of Biometrics
Uses and initiatives
Biometric technology was first used at the Olympic Summer Games in Athens, Greece in
2004. On registering with the scheme, accredited visitors will receive an ID card contain-
ing their fingerprint biometrics data that will enable them to access the German House.
Accredited visitors will include athletes, coaching staff, team management and members of
the media.
Wolfgang Schuble in the March 2008 edition of its magazine Datenschleuder. The maga-
zine also included the fingerprint on a film that readers could use to fool fingerprint readers.
Several banks in Japan have adopted palm vein authentication technology on their
ATMs. This technology which was developed by Fujitsu, among other companies, proved
to have low false rejection rate (around 0.01%) and a very low false acceptance rate (less
than 0.00008%).
31
The Nigerian Government has now rolled out fingerprint recognition throughout its
airports in fights to reduce passport fraud. All new passports distributed now have a
biometric chip containing the individuals characteristic in encrypted template form.
The United States government has become a strong advocate of biometrics with the
increase in security concerns in recent years, since September 11, 2001. Starting in 2005, US
passports with facial (image-based) biometric data were scheduled to be produced. Privacy
activists in many countries have criticized the technologys use for the potential harm to
civil liberties, privacy, and the risk of identity theft. Currently, there is some apprehension
in the United States (and the European Union) that the information can be skimmed and
identify peoples citizenship remotely for criminal intent, such as kidnapping. There also are
technical difficulties currently delaying biometric integration into passports in the United
States, the United Kingdom, and the rest of the EU. These difficulties include compatibility
of reading devices, information formatting, and nature of content (e.g. the US currently
expect to use only image data, whereas the EU intends to use fingerprint and image data
in their passport RFID biometric chip(s)).
32
2.4.2 Existing Technologies and need of RFID
We have seen the security personnel checking the employees identification cards at the
entrances to avoid illegal entry. The employees sign a register at the entrance before getting
in. This is still being practiced in most of the companies.
However, the disadvantages are that, when there is a necessity of providing control at
many locations inside the company, a person at each point will not be an economical way
of implementing it.
Then came were the punch cards. Employees possess cards, which are punched when
they enter into the building. But it had disadvantages. Workers started to practice buddy
punching, for their co-workers.
Concerns about buddy punching-the practice where employees fraudulently clock their
co-workers in or out to give them credit for time that wasnt actually worked-led Continental
Airlines to implement a fingerprint ID system to augment their automated employee time
and attendance recording system. The company expanded the system from Control Module
after it saved an estimated $100,000 in the first year. This led to the bar code readers.
It is a much common sight to see a bar code reader in the companies. These are used to
check with the employees identification. The employees swipe the card in the provided slot.
Then the access is given after checking the authenticity of the card. This was a substitute
to the security and emerged as a new technique in access control. This acted as a starting to
the automation of the access control. But, the bar code readers are contact readers where,
the cards are required to touch the readers.
With growth of technology and giant leap in the field of Radio frequency transmission,
a requirement for the same application using RF is desired.
A further improvement is the RF ID card technology, which uses contact less card
readers. Bringing the card nearer to the reader suffices for the reader to read the contents
of the card. This simplifies the usage for the employees. This technology is crawling into
the companies and has the potential to substitute the preceding technologies.
33
2.4.3 RFID Technology
RF technology is used in many different applications, such as television, radio, cellular
phones, radar, and automatic identification systems. The term RFID (radio frequency
identification) describes the use of radio frequency signals to provide automatic identification
of items.
Radio frequency (RF) refers to electromagnetic waves that have a wavelength suited
for use in radio communication. Radio waves are classified by their frequencies, which are
expressed in kilohertz, megahertz, or gigahertz. Radio frequencies range from very low
frequency (VLF), which has a range of 10 to 30 kHz, to extremely high frequency (EHF),
which has a range of 30 to 300 GHz. [1]
RFID is a flexible technology that is convenient, easy to use, and well suited for auto-
matic operation. It combines advantages not available with other identification technologies.
RFID can be supplied as read-only or read / write, does not require contact or line-of-sight
to operate, can function under a variety of environmental conditions, and provides a high
level of data integrity. In addition, because the technology is difficult to counterfeit, RFID
provides a high level of security.
RFID is similar in concept to bar coding. Bar code systems use a reader and coded
labels that are attached to an item, whereas RFID uses a reader and special RFID devices
that are attached to an item. Bar code uses optical signals to transfer information from the
label to the reader; RFID uses RF signals to transfer information from the RFID device to
the reader. Radio waves transfer data between an item to which an RFID device is attached
and an RFID reader. The device can contain data about the item, such as what the item
is, what time the device traveled through a certain zone, perhaps even a parameter such as
temperature. RFID devices, such as a tag or label, can be attached to virtually anything -
from a vehicle to a pallet of merchandise. [5]
RFID technology uses frequencies within the range of 50 kHz to 2.5 GHz. An RFID
system typically includes the following components:
An RFID device (transponder or tag) that contains data about an item
34
Figure 10: Typical RFID System
An antenna used to transmit the RF signals between the reader and the RFID device
An RF transceiver that generates the RF signals
A reader that receives RF transmissions from an RFID device and passes the data toa host system for processing
35
2.4.4 List of Observed Needs
In this section all the required needs are listed to develope a good new software from existing
system.The whole list is generated after a large survey of the existing systems.
Following is the list of Managers required
Attendance Manager
Daily Attendance
Weekly Report
Monthly Report
Leave Application
Recruitment Manager
Job Applications Handling
Short Listed Candidates
Selected Candidates
Employee Record Manager
Personal Details Management
Employee Record
Education History
Employee ID Card
Employee Contract
Employee Performance Manager
Verification
36
Discipline
Employee New Status
Employee Performance Review
Record Searching
Search By Name
Search By ID
Search by Document ID
Reporting Manager
Employee Reports
Performance Reports
Attendance Report
Payroll Manager
Weekly Calculations
Allownces
Monthly Payrolls
EDMS
Electronic Documents System
37
CHAPTER III
REQUIRMENTS & ANALYSIS
Requirements are capabilities and conditions to which the system must conform. A prime
challenge of requirements work is to find, communicate, and record what is really needed,
in a form that clearly speaks to the client.
Analysis emphasizes an investigation of the problem and requirements, rather than a
solution. Analysis is best qualified, as in requirements analysis that means investigation
of the requirements. Object-Oriented Analysis is an emphasis on finding and describing the
objects or concepts in the problem domain.
This chapter describes the Actors involved in the system,use cases,flow chart, analysis
model of the system. It explains the problem domain, requirements of the software, use-
cases and actors, and association Diagram of the system.
The requirements are divided into two parts.
3.1 Functional Requirements
Functional requirements are explored and recorded in the Use-Case model. Functional
requirements express the functions of the system that should be efficient, robust and simple
to use.
System Provide a form for Data Entry Operator (DEO)
On the basis of this form DEO will enter data.
After DEO work, Human Resource (HR) will assign a RFID Tag to this form.
DEO and HR can skip (a Scanned Image) form if form is not well Scanned or incorrectdata entered by DEO.
Form skip by DEO can be Re-set or Deleted by the Scanner.
38
Administrator assign jobs, Controls authorized users, Manage salary, and change jobstatus; manage advance, allowances, leave etc (almost all work).
Systems particular account will be providing ability to mark attendance throughRFID chip embedded card.
Authentication can be taken place by thumb identification system using Biometricedevice.
System generate different type of reports as required by the department,e.g dicipla-nary,daily attendance,record etc.
Data is scanned and managed through EDMS tool.
Provide ability of display attendance with speaking ability when employee entered orexit.
Provide ability to employee to login and can check his/her history.
3.2 Non Functional Requirements
It is helpful to use supplementary specification of the system to reduce the risk of not
considering some important fact of the system. Some of these requirements are non func-
tional requirements or quality requirements. These requirements have a strong influence on
the architecture of a system. Some non functional requirements of AHRIS using RFID &
Biometrice are as under:
3.2.1 Usability
Speed, ease, and error-free processing should be paramount in OAHRIS using RFID &
Biometrice of DHA islamabad.
3.2.2 Human Factors
Text should be easily visible for the user.
Should be avoided colors associated with the forms of color blindness
39
Special training should not be required for user; every user who is familiar with thedatabase can use this software.
3.2.3 Reliability
Mark attendance and also manage record should be handled automatically as well as manu-
ally and data will be consistent.Automation and Datawaring is also automatic,for example
if employee has resign, the search will automatically show his absence.
3.2.4 Performance
Employees management and Short listing of applicants should be done quickly.Users want
to complete payroll processing very quickly. System should be quick responsive for different
types of operations like calculation of overtime payments, Tax calculation and accessing
data from remote location.
3.2.5 Implementation Constraints
AHRIS using RFID & Biometrice insists on Microsoft Visual technologies and powerful
DBMS like Oracle 9i with Microsoft Acces, predicting this will improve portability and
supportability in addition to ease of development.
3.2.6 Documentation and Help
Documentation regarding the working of software, user manual, installation and adminis-
tration should be provided.
3.2.7 Noteworthy Hardware
Pentium IV or above is proposed for AHRIS using RFID & Biometrice of DHA is-lamabad.
128 MB Ram or above is proposed for AHRIS using RFID & Biometrice of DHAislamabad.
3.2.8 Error Handling
System should handle errors by