Human Resource Management System Using RFID
Human Resource Management System Using RFID
Using
Biometrics and RFID
A Thesis
Presented to
The Academic Faculty
by
In Partial Fulfillment
of the Requirements for the Degree
Bachelors in Software Engineering
Approved by:
Professor Originality-Checker
(Another Department)
Professor Verifier
Professor Anti-Plagiarism
Date Approved
iii
PREFACE
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 Authority(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.
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 applied 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 management 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
RF
EDMS
BM
PS
AS
AAS
DFD
CFD
FUIMCS
HRIS
RFID
UML
HR
DHA
DEO
VB
GUI
DBS
mb
Gb
VLF
OOA
E-R
DFD
PDM
AM
SDLC
SQA
BLL
ULL
DLL
DAL
Meaning
Radio Frequency
Electronic Data Management System
BioMetrics
Payroll System
Attendance System
Automated Attendance System
Data Flow Diagram
Control Flow Diagram
Foundation University institute of Management&
Computer Science
Human Resource Information System
Radio Frequency idnetification System
Unified Modeling Language
Human Resource
Defence Housing Authority
Data Entry Operator
Visual Basic
Graphical User Interface
DataBase System
Megabyte
Giga byte
Very Low Frequency
Object oriented Anaylsis
Entity Relationship
Data Flow Diagram
Project Domain Model
Analysis Model
Software Develpoment Life Cycle
Software Quality Assurance
Buisness Logic Layer
User Logic Layer
Data Logic Layer
Data Access Layer
Table 1: Abbreviations
viii
TABLE OF CONTENTS
DEDICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iii
PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
ABSTRACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vii
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xv
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1
Project in Breif . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1
Project Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2
Project Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.3
Problem Definition . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4
Supervisors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2
1.3
Introduction to Organization(DHA) . . . . . . . . . . . . . . . . . . . . . .
1.3.1
Projects of Orgranization . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2
Organizational Chart . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3
The Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2
Project Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
1.4.3
Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
1.4
1.5
. . . . . . . . . . . . . . . . . . . . . . . . .
12
1.6
Proposed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
1.6.1
Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
1.6.2
14
1.6.3
15
1.7
. . . . . . . . . . . . . . . . . . . . . . . . . .
18
18
ix
II
1.7.2
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
22
22
22
BACKGROUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
2.1
24
2.2
24
2.3
2.2.1
Attendance System . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
2.2.2
25
2.2.3
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
. . . . . . . . . . . . . . . . . . . . . . . .
27
List of Drawbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
30
2.4.1
Biometrice Technology . . . . . . . . . . . . . . . . . . . . . . . . .
30
2.4.2
33
2.4.3
RFID Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
2.4.4
36
38
2.3.1
2.4
3.1
Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
3.2
39
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
40
3.2.7
Noteworthy Hardware . . . . . . . . . . . . . . . . . . . . . . . . .
40
3.2.8
Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
40
3.3
Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
3.4
System Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
3.5
43
3.6
Analysis Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75
3.7
76
3.8
77
3.9
78
82
85
86
IV DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
4.1
4.2
4.3
87
4.1.1
Modules of AHRIS . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
92
4.2.1
Design Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92
4.2.2
Normalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92
4.2.3
List of DB Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . .
93
4.2.4
94
98
4.3.1
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
IMPLEMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
5.1
128
5.2
128
5.3
Software Components: . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
129
5.3.1
130
5.3.2
BLL Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
135
5.3.3
DAL Methods:
137
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VI TESTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
6.1
140
6.1.1
140
6.1.2
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
141
6.3
142
154
7.2
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
7.3
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
APPENDIX A
APPENDIX B
REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
INDEX
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
VITA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
xii
LIST OF TABLES
1
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
TableHRIS001
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
TableHRIS002
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
TableHRIS003
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
TableHRIS004
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
TableHRIS005
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
TableHRIS006
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
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
HR Information System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
Spiral Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
18
System Interface1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
System Interface2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
Biometrics Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
Working of Biometrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
10
35
11
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
76
xv
30
77
31
78
32
79
33
80
34
81
35
E-R Analysis of HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
82
36
83
37
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
97
47
99
48
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
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xx
187
DECLARATIONS !
The Purposed Project Automated Human Resource Information Using RFID and Biometrics is based upon new and most demanded technology that is Radio Frequency Identification
(RFID) and Thumb Identification using Biometrics. That fulfills requirements of Defence Housing 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
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 Management.
1.1.3
Problem Definition
This Project is a case study of well known organization DHA Islamabad.To create a software 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.4
Supervisors
External Supervisor:
Mr.Abdullah Bin Qadeer
(Doing Phd(in progress))
Head of Nettech Technologies pvt limited.
Contact No:
0323-6388324
1.2
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 ENTERPRISES 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.Only
RFID !
1.3
Introduction to Organization(DHA)
An Housing and Engineering base Organization DHA(Defence Housing Authority) a Private 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, Commercial 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 Management, 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
Organizational Chart
1.3.3
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]
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 Background 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
1.4
The Project
1.4.1
Objectives
The objective of this project is to develop a Automated management system which implements 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 managers to successfully built record and monitor Employees. Main objective of the projects
are:
Human Resource Management System,which enroll new employees and also check
whether the employee is still in organization or resigned.
EDMS , which stands for Electronic Documents Management System.All scanned
orginal Documents are kept in this management system.
Payroll System , Daily,Weekly and Monthly report of Employees generated.Payroll
System will ensure the exact calculation for the monthly salary of Employees.
To develope Automated Attendance System,When a registered user entered in the
primises 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 to
manage their projects.
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 user
created 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 select
a 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.
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
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]
12
Risk Assessment. Possible alternatives are examined by the developer, and associated 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 software is developed.
Planning and Management. The customer is given an opportunity to analyze
the 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 analyzing 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
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
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
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
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
1.7.2
18
19
1.7.3
System Interfaces
A system interface after launching the application. In the screenshot below the application can be launched by clicking the PjHRIS icon.
20
1.7.4
User Interfaces
For Detailed User interfaces Refer To Section User Manual Starting from Page : 155
1.7.5
Hardware Interfaces
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 and
20mb of secondary memory (excluding Database memory requirements).
40 Gb of Harddisk.
1.7.8
Operations
21
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
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
23
CHAPTER II
BACKGROUND
2.1
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 combination 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
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 department 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 difficult to manage as will as difficult to maintain.A register was placed on reception table and every employee has to mark his attendance with signature,which is very old system.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
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 system 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
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 reports.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
2.3.1
DHA has a healthy amount of employees that are divided into different Departments. Normally labours located in Warehouse department while other remains in Engineering,IT,
Managements and Finance departments. Managing Human Resource ,Payroll and Attendance in all departments is really a very critical and exhaustive job.
2.3.1.2
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
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
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
DHA has well name in the name of national and International Organizations. So Organization must meet with its Standard. Like Auto Attendance/Online product/Employee
Management System.
2.3.1.8
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
Existing system is exhaustive/time consuming, Not web supported and not detailed.
2.3.1.11
Un-reliable/Obsolete system
29
2.4
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
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]
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
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
34
35
2.4.4
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
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, usecases 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 incorrect
data 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 job
status; manage advance, allowances, leave etc (almost all work).
Systems particular account will be providing ability to mark attendance through
RFID chip embedded card.
Authentication can be taken place by thumb identification system using Biometrice
device.
System generate different type of reports as required by the department,e.g diciplanary,daily attendance,record etc.
Data is scanned and managed through EDMS tool.
Provide ability of display attendance with speaking ability when employee entered or
exit.
Provide ability to employee to login and can check his/her history.
3.2
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 functional 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
Special training should not be required for user; every user who is familiar with the
database can use this software.
3.2.3
Reliability
Mark attendance and also manage record should be handled automatically as well as manually 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 regarding the working of software, user manual, installation and administration should be provided.
3.2.7
Noteworthy Hardware
Pentium IV or above is proposed for AHRIS using RFID & Biometrice of DHA islamabad.
128 MB Ram or above is proposed for AHRIS using RFID & Biometrice of DHA
islamabad.
3.2.8
Error Handling
40
3.3
Actors
Actors
Name
User
Type
Primary
Operator
Primary
DB Admin
Primary
Description
The user can perform the following functionalities:
-Show card to RFID reader.
-Identify through Thumb identification system
-Enter Login
-Enter Password
-View Attendance record
The Operator can perform the following operations
at the server:
-Register/Deregister users
-Search Records of users
-Enter/view/edit/delete Employee Record.
-print Employee Record.
-Enter/view/delete Applicants Record.
-Enter/view/delete All Reports.
-Scan Images.
-View/delete Attendance Record.
-View Online Attendance.
-Calculate Payrolls.
-Leave record managing
-Allocate Tag IDs
The HR Admin can perform the following operations
at the server end:
-Connect/disconnect Devices.
-Register/Deregister users
-View connected users
-View/Search log by user id, name, type
-Assign username and rights.
-Reset Password.
-Manage Definations
-Check Disciplonary History
-View/delete Attendance records
-View/delete EDMS .
-Check Employee performance.
Table 2: Actors
41
3.4
System Diagram
42
3.5
This sections covers the description of all use cases followed by the flow charts of their
descriptions. [15]
1.User Authentication
Name
Number
Type
Pre Condition
Post Condition
User Authentication
HRIS001
Base
User Must be registered and System is Operational
The validate user logs in to access the system and
perform its required work.
User & System
1.Enter Login name
2.Enter Password
3.If login Name and Password is valid show main
screen
4.If wrong information is entered user will be prompt
to relogin.
System Generate Error Message or Exit
Authenticate User and provide security to the system
and Allows the user to access the system
N/A
N/A
Actors Involved
Basic Course
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. User runs the application
System Responce
2. System displays the login form to enter the user
name and password.
Table 3: TableHRIS001
43
44
2. Change Password
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Change Password
HRIS002
Base
User must be Logged in
User can change only its own Password
Operators & admins
User request to change his Password for making secure his account.
1.Logged in
2.Enter old Password
3.Enter new Password
Generate Error Message
,invalid old Password
Allows the user to change password as many
times as he wants.
N/A
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1.User chooses change password
from menu or clicks
change password button.
3.User enters old password,
new password and
confirm new password
System Responce
Table 4: TableHRIS002
45
46
3.Registering Employees
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1.Operators select to Enter
Employee record from menu
3.Operator enters All information,
about Employee and
submit it into Database
System Responce
2. System displays the corresponding form..
Table 5: TableHRIS003
47
48
4.Save information
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Save Information
HRIS004
Base
Record is available to save.
Record saved.
Operator,Administrator
1.Click On Employee Register
2.Enter Data in Fields
3.If valid data is not entered,Generate Error message
4.Valid Data submition should update the DB
Generate Error Message,invalid information entered
User can save the record in the database for future
use
Valid data in desired fields.
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Record entered in the fields.
3. Operator click the save button.
System Responce
2. Save button enabled.
4. System verifies information and Record has been
saved..
Table 6: TableHRIS004
49
50
5.Search Record
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Search
HRIS005
Base
Administrator,Operator must be logged in
Searched record is found
Operators, Administrator
1.Click On Search
2.Search By id or Name
3.Record found and display results
Generate Error Message,Record not found
To search the desired record
N/A.
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Administrator log in. .
3. Administrators selects the
search option and choose/provide
necessary detail either search
by emp id or
search by Name
then press search button
System Responce
2. System displays the administrator search form.
Table 7: TableHRIS005
51
52
6.Edit Information
Name
Number
Type
Pre Condition
Edit
HRIS006
Base
Record is present in the database which is to be
edited.
Record Updated.
Operators, Administrator
1.Click On Search
2.Search By id or Name
3.Record found and display results
4.Edit is pressed
5.Update Button is pressed and information is updated.
Generate Error Message,Record not found
To search the desired record
N/A.
N/A
Post Condition
Actors Involved
Basic Course
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Administrator searches/selects
a record.
3. Administrator press edit button
and edit the record.
5. Administrator press update button.
System Responce
2. System displays the desired record and edit button
enabled.
4. System displays the confirmation message.
6. Record successfully updated.
Table 8: TableHRIS006
53
54
7.Delete
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Delete
HRIS007
Base
Administrator,Operator must be logged in
Record Deleted Successfully
Operators, Administrator
1.Click On Search
2.Search By id or Name
3.Record found and display results
4.Select Record to delete
5.Press Delete Button
6.Record Deleted
Generate Error Message,Record not Selected
To Delete the desired record
Record is in DB.
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Administrator Selects records
which need to be Deleted. .
3. Administrator deletes a form by
selecting/providing valid
unique id or press yes.
System Responce
2. Systems ask/displays the delete confirmation dialogue.
Table 9: TableHRIS007
55
56
8.Print Report
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Print
HRIS008
Base
Desired form should be open
Report Printed Successfully
Operators, Administrator
1.Click On Search
2.Search By id or Name
3.Record found and display results
4.Select Report to Print
5.Press Print Button
6.Report Printed
Generate Error Message,Record not Found
To Print the desired record
Record is in DB.
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Administrator Selects reports
which need to be Printed. .
3. Administrator Print a report by
Pressing Print Button.
System Responce
2. Systems ask/displays the Print confirmation dialogue.
4. System prints report successfully..
57
58
9.Preview
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Preview
HRIS009
Base
Form is available
Report shown
Operators, Administrator
1.Click On Search
2.Search By id or Name
3.Record found and display results
4.Click on Previw button
5.Report shown
Generate Error Message,Record not found
To Preview report of selected record
N/A
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Administrator Selects report
which need to be Previewed .
3. Administrator Press Preview
button.
System Responce
2. Systems check the information and generate a report.
4. System Display the desired report..
59
60
10.Manual Attendance
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Administrator Click on
Attendance .
3. Administrator input valid
information and book on
the Attendance.
Attendance
HRIS010
Base
Administrator,Operator must be logged in
Attendance marked
user,Operators, Administrator
1.Click On Attendance
2.Search By id or Name
3.Record found and display results
4.input Information
5.Press Mark Attendance button
Generate Error Message,ID not found
To Mark Attendance manually of desired user
User is registered.
N/A
System Responce
2. Systems ask/displays desired form .
61
62
11.EDMS Login
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
EDMS Login
HRIS011
Base
Administrator must be logged in
EDMS tool activated Successfully
Administrator
1.Click On EDMS
2.Enter Login name and Password
3.If Successfull Show the tool
4.Otherwise relogin
Generate Error Message,Re-enter information
To use the EDMS tool
Admin is logged into main system
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Administrator Selects EDMS
tool to use. .
3. Administrator Enter valid
username and passowrd
and press login.
System Responce
2. Systems displays a forma and ask for login and
password to enter.
63
64
12.Browse image
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Browse
HRIS012
Base
Administrator must be logged in
image uploaded Successfully
Administrator
1.Click On Browse button
2.Search image from drive
3.Select image and upload it
4.Desired image uploaded successfully
Generate Error Message,Record not Selected
Pick up the scanned image from the disk.
N/A.
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Administrator click browse
button.
3. Administrator select desired
image and press ok
System Responce
2. System displays the system drive.
4. System performs the requested action..
65
66
13.Zooming
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Zoom
HRIS013
Base
Administrator must be logged in
Zoom in/out image
Administrator
1.Click On Browse button
2.Search image from drive
3.Select image and upload it
4.Desired image uploaded successfully
5.Click on Zoom in or Zoom out
6.zoom the desired image
Generate Error Message,Record not Selected
Zoom the scanned image .
N/A.
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Administrator click Zoom
button.
3. Administrator select desired
image and press zoomin
or zoomout
System Responce
2. System displays the option.
67
68
14.Logout/Exit
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. User/admin selects the
log off or exit option
from the menu.
3. User/admin clicks the yes
or ok button..
Logout/Exit
HRIS014
Base
System is Operational and User logged in
Logoff the system Successfully
Administrator,operator,user
1.Click On Logoff button or Exit from the menu
2.Confirmation messages shown
3.Application exit or logged off successfully
Generate Error Message,Record not Selected
To log off or Exit from the System.
N/A.
N/A
System Responce
69
70
15.Connect
Name
Number
Type
Pre Condition
Connect
HRIS015
Base
Reader (Hardware) must be connected with Serial
Port.
Connection has established.
Operator,Administrator
1.Login to system
2.Click on Connect
3.Enter port number
4.Enter Valid information about reader
5.Press connect
6.Connection Established..
Generate Error Message,invalid information or port
number.
To connect application with RF reader.
N/A.
N/A
Post Condition
Actors Involved
Basic Course
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Operator chooses Port type,
and enters some
detailed information
about reader.
3. Administrator/operator Press
connect
System Responce
71
72
16. Disconnect
Name
Number
Type
Pre Condition
Post Condition
Actors Involved
Basic Course
Disconnect
HRIS016
Base
Administrator/operator must be logged in
RF reader connection disconnected
Operator,Administrator
1.Click On Disconnect button
2.Confirmation message displayed
3.Select Yes
4.Connection disconected successfully
Generate Error Message,Connection not Selected
To Disconnect RF reader from application.
N/A.
N/A
Alternative Course
Purpose
Assumptions
Related Use Case
Actors Action
1. Admin/DEO enters his
user name and password.
System Responce
2. System validates the user information and displays
RF reader form.
3. Administrator/DEO Press
Disconnect button.
73
74
3.6
Analysis Model
75
3.7
76
3.8
A domain model can be thought of as a conceptual model of a system which describes the various entities involved in that system and
their relationships. The domain model is created to document the key
concepts and the vocabulary of the system. The model identifies the
relationships among all major entities within the system and usually
identifies their important methods and attributes. This means that
the model provides a structural view of the system which is normally
complemented by the dynamic views in Use Case models. [13]
77
3.9
A Data Flow Diagram is a graphical representation that depicts information flow and the transforms that are applied as data move from
input to output.The basic form of a data flow diagram also known as
a data flow graph. [11]
A DFD May contain different level,level 0, level 1 , level 2 DFD.Every
level is a subfunction the previous level.
78
79
80
81
3.10
82
83
84
3.11
Subsystem Diagram
AHRIS using RFID and Biometrics main system is divided into is subsystems,each subsystem will perform indivisually,Following subsystem
diagram depicts the image of how the main system will work.
85
3.12
Block Diagram
86
CHAPTER IV
DESIGN
4.1
The detailed system architecture and its interaction with other systems can be viewed in
the System Architecture Diagram [11]
4.1.1
Modules of AHRIS
87
88
SubModules of AS system
SubModules of ES system
89
SubModules of PS system
90
91
4.2
Database design is the process of producing a detailed data model of a database. This logical
data model contains all the needed logical and physical design choices and physical storage
parameters needed to generate a design in a Data Definition Language, which can then be
used to create a database. The activities of Database Design transform the requirements
for data storage developed during database analysis into specifications to guide database
implementation. [2]
4.2.1
Design Strategy
AHRIS Using RFID and Biometrics System has adopted the Relational Database Approach
for designing, which has become the dominant technology for Database Management. In
this relational DB data is managed as collection of tables in which all data relationships are
represented by common values in related tables.
4.2.2
Normalization
Normalization is a formal process for deciding which attributes should be grouped together
in a relation. Normalization is primarily a tool to validate and improve a logical design,
so that it satisfies certain constraints that avoid unnecessary duplication of data . [2] The
Database of AHRIS Using RFID and Biometrics System is fully in normalized form as:
All the duplications in tables are removed. All the Insertion, Update and deletion
anomalies are removed.
All the non-key columns depend on the entire primary key. In the case of a composite
primary key, this means that every non-key column do not depend on only part of the
composite key.
Every non key column in a table is mutually independent. Transitive Dependencies
are removed and the Database is in 3NF.
92
4.2.3
List of DB Tables
Following is a list of main tables(excluding sub-tables) of AHRIS ,which are used in Application,
Table Name
Applicants
Application
Appoinment
DailyAtt
Descipline
EDMSpassword
EmpCard
EmpNewstatus
EmpRec
LeaveApp
Login1
PerfRec
EmpNetPay
EmpGrossPay
FinalEmpNetPAy
Description
To Store Personal Record of Applicants Applied for
job.
To Store Record of Applications Applied for job.
To Store Record of Selected Candidates.
To Store Record of Daily Attendance of Employees.
To Store Record of Desciplinary cases of Employees.
To Store Record of Username & pswd for EDMS.
To Store Record of card allocated to Employees.
To Store Record of Employess up to date.
To Store Record of Employees Personal Details.
To Store Record of Employees Leaves.
To Store Record of Security Manager.
To Store Record of Performances of Employees.
To Store Employee Basic Pay.
To Store GrossPays of The Employees.
To Store Final Calculated net pay after addiion of
GrossPAy.
Table 19: List of DB Tables
93
4.2.4
LEAVE
ADMINISTRATION
95
96
97
98
4.3
System architecture alludes to the overall structure of the system and the ways in which
that structure provides conceptual integrity for a system. The primary objective of architectural design is to develop a modular program structure and represent the control
relationship between modules. In addition, architectural design melds program structure
and data structure, defining interfaces that enable data to flow throughout the program.
During construction, design components are implemented in programming language such
as Vb 6.0, Dot Net Framework.
The architectural design provides an excellent technique to improve understanding of
requirements in conceptual model i-e system sequence diagram.
99
4.3.1
100
4.4
Sequence Diagrams
101
102
103
104
105
106
107
108
109
4.5
State-chart Diagrams
Statechart diagrams provide a way to model the various states in which an object can
exist. While the Class diagrams show a static picture of the classes and their relationships,
Statechart diagrams are used to model the more dynamic behavior of a system. These types
of diagrams are extensively used in building real-time systems.
A Statechart diagram shows the behavior of an object.object. It shows the various states
in which an object can exist, what state an object is in when it is created, what state an
object is in when it is destroyed,how an object moves from one state to another, and what
an object does when it is in various states. All of this information helps a developer get
a complete picture of how a particular object should behave.Statechart diagrams do not
need to be created for every class in a model. Classes with significant dynamic behavior,
complex behavior, or behavior that is not well understood among the development team
are good candidates for Statechart diagrams. [16]
State Chart Diagram of AHRIS Using RFID & BM are given below..
110
111
112
113
114
115
4.6
Collaboration Diagrams
116
117
118
119
120
121
122
123
124
4.7
Component Diagram
A component diagram depicts how a software system is split up into physical components
and shows the dependencies among these components. [6]
125
4.8
Deployement Diagram
The deployment diagram depicts a static view of the run-time configuration of processing
nodes and the components that run on those nodes. It shows the hardware for the system,
the software that is installed on that hardware, and the middleware used to connect the
disparate machines to one another. [6]
126
CHAPTER V
IMPLEMENTATION
Implementation refers to the final process of moving the solution from development status
to production status. In this chapter we will discuss about the Tools and Technologies,
Software Components and the methods used for implementation.
127
5.1
The following tools and technologies are used to build the complete AHRIS RFID and BM
System.
Microsoft Visual Studio 2000 Professional Edition
Microsoft Visual Basic 6.0
Microsoft Access 2003
Microsoft Crystal Reports 9.0
UML Diagrammer
Microsoft Visio 2003
Rational Rose 2002
ER Win
Microsoft Office
TeXnicCenter Latex
Adobe Photoshop CS 8
5.2
There are various conversion methods for implementing a system. One has to use the best
that matches the requirements of this system. There are three conversion methods:
Direct Conversion
In this conversion, old system is totally abandoned and the new system becomes completely
operational. This conversion method is useful only for small organizations but for large
organizations it may result into the tremendous setback due to the failure.
Gradual Conversion
128
The technique allows one program at a time to replace an activity of the existing system.
Gradually, the present system is replaced by the newly designed system. Small-scale operations are conducted first to confirm that change over would be successful. The old system
is not used further and the new system is completely taken over. The process continues
until the new system is fully implemented.
Parallel Conversion
This is the technique in which both existing system and new system runs simultaneously
parallel to existing system. Data is processed or moved through systems concurrently and
only when new system is checked out, the operation of an old system is abandoned. It is
believed that the safest approach to conversion is to run both new and the old system at
the same time, until it is satisfactory established that the new system is producing reliable
results.
Adopted Conversion Plan
Most feasible conversion plan, which results best, is the parallel conversion. It is selected
because it provides an opportunity to compare the results of the existing system with those
of the developed system. Another advantage of this technique is that the risk of failure
is covered. Although this implementation will be slightly xpensive, however, the system
would be safe and the procedure should be followed for some time until it is confirmed that
the newly designed system is working perfectly.
5.3
Software Components:
AHRIS RFID & BM System is developed on the basis of 3-tier architecture but without
web services, having three distinctive layers i.e.
User Interface Layer (i.e. , .exe and .frm files)
Business Logic Layer (i.e. .vbp and .Dsr files)
Data Access Layer (i.e. .bas , .mdb files and stored procedure)
129
5.3.1
5.3.1.1
Login:
Login_Click()
Get user input for user id and password.
Verify user id and password.
IF Valid THEN
Maintain session
Redirect to MAin page
ELSE
Displays message that Invalid Login or Password.
ENDIF
5.3.1.2
Change Password:
ChangePassword_Click()
Get input for user login and Password
Update the user password.
Compare the user entered password with the saved one.
IF equal
Displays message "Password changed successfully".
ELSE
Displays message "Invalid Login name or Password".
ENDIF
5.3.1.3
Add Employee:
OnPage_load()
Get All fields
130
IF(EmpId==Valid)
Chck for Last number
Generate auto Employee number
ElSE
msg"Enter Valid Emp ID"
Search_click()
Execute Stored Procedure to search record.
Update_click()
Execute Stored Procedure to Update new record.
Execute procedure to Update edited field.
Save_click()
Execute Stored Procedure Save new record.
Execute procedure to save data as assigned.
Refresh_click()
see all fields empty
Exit_click()
close the page
5.3.1.4
Add Employee:
OnPage_load()
Get All fields
Get All Buttons
All Fields must have valid data enetered
Search_click()
Execute Stored Procedure to search record.
131
Update_click()
Execute Stored Procedure to Update new record.
Execute procedure to Update edited field.
Save_click()
Execute Stored Procedure Save new record.
Execute procedure to save data as assigned.
Refresh_click()
see all fields empty
Exit_click()
close the page
Delete_click()
Execute Stored Procedure Delete Selected record.
5.3.1.5
Attendance:
OnPage_load()
Ask for Empl ID
Ask for Employe Number
All Fields must be active.
BookON_Click()
IF
All fields are Empty
and BOOK on clicked
THEN
Show msg"Enter Data in fields"
ELSE IF(Data==Valid)
Enter Data in all fields
Update Data
ELSE
132
Show Error
BookOff_Click()
Show error msg
Refresh_click()
Empty all fields
Time()
Get current system time
DAte()
Get current date
5.3.1.6
Search
OnPage_load()
show Status
Show Grid
Ask for Empl ID
Ask for Employe Name
All Fields must be active.
Search_Click()
IF(Empno==Valid)
Execute saved search procedures
Search for the result
Display result in Grid form
Fill required fields
Else
Show error msg"Invalid ID"
Exit_Click()
Close the form.
133
Refresh_click()
Empty all fields
5.3.1.7
Reports
OnPage_load()
Click on required reports
Show Grid
Ask for Empl ID
Ask for Employe Name
All Fields must be active.
Print_Click()
IF(Empno==Valid)
Execute .dsr procedures
Search for the result
Display result in Grid form
Send for Print
Else
Show error msg"Invalid ID"
Exit_Click()
Close the form.
Preview_click()
Show .dsr Designs.
5.3.1.8
EDMS
OnPage_load()
Ask for login
login()
Ask for PAssword
password()
134
IF(Login==Success)
Show Main Screen
Show All fields
ElSE
Show error
NewScan_Click()
IF(Empno==Valid)
Search for drives
Select Document
Upload it
Else
Show error msg"Invalid ID"
Exit_Click()
Close the form.
Print_click()
Print the selected Document.
HElp_click()
Show Help
View_click()
View Selected Document.
Zoom_click()
Enlarge the screen by zooming.
Database_click()
Show Available Documents
5.3.2
BLL Method
5.3.2.1
Applicants list()
135
Return dataReader.
5.3.2.2
Employees dropdownlist ()
Delete (ID)
Add()
Else
Add record in the table
Update database.
IF Record added successfully
Display confirmation.
ENDIF
ENDIF
136
5.3.2.5
PopulateEditField(ID)
DAL Methods:
5.3.3.1
DataAccess()
5.3.3.2
ExecuteReturnValue()
Execute query and return data.
5.3.3.3
OpenConnection()
CloseConnection()
DisposeConnection()
IF (Connection Not null)
Dispose connection.
Set connection == null.
137
ENDIF
5.3.3.6
CreateAdapter()
Set Adapter =
return Adapter
5.3.3.7
CreateCommand()
Command.CommandText = procedureName.
ExecuteDataReader()
138
CHAPTER VI
TESTING
Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design, and coding.Most of the time software projects are
not estimated properly and tend to run behind schedule. When it comes to meeting the
deadline, people seem to ignore a very important phase in the whole process testing. But
our project Automated Human Resource Information System Using RFID and Biometrics
for DHA has been thoroughly tested.
System testing is an essential step for the development of a reliable and error-free system.
Testing is a process of executing a program with the explicit intension of finding errors but
this does not mean to embarrass the programmer or fail the product but the positive
intention to remove as many problems from the system. A test case is a set of data items
that the system processes as normal input. Good testing involves much more than just
running the program a few times to see whether it works.
Testing has an important place in SDLC (Software Development Life Cycle). The SQA
(Software Quality Assurance) team should be involved in the early phases of the project.
This will make them aware of the requirements and techniques that are being followed
enabling them to develop an appropriate test strategy.
The marketing group will bring the customer requirement.
The engineering group will access the feasibility.
The engineering and SQA groups will work together during the design phase and
generate the product specification.
The developers will start implementing while the SQA team is developing the test
plans and so on.
139
While the developers are ready with the code, the SQA team will be ready for
testing. The testing phase is no longer a bottleneck for product delivery because the
SQA team has been involved since the start of the project.
6.1
Black-box testing technique does not concern with the internal coding. But it checks the
functionality of the software. The software is executed without examining the code. The
tester acts as an end user and tries to find bugs.
6.1.2
In white box testing the tester is concerned with the internal coding of the software. In
this strategy the code is examined without being executed. White box testing is concerned
only with testing the software product; it cannot guarantee that the complete specification
has been implemented. Black box testing is concerned only with testing the specification; it
cannot guarantee that all parts of the implementation have been tested. White box testing
can indicate test considerations, which are not produced by black box testing. The converse
is also true; black box testing can produce test considerations, which are not produced by
white box testing.
140
6.1.3
Path Testing
A path is a sequence of operations that runs from the start of the program to an exit point.
This is also called an end-to-end path. Path testing is concerned with testing paths of the
software.There are three converge criteria in path testing.Line converge requires execution
of every line of code at least once. Branch converge requires testing of all lines and all
branches. Condition converge requires each ways of the condition can be made true or
false.
6.1.4
Regression Testing
It is very important testing technique. In this testing technique the old tests are tested
again. This can be performed after black box or white box testing.
6.1.5
Unit Testing
Unit testing is testing the individual units of software. In an Object Oriented Software
program these can be individual classes.
6.1.6
System Testing
In System Testing all the units of the software are combined and tested as an integrated
system.
6.1.7
Acceptance Testing
The acceptance testing is a process to verify the readiness of the software for implementation
or use. The software is checked for completeness that whether it is ready or not. After
successful completion of acceptance testing the software is ready and can be exported.
6.2
141
6.3
142
Prerequistie
Action to perform
Expected Results
The system should give
an error message indicating
that the User ID is incorrect
Comments
Fail
Database might not be connected!!
Prerequistie
Action to perform
Expected Results
The system should give
an error message indicating
that the Password is incorrect
Comments
Pass
Database has been reconnected..
143
Prerequistie
Action to perform
Expected Results
The system should show
main screen but no
option should be active
Comments
Fail
Admin didnt assign Blank login properties..
Prerequistie
Action to perform
Expected Results
The system should show
Main screen with all
Options active
Comments
Pass
Everything Working Excellently!!
144
Prerequistie
Action to perform
Expected Results
The system should display
an error message indicating
that the Old password is incorrect
Comments
Pass
Test case was done correctly..
Prerequistie
Action to perform
Expected Results
The system should display
message indicating that
Password hase been changed
Comments
Pass
Exceptional handling worked..
145
Expected Results
The system should display
an error message indicating
that the Necassary information
are not entered.
Comments
Pass
Exceptional Handling worked well..
Expected Results
The system should display
a message indicating
that data is updated.
Comments
Pass
Everything worked correctly..
146
Expected Results
The system should display
an error message indicating
that some fields are missing
Comments
Fail
Some problem in exceptional handling..corrected after this test case.
Expected Results
The system should display
a message indicating
that records are saved
Comments
Pass
Data saved in correct fields of table..
147
Prerequistie
Action to perform
Expected Results
The system should display
an error message indicating
that Record not found
Comments
Pass
OK
Prerequistie
Action to perform
Expected Results
The system should display
required results
Comments
148
Expected Results
The system should display
an error message indicating
that Printer is not connected
Comments
Fail
Application closed showing exceptional error..
Expected Results
The system should display
a message indicating
that DAta Printing..
Comments
Pass
OK..
149
Expected Results
The system should display
an error message indicating
that Empl ID is incorrect
Comments
Pass
Everything worked properly..
Expected Results
The system should display
a message indicating
that Attendance updated.
Comments
Pass
OK
150
Prerequistie
Action to perform
Expected Results
The system should display
an error message indicating
that ID or Pswd is incorrect
Comments
Fail
Not logged in with ADministrator rights..
Prerequistie
Action to perform
Expected Results
The system should display
EDMS Main Screen
Comments
151
152
Expected Results
The system should display
a error message indicating
Data is invalid
Comments
Pass
Dialog box appear..
Expected Results
The system should display
message that connection
successfully established.
Comments
PAss
OK..device connected
153
CHAPTER VII
CONCLUSION
The Software developed was the requirement of organization. This software has been developed using industry standard tools & technologies. The software is flexible enough to be
modified easily for further needs. If we compare the new procedure with the existing system
I would have no doubt in saying that by using the software DHA isb will attain a remarkable
success. AHRIS using RFID and Biometrics System also interacts with two other Systems,
AS System and PS System. These three systems use one centralized Database.The system
is fully evaluated but generally it produces information that posses the properties of accuracy, completeness, timeliness and conciseness. Some of the measurable human factors that
are central in evaluation are ease of use, speed of performance and rate of errors.
Due to the time constraints to the submission of this project the system could not be
fully evaluated, but By the Grace of Allmighty Allah and hard work this system is fully
evaluated and generally it produces information that posses the properties of accuracy,
completeness, timeliness and conciseness.
All the factors mentioned above do not guarantee a unique interface and each software
no matter how carefully designed and implemented has got its respective pros and cons.
The ones associated with our software are mentioned below:
7.1
There are no cons of this software. The Pros of this software are as follows:
The software is more reliable and consistent than existing system because it produces
accurate results without any loss of data.
The software provides interface for friendly communication between the user and the
system.
154
Software provides complete security involves validating user credentials (authentication) and determining access to resources (authorization).
Software is fault tolerant and efficient.
The rate of errors is considerably reduced as forms and reports are used and data
validation checks have been provided to ensure correct storage of information.
The software provides information in the form of printable reports, which helps the
users in making timely decision.
The software also generates proper error messages for the convenience of the user.
This enables the users to interact more easily with this software.
7.2
Software Requirements
7.3
Hardware Requirements
156
APPENDIX A
A.1
Istallation,User Manual(Interface)
This section Describe a detailed view of User Interface design(User Manual),How to use the
Application.All Screenshots are from Origional version of the Application.
1.Double Click on the prjHRIS.exe to start the Application. 2.A Splash Screen Will
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
APPENDIX B
SOURCE CODE
Here source code of AHRIS using RFID and BM is given in commented() form.All code is
shown by dividing it into functions.All the main modules code is covered Excluding small
chunks.
Authentication(security Manager)
Option Explicit
Dim con As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim srno As Integer
188
189
frmRpPerf.Show
End Sub
190
End Sub
191
End Sub
192
End Sub
End Sub
193
Unload Me
frmLogin.Show
End If
End Sub
194
195
Else
mdiMain.Admin.Enabled = False
End If
If a = 1 Then
mdiMain.Def.Enabled = True
Else
mdiMain.Def.Enabled = False
End If
If bb = 1 Then
mdiMain.Applications.Enabled = True
Else
mdiMain.Applications.Enabled = False
End If
If c = 1 Then
mdiMain.EmpRec.Enabled = True
Else
mdiMain.EmpRec.Enabled = False
End If
If d = 1 Then
mdiMain.LeaveAdmin.Enabled = True
Else
mdiMain.LeaveAdmin.Enabled = False
End If
If e = 1 Then
mdiMain.Performance.Enabled = True
Else
mdiMain.Performance.Enabled = False
196
End If
If f = 1 Then
mdiMain.Payroll.Enabled = True
Else
mdiMain.Payroll.Enabled = False
End If
If g = 1 Then
mdiMain.RecSear.Enabled = True
Else
mdiMain.RecSear.Enabled = False
End If
If h = 1 Then
mdiMain.Reports.Enabled = True
Else
mdiMain.Reports.Enabled = False
End If
If i = 1 Then
mdiMain.EDMS.Enabled = True
Else
mdiMain.EDMS.Enabled = False
End If
mdiMain.Admini = True
mdiMain.Menu = False
End Sub
197
198
frmPromotion.Show
End Sub
199
End Sub
200
Recruitment Manager
Option Explicit
Dim con As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim srno As Integer
desig", myConnection, 1, 1
txtSrNo.Text = ""
cmbTitle.Text = "[Select One]"
txtName.Text = ""
201
txtFName.Text = ""
MEBDOB = "
MEBCNIC = "
"
-
- "
txtNationality.Text = ""
cmbGender.Text = "[Select One]"
cmbMStatus.Text = "[Select One]"
cmbReligion.Text = "[Select One]"
cmbSect.Text = "[Select One]"
cmbDomicile.Text = "[Select One]"
txtDistrict.Text = ""
MEBDOA = "
MEBPhone = "
"
MEBMobile = "
"
-
"
txtEmail.Text = ""
txtImage.Text = ""
txtMAddress.Text = ""
txtPAddress.Text = ""
cmbCat.Text = "[Select One]"
cmbDte.Text = "[Select One]"
cmbAppoint.Text = "[Select One]"
txtExp.Text = "0"
MEBDOI = "
"
txtMinAge.Text = ""
txtMaxAge.Text = ""
cmbQual.Text = "[Select One]"
txtRemarks.Text = ""
txtCert.Text = ""
txtInst.Text = ""
cmbTitle.SetFocus
End Sub
202
txtSrNo.Text = ""
cmbTitle.Text = "[Select One]"
txtName.Text = ""
txtFName.Text = ""
MEBDOB = "
MEBCNIC = "
"
-
- "
txtNationality.Text = ""
cmbGender.Text = "[Select One]"
cmbMStatus.Text = "[Select One]"
cmbReligion.Text = "[Select One]"
cmbSect.Text = "[Select One]"
cmbDomicile.Text = "[Select One]"
203
txtDistrict.Text = ""
MEBDOA = "
MEBPhone = "
"
MEBMobile = "
"
-
"
txtEmail.Text = ""
txtImage.Text = ""
txtMAddress.Text = ""
txtPAddress.Text = ""
cmbCat.Text = "[Select One]"
cmbDte.Text = "[Select One]"
cmbAppoint.Text = "[Select One]"
txtExp.Text = "0"
MEBDOI = "
"
txtMinAge.Text = ""
txtMaxAge.Text = ""
cmbQual.Text = "[Select One]"
txtRemarks.Text = ""
txtCert.Text = ""
txtInst.Text = ""
cmbTitle.SetFocus
End Sub
204
205
txtSrNo.Text = ""
cmbTitle.Text = "[Select One]"
txtName.Text = ""
txtFName.Text = ""
MEBDOB = "
MEBCNIC = "
"
-
- "
txtNationality.Text = ""
cmbGender.Text = "[Select One]"
cmbMStatus.Text = "[Select One]"
cmbReligion.Text = "[Select One]"
cmbSect.Text = "[Select One]"
cmbDomicile.Text = "[Select One]"
txtDistrict.Text = ""
MEBDOA = "
MEBPhone = "
"
MEBMobile = "
"
-
"
txtEmail.Text = ""
txtImage.Text = ""
txtMAddress.Text = ""
txtPAddress.Text = ""
cmbCat.Text = "[Select One]"
cmbDte.Text = "[Select One]"
cmbAppoint.Text = "[Select One]"
txtExp.Text = "0"
MEBDOI = "
"
txtMinAge.Text = ""
txtMaxAge.Text = ""
206
End Sub
207
txtSrNo.Text = ""
cmbTitle.Text = "[Select One]"
txtName.Text = ""
txtFName.Text = ""
MEBDOB = "
MEBCNIC = "
"
-
- "
txtNationality.Text = ""
cmbGender.Text = "[Select One]"
cmbMStatus.Text = "[Select One]"
cmbReligion.Text = "[Select One]"
cmbSect.Text = "[Select One]"
cmbDomicile.Text = "[Select One]"
txtDistrict.Text = ""
MEBDOA = "
MEBPhone = "
"
MEBMobile = "
"
-
"
txtEmail.Text = ""
txtImage.Text = ""
txtMAddress.Text = ""
txtPAddress.Text = ""
cmbCat.Text = "[Select One]"
cmbDte.Text = "[Select One]"
cmbAppoint.Text = "[Select One]"
txtExp.Text = "0"
MEBDOI = "
"
txtMinAge.Text = ""
txtMaxAge.Text = ""
cmbQual.Text = "[Select One]"
txtRemarks.Text = ""
txtCert.Text = ""
txtInst.Text = ""
cmbTitle.SetFocus
208
End Sub
If k = 1 Then
cmdDelete.Enabled = True
Else
cmdDelete.Enabled = False
End If
If l = 1 Then
cmdUpdate.Enabled = True
Else
cmdUpdate.Enabled = False
End If
If m = 1 Then
cmdSearch.Enabled = True
Else
cmdSearch.Enabled = False
End If
If n = 1 Then
cmdRefresh.Enabled = True
209
Else
cmdRefresh.Enabled = False
End If
If o = 1 Then
cmdExit.Enabled = True
Else
cmdExit.Enabled = False
End If
cmbDte.AddItem Rs.Fields("Dte")
Rs.MoveNext
Loop
End If
210
End Sub
Employee Manager
Connect Setting
Option Explicit
Dim con As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim srno As Integer
211
txtDteID.Text = "3959"
End If
End If
End If
212
End If
End Sub
213
txtDOB.Text = ""
txtCNIC.Text = ""
txtNationality.Text = ""
txtGender.Text = ""
txtMStatus.Text = ""
txtReligion.Text = ""
txtSect.Text = ""
txtDomicile.Text = ""
txtDistrict.Text = ""
txtPhone.Text = ""
txtMobile.Text = ""
txtEmail.Text = ""
imgPic.Picture = LoadPicture("")
txtMAddress.Text = ""
txtPAddress.Text = ""
txtCat.Text = ""
txtDte.Text = ""
txtAppoint.Text = ""
DTPDOJ.Refresh
cmbPayScale.Text = "[Select One]"
txtEmpId.SetFocus
End Sub
Updating Data
Private Sub cmdUpdate_Click()
myConnection.Execute "Update EmpRec Set Emp=" & Trim(txtEmp.Text) & ",DteID="
& Trim(txtDteID.Text) & ",OffID=" & Trim(txtOffID.Text) & ",ElecNo="
& Trim(txtElecNo.Text) & ",EmpId=" & Trim(txtEmpId.Text) & ",Title="
& Trim(txtTitle.Text) & ",Name=" & Trim(txtName.Text) & ",FName="
& Trim(txtFName.Text) & ",DOB=" & Trim(txtDOB.Text) & ",CNIC="
& Trim(txtCNIC.Text) & ",Nationality=" & Trim(txtNationality.Text) & ",Gender="
& Trim(txtGender.Text) & ",MStatus=" & Trim(txtMStatus.Text) & ",Religion="
& Trim(txtReligion.Text) & ",Sect=" & Trim(txtSect.Text) & ",Domicile="
214
..................................................................................
Dim Status As Integer
Status = 0
txtSrNo.Text = ""
txtEmp.Text = ""
txtDteID.Text = ""
txtOffID.Text = ""
txtElecNo.Text = ""
txtEmpId.Text = ""
txtTitle.Text = ""
215
txtName.Text = ""
txtFName.Text = ""
txtDOB.Text = ""
txtCNIC.Text = ""
txtNationality.Text = ""
txtGender.Text = ""
txtMStatus.Text = ""
txtReligion.Text = ""
txtSect.Text = ""
txtDomicile.Text = ""
txtDistrict.Text = ""
txtPhone.Text = ""
txtMobile.Text = ""
txtEmail.Text = ""
imgPic.Picture = LoadPicture("")
txtMAddress.Text = ""
txtPAddress.Text = ""
txtCat.Text = ""
txtDte.Text = ""
txtAppoint.Text = ""
DTPDOJ.Refresh
cmbPayScale.Text = "[Select One]"
txtEmpId.SetFocus
End Sub
216
217
txtMobile = Rs.Fields("Mobile")
txtEmail.Text = Rs.Fields("Email")
End Sub
Leave Manager
Option Explicit
Dim con As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim srno As Integer
218
txtPAddress.Text = ""
txtPerAddress.Text = ""
cmbLType.Text = "[Select One]"
MEBDate = "
"
DTP1.Value = Date
DTP2.Value = Date
txtTotal.Text = ""
txtEmpID.SetFocus
End Sub
txtEmpID.Text = ""
txtCat.Text = ""
txtDte.Text = ""
txtAppoint.Text = ""
txtName.Text = ""
txtDOE.Text = ""
txtPAddress.Text = ""
txtPerAddress.Text = ""
cmbLType.Text = "[Select One]"
MEBDate = "
"
DTP1.Value = Date
DTP2.Value = Date
txtTotal.Text = ""
219
txtEmpID.SetFocus
End Sub
"
DTP1.Value = Date
DTP2.Value = Date
txtTotal.Text = ""
220
txtEmpID.SetFocus
End If
End Sub
txtEmpID.Text = ""
txtCat.Text = ""
txtDte.Text = ""
txtAppoint.Text = ""
txtName.Text = ""
txtDOE.Text = ""
txtPAddress.Text = ""
txtPerAddress.Text = ""
cmbLType.Text = "[Select One]"
MEBDate = "
"
DTP1.Value = Date
DTP2.Value = Date
txtTotal.Text = ""
txtSrNo.Text = ""
txtEmpID.SetFocus
End Sub
Private Sub Command1_Click()
221
Availed = 0
Availed1 = 0
JYear = Year(txtDOE.Text)
JMonth = MOnth(txtDOE.Text)
JDays = Day(txtDOE.Text)
CYear = Year(DTP1.Value)
CMonth = MOnth(DTP1.Value)
CDays = Day(DTP1.Value)
222
Wend
Wend
Label18.Caption = a
Earned Leaves.......................................................................
223
224
End Sub
225
End If
End Sub
End Sub
txtPAddress.Text = Rs.Fields("MAddress")
txtPerAddress.Text = Rs.Fields("PAddress")
Else
MsgBox "Record not found..."
End If
End Sub
226
Attendance Manager
Option Explicit
Dim con As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim srno As Integer
If B = "0" Then
227
txtEmpNo.Text = ""
txtCat.Text = ""
txtEmpID.Text = ""
txtDteID.Text = ""
txtOffID.Text = ""
txtElecNo.Text = ""
lblName.Caption = ""
lblAppoint.Text = ""
txtDte.Text = ""
lblResult.Caption = ""
lblResult.BackColor = &HC0C0C0
imgPic.Picture = LoadPicture("")
txtEmpNo.SetFocus
Else
MsgBox "Already Booked Off...", vbInformation, App.ProductName
txtEmpNo.Text = ""
txtCat.Text = ""
txtEmpID.Text = ""
txtDteID.Text = ""
txtOffID.Text = ""
txtElecNo.Text = ""
lblName.Caption = ""
lblAppoint.Text = ""
txtDte.Text = ""
txtEmpNo.SetFocus
End If
End Sub
228
Dim a As String
Dim B As String
a = Rs.Fields("EmpNo")
B = Rs.Fields("Date1")
Rs.MoveNext
srno = srno + 1
Wend
End If
txtEmpNo.Text = ""
txtCat.Text = ""
txtEmpID.Text = ""
txtDteID.Text = ""
txtOffID.Text = ""
txtElecNo.Text = ""
lblName.Caption = ""
lblAppoint.Text = ""
229
txtDte.Text = ""
lblResult.Caption = ""
lblResult.BackColor = &HC0C0C0
imgPic.Picture = LoadPicture("")
txtEmpNo.SetFocus
Else
If txtEmpNo.Text = "" Then
MsgBox "Please Enter Employee No...", vbInformation, App.ProductName
Else
myConnection.Execute "Insert into DailyAtt (EmpNo,Cat,EmpID,
DteID,OffID,ElecNo,Name,
Appoint,Dte,Pic,Date1,Time1,Time2)
Values(" & Trim(txtEmpNo.Text) & ","
Trim(txtCat.Text) & "," & Trim(txtEmpID.Text)
& "," & Trim(txtDteID.Text)& ","
& Trim(txtOffID.Text) & ","
& Trim(txtElecNo.Text) & "," & Trim(lblName.Caption) & ","
&Trim(lblAppoint.Text) & "," & Trim(txtDte.Text)
& "," & Trim(txtEmpNo.Text) & "," & Trim(DTPicker1) & ","
& Trim(lblTime.Caption) & "," & Trim(0) & ")"
MsgBox "Record Saved Successfully...", vbInformation, App.ProductName
lblResult.BackColor = &H4000&
lblResult.Caption = ""
MsgBox "Booked on... Successfully, Good Morning", vbInformation, App.ProductName
txtEmpNo.Text = ""
txtCat.Text = ""
txtEmpID.Text = ""
txtDteID.Text = ""
txtOffID.Text = ""
txtElecNo.Text = ""
230
lblName.Caption = ""
lblAppoint.Text = ""
txtDte.Text = ""
lblResult.Caption = ""
lblResult.BackColor = &HC0C0C0
imgPic.Picture = LoadPicture("")
txtEmpNo.SetFocus
End If
End If
End Sub
txtEmpNo.Text = ""
txtCat.Text = ""
txtEmpID.Text = ""
txtDteID.Text = ""
txtOffID.Text = ""
txtElecNo.Text = ""
lblName.Caption = ""
lblAppoint.Text = ""
txtDte.Text = ""
lblResult.Caption = ""
lblResult.BackColor = &HC0C0C0
imgPic.Picture = LoadPicture("")
txtEmpNo.SetFocus
End Sub
231
DTPicker1 = Date
End Sub
End Sub
MsgBox "The person is no more on job... Please contact Dir HR", vbInformation, App.ProductNam
Else
txtEmpNo.Text = Rs.Fields("EmpID")
txtCat.Text = Rs.Fields("Cat")
232
txtEmpID.Text = Rs.Fields("Emp")
txtDteID.Text = Rs.Fields("DteID")
txtOffID.Text = Rs.Fields("OffID")
txtElecNo.Text = Rs.Fields("ElecNo")
lblName.Caption = Rs.Fields("Name")
lblAppoint.Text = Rs.Fields("Appoint")
txtDte.Text = Rs.Fields("Dte")
imgPic.Picture = LoadPicture("")
On Error Resume Next
imgPic.Picture = LoadPicture(App.Path & "\Pics\" & Rs.Fields("EmpID") & ".jpg")
Err.Clear
End If
Else
MsgBox "Record not found..."
End If
End Sub
Side Bar
Private Sub Command1_Click()
Shell "Notepad.exe", vbNormalFocus
End Sub
Private Sub Command2_Click()
Shell "calc.exe", vbNormalFocus
End Sub
233
Unload mdiMain
End Sub
End Sub
234
txtEmpNo.Text = ""
txtCat.Text = ""
txtName.Text = ""
txtAppoint.Text = ""
txtDte.Text = ""
txtDOJ.Text = ""
txtFrom.Text = ""
txtTo.Text = ""
cmbAG.Text = "[Select One]"
txtStr.Text = ""
txtWeakness.Text = ""
cmbRecPro.Text = "[Select]"
DTP1.Value = Date
cmbPartII.Text = "[Select One]"
cmbPartIII.Text = "[Select One]"
cmbHR.Text = "[Select One]"
txtYear.Text = ""
txtEmpNo.SetFocus
235
End Sub
236
If a = txtYear.Text Then
MsgBox "Record Already Exists....", vbInformation, App.ProductName
Else
txtEmpNo.Text = ""
txtCat.Text = ""
txtName.Text = ""
txtAppoint.Text = ""
txtDte.Text = ""
txtDOJ.Text = ""
txtFrom.Text = ""
txtTo.Text = ""
cmbAG.Text = "[Select One]"
txtStr.Text = ""
txtWeakness.Text = ""
cmbRecPro.Text = "[Select]"
DTP1.Value = Date
cmbPartII.Text = "[Select One]"
cmbPartIII.Text = "[Select One]"
cmbHR.Text = "[Select One]"
237
txtYear.Text = ""
txtEmpNo.SetFocus
End If
End Sub
txtEmpNo.Text = ""
txtCat.Text = ""
txtName.Text = ""
txtAppoint.Text = ""
txtDte.Text = ""
txtDOJ.Text = ""
txtFrom.Text = ""
txtTo.Text = ""
cmbAG.Text = "[Select One]"
txtStr.Text = ""
txtWeakness.Text = ""
cmbRecPro.Text = "[Select]"
DTP1.Value = Date
cmbPartII.Text = "[Select One]"
cmbPartIII.Text = "[Select One]"
cmbHR.Text = "[Select One]"
txtYear.Text = ""
txtEmpNo.SetFocus
238
End Sub
DTP1.Value = Date
If j = 1 Then
cmdSave.Enabled = True
Else
cmdSave.Enabled = False
End If
If k = 1 Then
cmdDelete.Enabled = True
Else
cmdDelete.Enabled = False
End If
If l = 1 Then
cmdUpdate.Enabled = True
Else
cmdUpdate.Enabled = False
End If
If m = 1 Then
cmdSearch.Enabled = True
Else
cmdSearch.Enabled = False
239
End If
If n = 1 Then
cmdRefresh.Enabled = True
Else
cmdRefresh.Enabled = False
End If
If o = 1 Then
cmdExit.Enabled = True
Else
cmdExit.Enabled = False
End If
End Sub
240
..................
Else
MsgBox "Record not found..."
End If
End Sub
Search manager
Private Sub cmdRefresh_Click()
txtEmpNo.Text = ""
txtCat.Text = ""
txtDte.Text = ""
txtAppoint.Text = ""
txtName.Text = ""
txtPayScale.Text = ""
txtDOJ.Text = ""
txtProcess.Text = ""
txtStatus.Text = ""
txtEStatus.Text = ""
txtIssued.Text = ""
txtExpires.Text = ""
txtDDate.Text = ""
txtCStatus.Text = ""
txtReason.Text = ""
241
txtExtended.Text = ""
txtSC.Text = ""
txtWarning.Text = ""
txtDOB.Text = ""
txtEmpNo.SetFocus
con.Open strConnString
MSFlexGrid.FormatString = "ID
& vbTab & "From
& vbTab & "Total
"
MSFlexGrid.Rows = 1
srno = 1
End Sub
242
"
"
SC = 0
Warning = 0
Advice = 0
Cancel = 0
End If
End If
243
End If
End If
244
245
con.Open strConnString
MSFlexGrid.FormatString = "ID
& vbTab & "From
& vbTab & "Total
"
"
"
MSFlexGrid.Rows = 1
srno = 1
While Not Rs.EOF
MSFlexGrid.AddItem srno & vbTab & Rs!LTypes & vbTab & Rs!From1
& vbTab & Rs!To1 & vbTab & Rs!Total
Rs.MoveNext
srno = srno + 1
Wend
Rs.Close
Set Rs = Nothing
End Sub
246
End Sub
con.Open strConnString
MSFlexGrid.FormatString = "ID
"
"
MSFlexGrid.Rows = 1
srno = 1
End Sub
Option Explicit
Dim con As ADODB.Connection
247
Dim Rs As ADODB.Recordset
Dim srno As Integer
End Sub
a = 0
Availed = 0
Remaining = 0
Comulated = 0
248
End If
End If
Wend
249
End Sub
frmLeavecal.Show
frmLeavecal.txtEmpNo.Text = txtEmpNo.Text
frmLeavecal.txtName.Text = txtName.Text
frmLeavecal.txtAppoint.Text = txtAppoint.Text
End Sub
250
CMonth = MOnth(DTP1.Value)
CYear = Year(DTP1.Value)
251
252
End Sub
con.Open strConnString
MSFlexGrid.FormatString = "ID
" & vbTab & "Applied On
& vbTab & "To
MSFlexGrid.Rows = 1
DTP1.Value = Date
DTP2.Value = Date
253
"
"
Rs.MoveNext
Loop
End If
End Sub
Text1.Visible = True
Text1.Text = Grid1.Text
Dim irow, icol As Integer
End Sub
254
Else
MsgBox "Record not found..."
End If
con.Open strConnString
MSFlexGrid.FormatString = "ID
& vbTab & "Applied On
& vbTab & "To
255
"
"
"
MSFlexGrid.Rows = 1
srno = 1
While Not Rs.EOF
Rs.MoveNext
srno = srno + 1
Wend
Rs.Close
Set Rs = Nothing
End Sub
Module
Public myConnection As ADODB.Connection
256
Public k As Integer
Public l As Integer
Public m As Integer
Public n As Integer
Public o As Integer
Public gCrystalObj As Object
mdiMain.Show
End Sub
EDMS Manager
Option Explicit
Dim con As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim srno As Integer
Dim a As Integer
Dim fso As New FileSystemObject
257
frmCabinet.Show
End Sub
con.Open strConnString
258
MSFlexGrid2.FormatString = "ID
"
"
" & vbTab & "PA No
End Sub
259
txtCabinet.Text = ""
End Sub
260
End Sub
Text1.Text = ""
Dir1.Path = "H:\PSDte\PS1\Img\"
con.Open strConnString
MSFlexGrid.FormatString = "ID
MSFlexGrid.Rows = 1
srno = 1
While Not Rs.EOF
Rs.Close
261
"
Set Rs = Nothing
con.Open strConnString
MSFlexGrid2.FormatString = "ID
& vbTab & "Emp No
"
End Sub
Dim a As String
Dim B As String
If MSFlexGrid.MouseRow = 0 Or MSFlexGrid.MouseCol = 0 Then
Text1.Visible = False
Exit Sub
262
End If
Text1.Text = ""
Text1.Visible = True
Text1.Text = Grid1.Text
Dim irow, icol As Integer
txtFile_No.SetFocus
myConnection.CommitTrans
Exit Sub
errorH:
myConnection.RollbackTrans
MsgBox "Please Select Cabinet... " + Err.Description, vbCritical + vbOK
con.Open strConnString
263
MSFlexGrid2.FormatString = "ID
& vbTab & "Emp No
"
MSFlexGrid2.Rows = 1
srno = 1
While Not Rs.EOF
MSFlexGrid2.AddItem srno & vbTab & Rs!Cat & vbTab & Rs!EmpID & vbTab
& Rs!Name & vbTab & Rs!FName & vbTab & Rs!CNIC & vbTab & Rs!DOB
Rs.MoveNext
srno = srno + 1
Wend
Rs.Close
Set Rs = Nothing
End Sub
Dim a As String
Dim B As String
If MSFlexGrid2.MouseRow = 0 Or MSFlexGrid2.MouseCol = 0 Then
Text1.Visible = False
264
Exit Sub
End If
Text1.Text = ""
Text1.Visible = True
Text1.Text = Grid1.Text
Dim irow, icol As Integer
txtFile_No.SetFocus
myConnection.CommitTrans
Exit Sub
errorH:
myConnection.RollbackTrans
MsgBox "Please Select Cabinet... " + Err.Description, vbCritical + vbOK
If txtFile_No = "DHO" Then
Dir1.Path = "\\Server\hr dte$\HR\EDMS\"
If Text1.Text <> "" Then
If fso.FolderExists("\\Server\hr dte$\HR\EDMS\" & Text1.Text) Then
File1.Path = "\\Server\hr dte$\HR\EDMS\" & Text1.Text
Else
MsgBox "Required Record not found....", vbInformation, App.ProductName
End If
End If
End If
Else
265
End Sub
266
End If
End If
End Sub
267
con.Open strConnString
MSFlexGrid.FormatString = "ID
MSFlexGrid.Rows = 1
srno = 1
While Not Rs.EOF
Rs.Close
Set Rs = Nothing
End Sub
268
"
con.Open strConnString
MSFlexGrid2.FormatString = "ID
& "Rank
"
"
" & vbTab
"
"
"
" & vbTab
"
"
"
"
"
"
"
MSFlexGrid2.Rows = 1
srno = 1
While Not Rs.EOF
269
& Rs!Cabinet & vbTab & Rs!PA_No & vbTab & Rs!Rank & vbTab
& Rs!Svc_Status & vbTab & Rs!Unit_Fmn & vbTab & Rs!Name
& vbTab & Rs!Arm_Svc & vbTab & Rs!PA_No_2 & vbTab & Rs!Rank_2
& vbTab & Rs!Svc_Status_2 & vbTab & Rs!Unit_Fmn_2 & vbTab
& Rs!Name_2 & vbTab & Rs!Arm_Svc_2 & vbTab & Rs!PA_No_3
& vbTab & Rs!Rank_3 & vbTab & Rs!Svc_Status_3 & vbTab
& Rs!Unit_Fmn_3 & vbTab & Rs!Name_3 & vbTab & Rs!Arm_Svc_3
& vbTab & Rs!PA_No_4 & vbTab & Rs!Rank_4 & vbTab
& Rs!Svc_Status_4 & vbTab & Rs!Unit_Fmn_4 & vbTab & Rs!Name_4
& vbTab & Rs!Arm_Svc_4 & vbTab & Rs!PA_No_5 & vbTab & Rs!Rank_5
& vbTab & Rs!Svc_Status_5 & vbTab & Rs!Unit_Fmn_5 & vbTab
& Rs!Name_5 & vbTab & Rs!Arm_Svc_5 & vbTab & Rs!Award_Year
& vbTab & Rs!Cat_of_Award
Rs.MoveNext
srno = srno + 1
Wend
Rs.Close
Set Rs = Nothing
End Sub
con.Open strConnString
270
MSFlexGrid2.FormatString = "ID
& vbTab & "Emp No
"
"
MSFlexGrid2.Rows = 1
srno = 1
While Not Rs.EOF
Rs.Close
Set Rs = Nothing
End Sub
271
con.Open strConnString
MSFlexGrid2.FormatString = "ID
"
& vbTab & "Cabinet
& "Rank
"
"
MSFlexGrid2.Rows = 1
srno = 1
While Not Rs.EOF
"
272
"
"
"
"
"
& vbTab & Rs!Cabinet & vbTab & Rs!PA_No & vbTab
& Rs!Rank & vbTab & Rs!Svc_Status & vbTab & Rs!Unit_Fmn
& vbTab & Rs!Name & vbTab & Rs!Arm_Svc & vbTab
& Rs!PA_No_2 & vbTab & Rs!Rank_2 & vbTab & Rs!Svc_Status_2
& vbTab & Rs!Unit_Fmn_2 & vbTab & Rs!Name_2 & vbTab
& Rs!Arm_Svc_2 & vbTab & Rs!PA_No_3 & vbTab & Rs!Rank_3 & vbTab
& Rs!Svc_Status_3 & vbTab & Rs!Unit_Fmn_3 & vbTab & Rs!Name_3
& vbTab & Rs!Arm_Svc_3 & vbTab & Rs!PA_No_4 & vbTab
& Rs!Rank_4 & vbTab & Rs!Svc_Status_4 & vbTab & Rs!Unit_Fmn_4
& vbTab & Rs!Name_4 & vbTab & Rs!Arm_Svc_4 & vbTab & Rs!PA_No_5
& vbTab & Rs!Rank_5 & vbTab & Rs!Svc_Status_5 & vbTab
& Rs!Unit_Fmn_5 & vbTab & Rs!Name_5 & vbTab & Rs!Arm_Svc_5
& vbTab & Rs!Award_Year & vbTab & Rs!Cat_of_Award
Rs.MoveNext
srno = srno + 1
Wend
Rs.Close
Set Rs = Nothing
End Sub
------------------------------------Zooom Pic--------------------------------Option Explicit
Dim con As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim srno As Integer
Dim a As Integer
Dim fso As New FileSystemObject
273
End Sub
274
Else
MsgBox "Required Record not found...."
End If
End If
Exit Sub
errorH:
myConnection.RollbackTrans
MsgBox "Please Select Appropriate Section... " + Err.Description
, vbCritical + vbOK
End Sub
Administration
Option Explicit
Dim con As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim srno As Integer
275
chEDMS.Value = 0
chSave.Value = 0
chDelete.Value = 0
chUpdate.Value = 0
chSearch.Value = 0
chRefresh.Value = 0
chExit.Value = 0
txtUser.SetFocus
con.Open strConnString
MSFlexGrid.FormatString = "ID
MSFlexGrid.Rows = 1
srno = 1
While Not Rs.EOF
Rs.MoveNext
srno = srno + 1
Wend
276
"
Rs.Close
Set Rs = Nothing
End Sub
If chDef.Value = 1 Then
a = 1
Else
a = 0
End If
If chApp.Value = 1 Then
B = 1
Else
B = 0
End If
If chEmpRec.Value = 1 Then
c = 1
Else
c = 0
End If
If chLAdmin.Value = 1 Then
d = 1
277
Else
d = 0
End If
If chPerform.Value = 1 Then
e = 1
Else
e = 0
End If
If chPayroll.Value = 1 Then
f = 1
Else
f = 0
End If
If chRecSearch.Value = 1 Then
g = 1
Else
g = 0
End If
If chReports.Value = 1 Then
h = 1
Else
h = 0
End If
If chEDMS.Value = 1 Then
i = 1
Else
i = 0
End If
278
If chSave.Value = 1 Then
j = 1
Else
j = 0
End If
If chDelete.Value = 1 Then
k = 1
Else
k = 0
End If
If chUpdate.Value = 1 Then
l = 1
Else
l = 0
End If
If chSearch.Value = 1 Then
m = 1
Else
m = 0
End If
If chRefresh.Value = 1 Then
n = 1
Else
n = 0
End If
If chExit.Value = 1 Then
o = 1
279
Else
o = 0
End If
txtUser.Text = ""
txtPassword.Text = ""
txtConPass.Text = ""
chDef.Value = 0
chApp.Value = 0
chEmpRec.Value = 0
chLAdmin.Value = 0
chPerform.Value = 0
chPayroll.Value = 0
chRecSearch.Value = 0
chReports.Value = 0
chEDMS.Value = 0
chSave.Value = 0
chDelete.Value = 0
chUpdate.Value = 0
chSearch.Value = 0
chRefresh.Value = 0
chExit.Value = 0
txtUser.SetFocus
280
con.Open strConnString
MSFlexGrid.FormatString = "ID
MSFlexGrid.Rows = 1
srno = 1
While Not Rs.EOF
Rs.MoveNext
srno = srno + 1
Wend
Rs.Close
Set Rs = Nothing
Else
MsgBox "Please Enter Correct Password...", vbInformation,
App.ProductName
End If
End Sub
281
"
If chDef.Value = 1 Then
a = 1
Else
a = 0
End If
If chApp.Value = 1 Then
B = 1
Else
B = 0
End If
If chEmpRec.Value = 1 Then
c = 1
Else
c = 0
End If
If chLAdmin.Value = 1 Then
d = 1
Else
d = 0
End If
If chPerform.Value = 1 Then
e = 1
Else
e = 0
282
End If
If chPayroll.Value = 1 Then
f = 1
Else
f = 0
End If
If chRecSearch.Value = 1 Then
g = 1
Else
g = 0
End If
If chReports.Value = 1 Then
h = 1
Else
h = 0
End If
If chEDMS.Value = 1 Then
i = 1
Else
i = 0
End If
If chSave.Value = 1 Then
j = 1
Else
j = 0
End If
If chDelete.Value = 1 Then
283
k = 1
Else
k = 0
End If
If chUpdate.Value = 1 Then
l = 1
Else
l = 0
End If
If chSearch.Value = 1 Then
m = 1
Else
m = 0
End If
If chRefresh.Value = 1 Then
n = 1
Else
n = 0
End If
If chExit.Value = 1 Then
o = 1
Else
o = 0
End If
284
& ",Payroll=" & Val(f) & ",RecSearch=" & Val(g) & ",Reports="
& Val(h) & ",EDMS=" & Val(i) & ",Save1=" & Val(j) & ",Delete1="
& Val(k) & ",Update1=" & Val(l) & ",Search1=" & Val(m) & ",Refresh1="
& Val(n) & ",Exit1=" & Val(o) & "
where UserName=" & Trim(txtUser.Text) & ""
MsgBox "Record Updated Successfully...", vbInformation, App.ProductName
txtUser.Text = ""
txtPassword.Text = ""
txtConPass.Text = ""
chDef.Value = 0
chApp.Value = 0
chEmpRec.Value = 0
chLAdmin.Value = 0
chPerform.Value = 0
chPayroll.Value = 0
chRecSearch.Value = 0
chReports.Value = 0
chEDMS.Value = 0
chSave.Value = 0
chDelete.Value = 0
chUpdate.Value = 0
chSearch.Value = 0
chRefresh.Value = 0
chExit.Value = 0
txtUser.SetFocus
con.Open strConnString
285
MSFlexGrid.FormatString = "ID
"
MSFlexGrid.Rows = 1
srno = 1
While Not Rs.EOF
Rs.MoveNext
srno = srno + 1
Wend
Rs.Close
Set Rs = Nothing
End Sub
con.Open strConnString
286
MSFlexGrid.FormatString = "ID
"
MSFlexGrid.Rows = 1
srno = 1
While Not Rs.EOF
Rs.MoveNext
srno = srno + 1
Wend
Rs.Close
Set Rs = Nothing
End Sub
Text1.Visible = True
287
Text1.Text = Grid1.Text
Dim irow, icol As Integer
End If
288
chSave.Value = Rs.Fields("Save1")
chDelete.Value = Rs.Fields("Delete1")
chUpdate.Value = Rs.Fields("Update1")
chSearch.Value = Rs.Fields("Search1")
chRefresh.Value = Rs.Fields("Refresh1")
chExit.Value = Rs.Fields("Exit1")
Else
MsgBox "Record not found..."
End If
End Sub
Payroll Manager
Option Explicit
Dim con As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim srno As Integer
txtEmpNo.Text = ""
txtCat.Text = ""
txtName.Text = ""
txtAppoint.Text = ""
txtDte.Text = ""
txtDOA.Text = ""
txtDOB.Text = ""
txtGrade.Text = ""
txtACNo.Text = ""
289
txtBasicPay.Text = "0"
txtHRA.Text = "0"
txtMedical.Text = "0"
txtConveyance.Text = "0"
txtTGP.Text = "0"
txtMarriedAll.Text = "0"
txtExpPay.Text = "0"
txtTechPay.Text = "0"
txtQualiPay.Text = "0"
txtPerfPay.Text = "0"
txtDearAll.Text = "0"
txtInc.Text = "0"
txtSpecAll.Text = "0"
txtSpecInc.Text = "0"
txtAdminDir.Text = "0"
txtGP.Text = "0"
txtEmpNo.SetFocus
End Sub
290
MarriedAll = txtMarriedAll.Text
ExpPay = txtExpPay.Text
TechPay = txtTechPay.Text
QualiPay = txtQualiPay.Text
PerfPay = txtPerfPay.Text
DearAll = txtDearAll.Text
Inc = txtInc.Text
SpecAll = txtSpecAll.Text
SpecInc = txtSpecInc.Text
AdminDir = txtAdminDir.Text
TGP = txtTGP.Text
End Sub
291
txtTemp.Text = Rs.Fields("EmpNo")
End If
292
txtACNo.Text = ""
txtBasicPay.Text = "0"
txtHRA.Text = "0"
txtMedical.Text = "0"
txtConveyance.Text = "0"
txtTGP.Text = "0"
txtMarriedAll.Text = "0"
txtExpPay.Text = "0"
txtTechPay.Text = "0"
txtQualiPay.Text = "0"
txtPerfPay.Text = "0"
txtDearAll.Text = "0"
txtInc.Text = "0"
txtSpecAll.Text = "0"
txtSpecInc.Text = "0"
txtAdminDir.Text = "0"
txtGP.Text = "0"
txtEmpNo.SetFocus
End If
End Sub
txtEmpNo.Text = Rs.Fields("EmpNo")
txtCat.Text = Rs.Fields("Cat")
txtName.Text = Rs.Fields("Name")
293
txtAppoint.Text = Rs.Fields("Appoint")
txtDte.Text = Rs.Fields("Dte")
txtDOA.Text = Rs.Fields("DOA")
txtDOB.Text = Rs.Fields("DOB")
txtGrade.Text = Rs.Fields("Grade")
txtACNo.Text = Rs.Fields("AcNo")
txtBasicPay.Text = Rs.Fields("BasicPay")
txtHRA.Text = Rs.Fields("HRA")
txtMedical.Text = Rs.Fields("Medical")
txtConveyance.Text = Rs.Fields("Convey")
txtTGP.Text = Rs.Fields("TGP")
txtMarriedAll.Text = Rs.Fields("MarriedAll")
txtExpPay.Text = Rs.Fields("ExpPay")
txtTechPay.Text = Rs.Fields("TechPay")
txtQualiPay.Text = Rs.Fields("QualiPay")
txtPerfPay.Text = Rs.Fields("PerfPay")
txtDearAll.Text = Rs.Fields("DearAll")
txtInc.Text = Rs.Fields("Inc")
txtSpecAll.Text = Rs.Fields("SpecAll")
txtSpecInc.Text = Rs.Fields("SpecInc")
txtAdminDir.Text = Rs.Fields("AdminDir")
txtGP.Text = Rs.Fields("GP")
End If
End Sub
294
BP = txtBasicPay.Text
HRA = txtHRA.Text
Medical = txtMedical.Text
Convey = txtConveyance.Text
txtMarriedAll.Text = "0"
txtExpPay.Text = "0"
txtTechPay.Text = "0"
txtQualiPay.Text = "0"
txtPerfPay.Text = "0"
txtDearAll.Text = "0"
txtInc.Text = "0"
295
txtSpecAll.Text = "0"
txtSpecInc.Text = "0"
txtAdminDir.Text = "0"
txtGP.Text = "0"
txtEmpNo.SetFocus
End Sub
End Sub
& ",Medical=" & Trim(txtMedical.Text) & ",Convey=" & Trim(txtConveyance.Text) & ",TGP=" & T
& Trim(txtExpPay.Text) & ",TechPay=" & Trim(txtTechPay.Text) & ",QualiPay="
& Trim(txtQualiPay.Text) & ",PerfPay=" & Trim(txtPerfPay.Text) & ",DearAll="
& Trim(txtDearAll.Text) & ",Inc=" & Trim(txtInc.Text) & ",SpecAll=" & Trim(txtSpecAll.Text
& Trim(txtAdminDir.Text) & ",GP=" & Trim(txtGP.Text) & " where EmpNo="
& Trim(txtEmpNo.Text) & ""
MsgBox "Record Updated Successfully...", vbInformation, App.ProductName
txtEmpNo.Text = ""
txtCat.Text = ""
txtName.Text = ""
txtAppoint.Text = ""
txtDte.Text = ""
txtDOA.Text = ""
txtDOB.Text = ""
txtGrade.Text = ""
txtACNo.Text = ""
txtBasicPay.Text = "0"
txtHRA.Text = "0"
296
txtMedical.Text = "0"
txtConveyance.Text = "0"
txtTGP.Text = "0"
txtMarriedAll.Text = "0"
txtExpPay.Text = "0"
txtTechPay.Text = "0"
txtQualiPay.Text = "0"
txtPerfPay.Text = "0"
txtDearAll.Text = "0"
txtInc.Text = "0"
txtSpecAll.Text = "0"
txtSpecInc.Text = "0"
txtAdminDir.Text = "0"
txtGP.Text = "0"
txtEmpNo.SetFocus
End Sub
End Sub
297
txtStatus.Text = Rs.Fields("Resigned")
If txtStatus.Text = 1 Then
MsgBox "This Employee is no more on job...... Please contact HR/OD"
txtEmpNo.Text = ""
Else
txtCat.Text = Rs.Fields("Cat")
txtEmpNo.Text = Rs.Fields("EmpNo")
txtName.Text = Rs.Fields("Name")
txtAppoint.Text = Rs.Fields("Appoint")
txtGrade.Text = Rs.Fields("Grade")
txtDOA.Text = Rs.Fields("DOA")
txtDte.Text = Rs.Fields("Dte")
txtDOB.Text = Rs.Fields("DOB")
txtACNo.Text = Rs.Fields("ACNo")
End If
End If
End Sub
-----------------------------------------------------------------------------------Private Sub cmdGPSlip_Click()
Dim Rs As New ADODB.Recordset
and Dte = " & Trim(cmbDte.Text) & "", myConnection, adOpenStatic, adLockReadOnly
298
crptEmpRec.Pic2 = pImageFilePath
crptNetPayInd.DiscardSavedData
crptNetPayInd.Database.SetDataSource Rs, 3, 1
Set gCrystalObj = crptNetPayInd
frmCrystalReport.Show
End If
End Sub
crptEmpRec.Pic2 = pImageFilePath
crptNetPay.DiscardSavedData
crptNetPay.Database.SetDataSource Rs, 3, 1
Set gCrystalObj = crptNetPay
frmCrystalReport.Show
End If
End Sub
299
End Sub
300
chResigned.Value = 0
txtEmpNo.SetFocus
End Sub
If chResigned.Value = 1 Then
chResigned.BackColor = &HFF&
End If
Else
End If
End Sub
301
End Sub
End Sub
302
cmbGrade.Text = ""
txtDOA.Text = ""
cmbDte.Text = ""
txtDOB.Text = ""
txtACNo.Text = ""
chResigned.Value = 0
chResigned.BackColor = &HE0E0E0
txtEmpNo.SetFocus
End Sub
303
End Sub
End Sub
End Sub
End Sub
304
Else
MsgBox "Record not found..."
End If
End Sub
End Sub
305
REFERENCES
307
INDEX
chip, 32
Classes, 141
code, 188
collaboration Diagrams, 116
communication, iv
component diagram, 125
Conclusion, 154
Biometrics, 30, 40
Black box testing, 140
BLL, 130
block Diagram, 86
buddy punching, 33
Calculator, 162
CFD, 81
Change password, 160
ChangePassword(), 130
308
Management, 5
management, 40
manual system, 24
Many-to-Many, 96
memory, 21
model, 77
Module diagram, 87
Modules Diagram, 87
F1, 184
File menu, 159
fingerprint, 32
functional, 38
Objective, 9
Olympic, 31
One-to-Many, 96
One-to-one, 96
non-functional, 39
Normalization, 92
Notepad, 162
hardware interface, 21
Help, 186
Housing, 5
HR, 7, 25, 38
HR server, 19
HRM, 7
ID, 31, 33
ID card, 31
identification, 31, 33
implementation, 127
Radio Frequency, 33
range, 34
REcruitment, 164
Regression testing, 141
relational, 92
relationships, 82
reliablity, iv, 22
Leave manager, 16
level 0, 78
LoginClick(), 130
logoff, 163
maitainabality, 23
309
Report, 36
Reports, 177
Reports(), 134
requirements, 39
Reuirements, 38
RF, 33, 34
RFID, 14, 32, 34, 40
rights, 183
risk, 13
Risk Assesement, 13
SDLC, 139
Search Manager, 175
Search(), 133
searching, 22
Security, 33
security, 34
secutiry, 22
Sequence Diagrams, 101
skimmed, 32
Software Architecture diagram,
100
software design, 75
Software Testing, 139
source code, 188
spiral model, 12
Splash Screen, 157
SQA, 139
ULL, 130
Unit testing, 141
US, 32
usecase, 43, 77
usecase diagram, 76
user manual, 157
validity, 13
Vb 6.0, 98
verification, 31
Vision, 5
waterfall, 12
White box testing, 140
wireless, 11
310
VITA
Those Who Joyfully Leaves Everything in Allahs Hand Will Eventually See Allahs
Blessing in Everything,Because Worries End Where Faith Begins!!
Alls Well That Ends Well !!
311