intelligent access control system by yusuph kileo

INTELLIGENT ACCESS CONTROL SYSTEM

By

YUSUPH KILEO

BSc. (Hons) in Computing: Computer Security

Staffordshire University

A project submitted in partial fulfillment of the

award of the Bachelor of Science (Honors) in

Computing: Computer Security

YUSUPH KILEO Intelligent access control system

Page 1

DEDICATION

This is for my family, the one which never get tired to provide me all the support that I need. I

will always be thankful to them.

ACKNOWLEDGMENTS

First of all I would like to express my appreciation to be given faith and dedication to complete

this project. It has helped me a lot in understanding of what I have learnt and at the same time

provided me with self-confidence to implement the knowledge for future use. However, I

realized that there would be no great result without helping hands.

I would also like to express my most grateful appreciation to these people and organizations.

This project would not be a success without any help from them. I would be no where without

the insight, patience and guidance of my supervisor Nor Azlina and my other class met who

always make me to be better than ever before. In the process of writing this project, they often

made me laugh.

Throughout the help from these people and those who were there to respond on my questioner, I

have successfully completed my project on time and am satisfied with the outcome of it .This

was not the result of my commitment and dedication alone. So, I would like to show my thankful

to my mother for giving me emotional support and constant encouragement even from far. She

is the backbones of my resistance towards internal and external challenges. She is great parent.

Unforgotten are my classmates and friends which had shared some materials to be utilized in

this project. They also suggested some ideas and sources for my references.

Thank you.


Page 2

ABSTRACT

Accessing Buildings and private property has given birth to many access control systems and this

projects covers the security of the theoretical system where by authorized user to the building

can utilize. There are many technologies that can be used to implement such a system each with

different strengths and weaknesses. The system designed in this project was constructed for the

security to the buildings like Conference buildings or restricted area to help the control of the

facilities (Buildings).

The design was the concentrated on the intelligent way to allow the property manager to have a

full control of the electronic equipment within the building concern by providing capability to

switch them on or off as when automatically when user started using the facility. Also the system

provided an easy way to track the movement of the facility (Buildings) users.

ABBEREVIATIONS

Throughout this project the below will be important abbreviations that will be used.

IACS Intelligent access control system.

PPF Project proposal Form.

PSF Project Specification Form.

FM Facility manager.

LabVIEW Laboratory Virtual Instrument Engineering Workbench.

SDLC System Development Life Cycle.

ELC Electronic Device Control.

PACS Physical Access Control System.

VI Virtual Instrument.

CASE Computer Aided Software Engineering.

FM Facility Manager.

CPU Central Processing Unit.

RAD Rapid application Development.

SC Smart Card.

SSADM Structured Systems Analysis and Design Method.


Page 3

Table of Contents CHAPTER ONE: INTRODUCTION .................................................................................................................... 6

1.1 PROJECT OVERVIEW ............................................................................................................................ 6

1.2 PROJECT AIMS AND OBJECTIVES ......................................................................................................... 6

1.2.1 AIMS ............................................................................................................................................. 6

1.2.2 OBJECTIVES .................................................................................................................................. 7

1.3 TARGET AUDIENCE .............................................................................................................................. 7

1.4 PROJECT SCHEDULE ............................................................................................................................ 8

1.5 PROJECT WORK BREAK DOWN ........................................................................................................... 8

CHAPTER TWO: PROBLEM DESCRIPTION ...................................................................................................... 9

CHAPTER THREE: LITERATURE REVIEW ....................................................................................................... 10

3.1 INTRODUCTION ................................................................................................................................. 10

3.2 SYSTEM DEVELOPMENT METHODOLOGY ......................................................................................... 11

3.2.1 INTROUCTION ............................................................................................................................ 11

3.2.2 RAPID APPLICATION DEVELOPMENT (RAD) ............................................................................... 12

3.2.3 OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN METHOD .................................................. 14

3.2.4 STRUCTURED SYSTEM ANALYSIS AND DESIGN METHOD (SSADM) ........................................... 15

3.2.5 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) ............................................................................... 17

3.2.6 METHODOLOGY COMPARISONS ................................................................................................ 18

3.2.7 SELECTION OF METHODOLOGY ................................................................................................. 19

3.3 PROGRAMMING LANGUAGES ........................................................................................................... 21

3.3.1 INTRODUCTION .......................................................................................................................... 21

3.3.2 VISUAL BASIC.NET ...................................................................................................................... 21

3.3.3 C ++ PROGRAMMING ................................................................................................................. 22

3.3.4 LabVIEW ..................................................................................................................................... 25

3.3.5 SELECTION OF PROGRAMMING LANGUAGE ............................................................................. 27

3.4 DATA BASE ........................................................................................................................................ 28

3.4.1 INRODUCTION ............................................................................................................................ 28

3.4.2 STRUCTURED QUERY LANGUAGE (MYSQL) ............................................................................... 29

3.4.3 MS SQL SERVER .......................................................................................................................... 29

3.4.4 MYMSQL AND MS SQL SEVER COMPARISONS ........................................................................... 30

3.4.5 SELECTION OF DATA BASE ......................................................................................................... 32


Page 4

3.5 REVIEW SIMILAR SYSTEM.................................................................................................................. 33

3.5.1 INTRODUCTION .......................................................................................................................... 33

3.5.2 HONEYWELL ............................................................................................................................... 34

3.5.3 CONCLUSION .............................................................................................................................. 44

CHAPTER FOUR: RESEARCH METHODS ....................................................................................................... 45

4.1 INTRODUCTION ................................................................................................................................. 45

4.2 QUESTIONNAIRES ............................................................................................................................. 45

4.2.1 ADAVANTAGES ........................................................................................................................... 45

4.2.2 DISADVANTAGES ........................................................................................................................ 46

4.2.3 QUESTIONNARES AND OBJECTIVES ........................................................................................... 46

4.3 SUMMARY ......................................................................................................................................... 49

CHAPTER FIVE: ANALYSIS AND DESIGN ....................................................................................................... 50

5.1 INTRODUCTION ................................................................................................................................. 50

5.2 ANALYSIS OF QUESTIONNAIRES RESULTS ......................................................................................... 50

5.3 SUMMARY ............................................................................................................................................. 56

5.4 DESIGN .................................................................................................................................................. 57

5.4.1 USE CASE DIAGRAM ....................................................................................................................... 57

5.4.1.0 ANALYSIS USE CASE ................................................................................................................. 58

5.4.2 SEQUENCE DIAGRAM ..................................................................................................................... 62

CHAPTER SIX: IMPLEMENTATION ............................................................................................................... 63

6.1 INTRODUCTION ................................................................................................................................. 63

6.2 SYSTEM PROTOCAL DESIGN .............................................................................................................. 63

6.2.1 SEVER ......................................................................................................................................... 63

6.2.2 CLIENT ........................................................................................................................................ 64

6.2.3 Controls ...................................................................................................................................... 65

6.3 SAMPLE PROGRAMMING .................................................................................................................. 74

CHAPTER SEVEN: TESTING .......................................................................................................................... 77

7.1 INTRODUCTION ................................................................................................................................. 77

7.2 OJECTIVES OF TESTING ..................................................................................................................... 77

7.3 SYSTEM/APPLICATION TESTING STRATEGY ...................................................................................... 78

7.3.1 UNIT TESING ............................................................................................................................... 78

7.3.2 INTEGRATION TESTING .............................................................................................................. 78


Page 5

7.3.3 SYSTEM TESTING ........................................................................................................................ 79

7.4 TESTING RESULTS .............................................................................................................................. 79

7.4.1 UNIT TESTING RESULT ................................................................................................................ 79

7.4.2 INTEGRATION TESTING RESULT ................................................................................................. 81

7.4.3 THE RECOVERY TESTING RESULT ............................................................................................... 83

7.4.4 SECURITY TESTING RESULT ........................................................................................................ 83

7.4.5 PERFORMANCE TESTING RESULTS ............................................................................................. 85

CHAPTER EIGHT: REFERENCES .................................................................................................................... 86

CHAPTER NINE: USER MANUAL .................................................................................................................. 89


Page 6

CHAPTER ONE: INTRODUCTION

1.1 PROJECT OVERVIEW

This project is segregated into three main parts which are Part one, Part two and Part three. Part

One highlights Introduction that will highlight the need of the system, why is it important to have

the system, what will be the scope and limitations of the systems and closely check on the

targeted audience to the system. Also Problem description will be analyzed to show the problems

that cause the need of the intelligent access control system.

Part two describes in detail the literature review where by similar system will be reviewed with

good analysis of the features that improved on the current system. Research methods both

primary and secondary where by online questioner will be used which will then analyzed

critically. The design of the system using the waterfall model which is under classic Software

Development Life Cycle (SDLC) methodology will be critically discussed on this part. And

finally developer will implement the system and testing of the system will be done.

Part three Will consists of critical evaluations of the whole project and finalizes with the

conclusion, as the name suggests would summarize the main contents of the project and showing

the how the problem is solved as well as briefly outline the limitations of the system and future

enhancements to the system and finally the deducted lessons from the project and the challenges

faced and how they were mitigated will be outlined.

1.2 PROJECT AIMS AND OBJECTIVES

1.2.1 AIMS

As the technology grow, the need of modifying traditional way of securing physical property is

getting more demand. Physical property like office buildings, conference building and other

buildings need to have security feature that will keep unauthorized user not to be able to access

them. Intelligent access control system will come up with the solution that will keep these

Physical properties (Buildings) more secure. The property manager through the help of this

system will have a full control to the buildings.


Page 7

1.2.2 OBJECTIVES

Intelligent access control system will come up with the solution to increase the building security

and to allow the building/ property manager to have full access to the building. This will go

together with the following objectives.

To help the facility manager to be in a full control to the property: here the facility

manager will be able to control the building in terms of security wise since the facility

manager will be able to control unauthorized people not to access the building. The use of

the card which is integrated with the system to provide access only to the authorized user

is applied. Therefore the facility will be protected by an intelligent access control system.

To be able to control electronics equipment: this system is also capable of switching

on/off various electrical and electronics instruments immediately on entry/ departure of

persons as per the predefined software.

To keep track of the facility users: the system is able to keep track of the facility users by

generating the log file. This will help the facility manager to keep track to all the user of

the buildings with the valid records.

The deliverable of the system will be Simulator program that will demonstrate the whole process

used to allow authorized people to access the required building.

1.3 TARGET AUDIENCE The system that Will be developed by the developer can be used in any cooperate company and

any office where by the need of security is highly recommended. Since the system is helpful in

terms of doing multi task like controlling electronic equipment and keep track of the facility

users its highly recommended in most of the company and offices in our current world so that to

simplify the works within the facility that uses Intelligent access control system.


Page 8

1.4 PROJECT SCHEDULE In order to keep tasks and entire project schedule in scope and on-target together with resource

planning and budgeting of costs the need of the project schedule is highly recommended that will

provide realistic milestones for the completion of tasks through the lifespan of the project and

allows applicable resources to be identified, an anticipated timeframe to be established and also

provides the basis for budgeting individual tasks and the project at large. During project or task

execution, the schedule identifies elements that are ahead, behind and on-schedule and allows

appropriate adjustments to be made. It removes the "surprise" element that often confronts

project management.

1.5 PROJECT WORK BREAK DOWN The developers project work break down is categorized on the followings.

Project initiation Here is where the Idea generation comes in, PPF and PSF where

drown by developer at this stage.

Planning The time that developer will utilize to make this project successfully and

delivered on time is planned accordingly on this stage.

Analysis Findings of the researches made by the developer critically analyzed on this

stage.

Design The design of the system is done on this stage after a critical analysis of the

need and what to delivery is completed.

Develop The system is developed on this stage.

Evaluation after a clear development of the system critical evaluation along with

delivering of the system is carried out on this stage.

Project ending here is where the soft and hard copy of the whole documentation and the

system is delivered or handed over admin for further marking.


Page 9

CHAPTER TWO: PROBLEM DESCRIPTION

All Physical properties like buildings needed to have security so that unauthorized user will have

no ability to access them. This security will help the property owner to be in control of the

building concerned.

Unauthorized user happen to be desperate in need to access properties like buildings for

different purpose which leads to the breaking in to the property and do varieties of crimes

like theft, destructions of the property inside the buildings or utilizations of the private

resources that are not supposed to be utilized by unauthorized users.

The security which will be implemented for unauthorized used to have no ability to

access the building is to insure the utilization of the resources is taken in considerations

and the minimum usage of the resources is effectively observed.

Most of access controls available now are incapable of controlling electronics equipment

of the buildings such as lights and Air Conditions. Intelligent access control system will

be able to resolve the problem by providing an ability to control the electronics

equipment.

Also, The keeping tracks of the facility users is being an issue with the systems available

that uses smart cards to access buildings where by a user can utilize the facilities and the

records are not properly kept for further referencing in case of any emergences. New

intelligent access control system will be able to eliminates this weakness that is seen in

most current system and the users of the facility will be monitored as they swap the card

to access the building by keeping the records of all the users.

Time saving, The system available that uses smart card on access control to the buildings

especially to the offices there is a tendency of the user to face the signing book where by

the user will need to write the name as a notification of his/her presence. This tends to

slow down other important activities. New intelligent access control system will be able

to eliminate this problem where by a user will not be in a position to start registering as

the system itself will take care of it by collecting the details of the smart card users and

store them.


Page 10

CHAPTER THREE: LITERATURE REVIEW

3.1 INTRODUCTION

A literature review discusses published information in a particular subject area, and sometimes

information in a particular subject area within a certain time period.- Leonard J, 2000. Here is

where a developer compare similar systems of what is about to develop and research it in detail.

At the same time the methodologies comparison and analysis are done in here.

Literature review provides an overview or act as a stepping stone to a developer especially when

there is a limited time to conduct research. This will provide a handy guide to the system which

is about to be developed. Literature reviews also provide a solid background for a research

paper's investigation.

This Literature review will focus on two Main parts which are Technical research and domain

research where by technical research will focus on reviewing different types of system

development methodologies. It will also analyze each of them and provide a summary

conclusion to justify the chosen system development methodology used to develop intelligent

access control system and to provide a solid understanding to the new system which is about to

be developed. Programming languages and database Research will be also reviewed.

Domain research will focus on reviewing the reviewing similar system to intelligent access

control system that are currently existing and critically observe there strength and weakness in

order to come up with the solid background on developing the new system which will consists of

modified features on access control system using smart card.


Page 11

3.2 SYSTEM DEVELOPMENT METHODOLOGY

3.2.1 INTROUCTION

Methodology can properly refer to the theoretical analysis of the methods appropriate to a field

of study or to the body of methods and principles particular to a branch of knowledge (The Free

Dictionary by Farlex, 2011). In other words we can refer methodology as the system of methods

and principles that can be used in a particular discipline.

There are different types of system development methodologies that are used when some

individual is planning to design an Information system. Each of the methodology depends on

approach that developer is planning to use and the requirement of the system. These types of

methodologies include The Structured System Analysis and Design method (SSADM), System

development Life Cycle (SDLC), Rapid Application Development (RAD) and Object Oriented

System analysis and design Method.

The developer here will choose three among these system development methodologies where by

critical analysis of each of the chosen system methodology will be carried out and eventually the

developer will provide a justification on the selection of the right methodology that will be

suitable to be used to develop an intelligent access control system using smart cards.

The developer will analyze the challenges that are available such as Purpose, approach,

Requirement and analysis, planning the project, Design and development, Implementation and

maintenance in order to come up with the most appropriate system development methodology

for the intelligent access control system using smart card.


Page 12

3.2.2 RAPID APPLICATION DEVELOPMENT (RAD)

RAD is a linear sequential software development process model that emphasis an extremely

short development cycle using a component based construction approach. If the requirements are

well understood and defines, and the project scope is constraint, the RAD process enables a

development team to create a fully functional system with in very short time period. RAD

reduces the development time and reusability of components help to speed up development. All

functions are modularized so it is easy to work with.

For large projects RAD require highly skilled engineers in the team. Both end customer and

developer should be committed to complete the system in a much abbreviated time frame. RAD

is based on Object Oriented approach and if it is difficult to modularize the project the RAD may

not work well.

RAD proposes that products can be developed faster and of higher quality by:

Using workshops or focus groups to gather requirements.

Prototyping and user testing of designs.

Re-using software components.

Following a schedule that defers design improvements to the next product version.

Keeping review meetings and other team communication informal.

The above figure shows the phases available for RAD Model. (Kendall & Kendall System

Analysis and Design, Pg. 219)


Page 13

Systems development methodology is created to radically decrease the time needed to design and

implement information systems radically especially for five key factors:

Extensive user involvement Using this type of methodology user involvement is

highly required so that each time user has to provide feedback on the system developed

rapidly in order to make the process as easiest as possible to developer as the system is

rapidly developed and the need of the developer to rotate from user design and

construction is highly needed to be closely observed by the developer.

Joint Application Design sessions is used by RAD which involves a lot of user

communication with planner, manager and system analyst. With JAD time and cost

associated with collection of data, analyze them and requirements can be significantly

reduced. Although it is cut costs and use short time it brings ideas conflicts as it

involves many people during the planning and its advised to be use with the projects

that has tight time and schedule.

Prototyping This is where the building of a model of the system is done.it helps

system designers to build an information system that intuitive and easy to manipulate

for the end user. It is a part of the analysis phase.

Integrated CASE tools tools that provide assistance to the developer on developing

software are integrated in RAD to decrease the development time and increase the

quality of the software. CASE tools reduce the time and cast of software development

and ensure the quality of software. The objective of introducing Computer Aided

Software Engineering (CASE) tools was the reduction of the time, cost of software

development and for the enhancement of the quality of the systems developed (Diane

Lending et al. 1998).

Code generators As in RAD the development is rapidly done the code are generated

to allow an easy production to save time but the skills needed happen to be high to meet

the standard.


Page 14

3.2.3 OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN METHOD

Object-oriented analysis and design (OOAD) is defined as a system development methodologies

and techniques based on objects rather than data or process. It combines both data and processes

into single entities which is called object.

It is the principal industry-proven methodology for developing high-quality object-oriented

systems. It involves three aspects: object-oriented analysis (OOA), which deals with the design

requirements and overall architecture of a system, and is focused on describing what the system

should do in terms of key objects in the problem domain; object-oriented design (OOD), which

translates a system architecture into programming constructs (such as interfaces, classes, and

method descriptions); and object-oriented programming (OOP), which implements these

programming constructs. (www. softerra.com)

Object-oriented design is a method of design encompassing the process of object-oriented

Decomposition and a notation for depicting logical and physical as well as static and dynamic

models of the system under design. And Object-oriented analysis is a method of analysis that

examines requirements from the perspective of the classes and objects found in the vocabulary of

the problem domain. (Booch G, 1998)

The Object-Oriented method has the following concepts:

Abstraction Refers to the demonstrating of essential features without the background

information.

Encapsulation It is all about information hiding. The data that contained cannot be

viewable by the outside of the world and only those functions which are stored in the

class can be access it.

Inheritance Inheritance is all about reusability such as adding additional features to

an existing class without modifying it.

Message Sending When there is an object, there will be messages to the objects and

the following objects send message back to us. Information hiding prevents the end user

form changing an objects data. However, the end user can send a message asking the

object to perform a service, and the service might change the objects data


Page 15

Polymorphism As to explain it easier, the one interface to access general class of

actions. It helps to make more than one form. The operation may display different

behaviors in different instance and it is depends on data types that used in the operation.

3.2.4 STRUCTURED SYSTEM ANALYSIS AND DESIGN METHOD (SSADM)

Structured Systems Analysis and Design Method (SSADM) is a detailed method, which covers

almost every element of the information system. (Duncan, Rackley & Walker, 1995) The

Structured System Analysis and Design Method is the only open method available for

information systems development, SSADM has been refined and improved through changing

technology and experiences of its users. It also covers system analysis and design which is not

include or does not cover project management or quality assurance (System maintaining) and

system implementation.

The basic principle of SSADM is that the system belongs to the users and hence their

participation in the development process is an essential. SSADM has three to five phases with

three technique named Data flow modeling, entity behavior modeling and Logical data

modeling.

This method is basically used for requirement specification, system design and structures a

project into smaller well defined activities and specifies the sequence and interaction of these

activities. It is also used for Specifies the sequence and interaction of these activities and gives a

precise (structured) definition. When a developer uses this methodology it is advised to

document the project as it is very important since the methodology concentrate only on analysis

and not implementation.

SSADM also deals with some of the soft system aspects. The problem to be solved is identified

at the strategic planning stage that studies the organisational requirements and defines the

business areas that need to be improved and specifies their priorities to the organisation. So

SSADM gets the result of the strategic planning regarding the system that needs to be developed

or improved. SSADM starts by studying the feasibility of the system to define its operational,

economical and technical feasibility. SSADM documents these decisions in the Requirements

Catalogue (RC). The analyst also identifies other problems through detailed investigation of the

current system. Moreover, SSADM supports the user involvement through the use of interviews

and discussions in the identification of the system requirements. The users review the products at


Page 16

each stage in the development life cycle with the analyst available to identify any defects in the

requirements. There is a new trend for the user to become a full member of the project team.

Also, the organisational structure, goals and policies are investigated in the strategic planning.

These are documented in the Project Initiation Document that is used as the starting point in

developing the system.

In addition, the users interact with the analyst to choose appropriate options from Business

System Option (BSO). BSO describes what the system should do. The analyst presents many

options for the users to choose from. BSO includes some aspects about the impact of the system

on customers and the need for training to increase employees job satisfaction, acceptability and

usability of the system. Also SSADM documents the different views of the people regarding the

system in the Requirements Catalogue. These views are documented as requirements for the new

system. Finally, the involvement of the user in analysis and design will increase the acceptability

of the new system. This is achieved by involving the user in reviewing the products of the

development cycle stages. Prototyping is used to check the system requirements. The project

management determines the prototype scope. The impact of the system on the staff is studied

during the selection of Technical System Options, which will increase the usability of the system

for the users. The users participate in choosing the options that will be implemented. The

prototype helps the users to accept and use the new system. Also, the involvement of the users in

the dialogue design increases the system usability level. The latest version of SSADM proposes

the use of SSM (Soft Systems Methodology) in the early phases (CCTA, 1993).

In summary Structured System Analysis and Design method (SSADM) have the following flow

starting as seen below:

Feasibility study.

Requirement Analysis.

Requirement Specification.

Logical System Specification.

Physical Design.


Page 17

3.2.5 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

SDLC is the process of developing information systems through investigation, analysis, design,

implementation and maintenance. SDLC is also known as information systems

development or application development. SDLC is a systems approach to problem solving and is

made up of several phases, each comprised of multiple steps (Webopedia Computer

Dictionary. 2011.)

This is one of the most popular methodologies that have been used to develop different systems.

SDLC contains models like traditional water fall model which is a good basic model for most

application development and is the oldest of the models. The waterfall method assumes,

however, that the only role for user is in specifying requirements, and that all requirements can

be specified in advance.- (SDLC. 2011 [Online] www.graywwright) It doesnt support

interactive development which is hen needed to be done sequentially.

The spiral model emphasizes the need to go back and reiterate earlier stages a number of times

as the project progresses. Its actually a series of short waterfall cycles, each producing an early

prototype representing a part of the entire project. This approach helps demonstrate a proof of

concept early in the cycle, and it more accurately reflects the disorderly, even chaotic evolution

of technology. (SDLC. 2011 [Online] www.graywwright)

The prototype model The process of quickly putting together a working model in order to test

various aspects of designing, illustrating ideas or features and gather early user feedback.

Prototyping is often treated as an integrated part of the system design process where it Is

believed to reduce project risks and cost. Often one or more prototypes are made in a process of

incremental development where each prototype is influenced by the performance of various

design in this way problem or deficiencies in design can be corrected. (SDSL Model 2011

[Online] www.dostock.com)

In general, an SDLC methodology follows these steps:

1. If there is an existing system, its deficiencies are identified. This is accomplished by

interviewing users and consulting with support personnel.


Page 18

2. The new system requirements are defined including addressing any deficiencies in the existing

system with specific proposals for improvement.

3. The proposed system is designed. Plans are created detailing the hardware, operating systems,

programming, and security issues.

4. The new system is developed. The new components and programs must be obtained and

installed. Users of the system must be trained in its use, and all aspects of performance must be

tested. If necessary, adjustments must be made at this stage.

5. The system is put into use. This can be done in various ways. The new system can phased in,

according to application or location, and the old system gradually replaced. In some cases, it

may be more cost-effective to shut down the old system and implement the new system all at

once.

6. Once the new system is up and running for a while, it should be exhaustively evaluated.

Maintenance must be kept up rigorously at all times. Users of the system should be kept up-to-

date concerning the latest modifications and procedures.

(System Development life cycle. 2011 [Online] www.Mariosalexandrou.com)

3.2.6 METHODOLOGY COMPARISONS

SDLC SSADM RAD

TIME This spend long time This spends moderate time

This spent short time

COST The cost is high (long time and a lot of documentation)

The cost is low (there is no testing and implementation)

The cost is moderate (Low documentation)

EFFORT It needs high efforts It need moderate effort Very high effort is required

COMPLEXITY It very complex It moderate complex Low complexity

USER INVOLVEMENT Moderate user involvement.

Low user involvement. Very high user involvement is required throughout the development.

SKILLS A moderate skill is needed.

Low skills is required The skill required is very high.

PHASES 7 Phases 3 5 Phases 4 phases

Table 1.0 Shows Methodology comparisons.


Page 19

3.2.7 SELECTION OF METHODOLOGY

For this project, developer prefers to use classic Software Development Life Cycle (SDLC) in

developing this project. The main purpose of this model is to develop software in a structured

way, but highly detailed in each of the processes, one-way project flow and proper management

for each of the progress.

The structure/phases of SDLC methodology includes:-

1st Phase system requirements The collections of the system requirement will be done where

by all the necessary requirements that system should have will be critically analyzed and placed

in order so that the system will satisfy clients need.

2nd

Phase Analysis and Design on this phase, the analysis and design for the proposed system.

From this stage, analysis of the requirements and needs of the system will be carried out.

Besides that, on the design part more focus will be on three levels which are interface design,

low-level design and high-level design. After analyze the needs, requirements and complete

outline of interface design and database design, the documented specifications and design will be

delivered to the sample clients/ peoples and let them understand the flows of the system and

gather some input (Feedback)

3rd

Phase Prototype development before proceed to the implementation phase, the first

prototype will developed this will allow the user to understand the system through the prototype.

After the prototype has been finalized by, it will proceed to the next phase else it will return to

the analysis and design stage and prototyping stage. There is actually a cycle analyze and design

phase and review and resolve phase before proceed to the implementation stage.

4th

Phase Implementation here is where the actual system is built with Programming. On the

fourth phase, programming will be involved in the implementation stage. On this stage, the

coding using suitable programming language will be carried out and other developer tools a

suitable programming to this project I think will be LabVIEW or Visual Basic. Net or any other

object oriented programming.


Page 20

5th

Phase Testing the testing phase will be included three different type of testing which are

unit testing, integration testing and acceptance testing. The specific group of end-user or

debugger will test and debug on the system.

Finally the system can be ready to deliver to the client.

WHY SDLC METHODOLOGY?

There are several reasons why we choose this type of model in developing this project.

Cost consideration Compared to other development model like the spiral model, this

methodology conserve costs by ensure that the client accept the output from one of the

stage before continue to the next stage. In spiral model, for every complete spiral made,

one prototype is been made and it costs money. Although the client is happy to view the

output, the client might not like to see the price later.

The clients focuses into considerations In this methodology, the client will only see the

prototype in the output from the integration stage. The second time the client see the

output will be the actual product that is ready to be used. In the spiral model, every stage

has its own prototype. The client might get confused with the prototypes as the actual

product. Therefore, the methodology selected suited best for the relaxation of the client.


Page 21

3.3 PROGRAMMING LANGUAGES

3.3.1 INTRODUCTION

Programming language is defined as a vocabulary and set of grammatical rules for instructing

a computer to perform specific tasks (Webopedia computer dictionary, 2011).For 50 years,

computer programmers have been writing code. New technologies continue to emerge, develop,

and mature at a rapid pace. Now there are more than 2,500 documented programming languages

(OReilly media, 2011).This section will concentrate on few types of programming language

which includes Visual Basic.net, C++ Programming and LabVIEW.

3.3.2 VISUAL BASIC.NET

Visual Basic.net is an extended vision of Visual basic Programming developed by Microsoft. It

is one among the Object oriented programming languages that allows a programmer to use class

while developing application.

In 1991, BASIC at Microsoft took a major step forward with the introduction of Visual Basic.

Based on an idea originally developed by Alan Cooper, Visual Basic wedded a version of the

BASIC language to the new Windows user interface, resulting in a powerful tool for developing

Windows applications. (Paul Vick, 2004)

Visual Basic.net Is mainly used to develop Microsoft application and it one among the simple

programming language to be used which does not need a developer to have a good skills at

programming languages while using it.

Advantages of Visual Basic.net includes:-

Visual basic.net extremely easy to use even to the people who are not computer

programmers as it use drag drop objects to develop applications.

Visual basic.net is excellent in writing a very simple line of programming when

developing an application since most of the codes are automatically generated when the

objects like button, labels and others are dropped to an intended application to be

developed.

Visual basic.net provides a fast way to create .NET based applications, Including XML

web services and web applications. It is mostly used for Rapid application development

(RAD).


Page 22

Visual Basic.net is a powerful object-oriented programming language, including

inheritance, interfaces, and overloading. Other new language features include free

threading and structured exception handling. (Visual Basic language, 2011[Online]

Available at www.msdn.microsoft.com). This is because the Visual basic has improved

features compare to Visual Basic that allows it to be integrated with .NET frameworks

and the common language runtime.

Disadvantages of Visual basic.net includes:-

Visual Basic.net locks a developer into using Microsoft products line. This is because its

features are designed to provide an easy way of developing and modifying Microsoft

applications.

Visual basic.net is more coupled with the Microsoft Windows operating system and is

implemented only on Microsoft Windows successfully. Since its platform is the property

of Microsoft.

All the components of Visual Basic.net must be registered in the window registry and this

makes it have compatibility issues with other operating systems and considered it good

with Microsoft windows operating systems.

3.3.3 C ++ PROGRAMMING

The C++ Programming language is an Object oriented programming language that was extended

from C Programming developed by Bjurne Stroustrup in the early 1980s at Bell Laboratories. It

has an extend features includes classes and functions which was not found in C. It also

considered a Hybrid language since a developer can develop an application in a C-like style, an

object-oriented style, or both. (Robert w. Sebsesta, 1996)

The C++ Programming language provides a collection of predefined classes along with the

capability of user-defined classes which are:-

Data type This can be instantiated any number of times.

Data member This is class definition to specify data objects.

Data Function This is a class definition to specify data functions.


Page 23

The Classes in C++ programming can name one or more parent classes, providing inheritance

and multiple inheritances respectively. It can inherit the data member and the parent classes that

are specified to be inheritable. This makes C++ programming language to be mainly used for

software engineering and graphics. (H.M. DEITEL/P.J. DEITEL, 1994)

Advantages/ benefits of C++ Programming language includes:-

C++ Programming language is a huge language with a very broad base of users. This

provides high quality compilers and other development tools for a wide range of systems.

C++ is a multi-paradigm language. This allows developers to choose the programming

style that is right for the task at hand. For example, a traditional procedural style may be

appropriate for performing a simple task such as writing the code within a small member

function.

C++ software can be performance and memory efficient. For example, well-designed,

object oriented software is normally comprehensible and therefore amenable to

performance tuning. In addition, C++ has low-level facilities that allow a skilled C++

developer to obtain appropriate levels of performance.

C++ is backward compatible with C. This is useful in very large legacy systems where

the migration to C++ normally occur a few subsystems at a time rather than all at once. In

particular, C++ backward compatibility makes it relatively inexpensive to compile C

code with C++ compiler.

C++ allows programmers to operate at a higher level of abstraction. This higher level of

abstraction allows programmers to develop software in the language of the problem

domain rather than in the language of the computer. The key to a good abstraction is deep

knowledge of the problem domain. A good abstraction allows users to use an object in a

relatively safe and predictable manner. It reduces the learning curve by providing a

simple interface described in terms of the user's own vocabulary.

(Benefits of Using C++ [ONLINE] Available at: www.ezinearticles.com)


Page 24

Disadvantages of C++ Programming languages includes:-

C++ Programming language lacks strong type checking, meaning that the compiler will

allow a character variable to be stored into a floating point variable without complaining.

The C++ component of a C and C++ compiler has much stronger type checking and will

issue warnings for such behavior. So for the programmer to receive the maximum

protection against mixed type errors, it would be better to use the C++ component of the

C and C++ compiler.

C++ programming language has bounds checking on arrays. For example, if a

programmer declares an array of 50 integers, but in the program code he or she by

mistake stores a value into array element 52, the compiler will not complain. The integer

value was indeed stored at the fifty-second integer sized offset from the base address of

the array. This lack of bounds checking can cause severe problems in some programs.

In the MS-DOC and PC-DOS operating system, C++ programming language has any

memory protection from access by pointers. A programmer can load a memory address of

any place in memory into a pointer and through that pointer retrieve or set the value at

that memory address. This feature can cause the DOS operating system to re- boot, hang-

up, or crash completely. In addition, a programmer that is unfamiliar with the use of

pointers can, in MS/PC-DOS, because his or her hard disk drive to crash, be reformatted,

or destroyed. The same also holds true for the video display on a DOS machine.

Fortunately, mini-computer operating systems, such as UNIX, have built in memory

protection that prevents such dangerous happenings as stated above.

C++ Programming language does not have sophisticated string and record handling

capabilities. Strings must be handled with a series of functions supplied in the standard C

and C++ libraries. With C++, sophisticated String objects can be created as well as

advanced record management schemes.

(C/C++ Programming, 2011 [ONLINE] Available at: www-control.eng.cam.ac.uk)


Page 25

3.3.4 LabVIEW

LabVIEW stands for Laboratory Virtual Instrument Engineering Workbench. It is defined as a

graphical programming language that uses icons instead of lines of text to create applications. In

contrast to text-based programming languages, where instructions determine program execution,

LabVIEW uses dataflow programming, where the flow of data determines execution.

With LabVIEW integrate numbers of task like, interfacing computers with the instruments,

collecting, storing, analyzing, transmitting measured data, developing program in a graphical

environment, and providing an effective user interface.

LabVIEW is a graphical programming environment used by millions of engineers and scientists

to develop sophisticated measurement, test, and control systems using intuitive graphical icons

and wires that resemble a flowchart. It offers unrivaled integration with thousands of hardware

devices and provides hundreds of built-in libraries for advanced analysis and data visualization

all for creating virtual instrumentation. The LabVIEW platform is scalable across multiple

targets and OSs, and, since its introduction in 1986, it has become an industry leader.

LabVIEW is a virtual instrument (VI) contains two parts front panel which is a user interface

with all control usable such as buttons and Block diagram is the actual executable code. It

consists of built in functions, constants and execution control structures. All controls in the front

panel have terminals in the block diagram which enables communication between the user and

the program.

(LabVIEW 2011, [Online] available at: www.ni.com/company)

In LabVIEW an interface is built by using a set of tools and objects. The followings are features

that are included on LabVIEW:-

Icon/Connector These are the ones that specify the pathways for data to flow in and out

the VIs. The icon is the graphical representation of the VI in the block diagram and the

connector defines input and output.


Page 26

Front panel (user interface) This is the interactive user interface of a virtual instrument.

It contains all controls usable in the virtual instrument such as buttons, knobs and

indicators.

Block diagram This is where the codes are added using graphical representations of

functions to control the front panel objects.


Page 27

Advantages/ benefits of LabVIEW Programming language includes:-

LabVIEW has extensive support for accessing instrumental hardware.

LabVIEW provides driver interface that save program development time.

LabVIEW is easy to use, even user with limited coding experience can write program and

deploy test solution in a reduced time.

LabVIEW consists of a large library of drivers for data acquisition hardware and test

instruments. If your task is basically about getting data to and from these and putting a

user interface on it then you can achieve it with almost no programming.

LabVIEW allows Parallel execution of multiple tasks automatically when a user place

two independent loops on the diagram and they will execute simultaneously. This is often

a requirement in data acquisition and control applications.

Disadvantages of LabVIEW Programming languages includes:-

LabVIEW utilize a large number of the computer resources compare to other

programming language.

LabVIEW has Lack of GUI elements such as, status bar for bottom of window, Grid

control think table but with Booleans, combo boxes, etc. which are available to the other

.NET programming.

LabVIEW may turn out to be difficult when it comes to the development of big

programs.

3.3.5 SELECTION OF PROGRAMMING LANGUAGE

Intelligent access control system using smart card the developer will use LabVIEW to develop

the system. This is due to its graphical nature LabVIEW has quite a number of merits, some of

which are

Multiple platforms LabVIEW can run in multiple platforms which will eventually save

users time of having to change platforms in order to suite the programming language.

Less development time - LabVIEW may be termed as one of the easiest programming

languages due to its graphical nature and thus as compared to other programming

languages system development takes less time.


Page 28

Eliminate the possibility of human error - LabVIEW is used for creating simulations for

big systems before they could be implemented.

Flexibility and scalability - LabVIEW allows for easy system maintenance or expansion.

This is due to its modularity feature. The system can be broken down into manageable

pieces and thus making expansion, maintenance and detection of problems easy.

3.4 DATA BASE

3.4.1 INRODUCTION

Database is defined as the collection of information organized in such a way that a computer

program can quickly select the desired pieces of data (Webopedia Computer Dictionary,

2011). The quick selection of data in a database is due to the database design which offers an

organized mechanism for storing, managing, and retrieving information with the help of the

tables that are available in a database.

The database is said to be efficient and truly functional when it has ability not only to store

large amounts of records well, but also to be accessed easily. In addition, new information and

changes should also be fairly easy to input. In order to have a highly efficient database system,

you need to incorporate a program that manages the queries and information stored on the

system. This is usually referred to as DBMS or a Database Management System. Besides these

features, all databases that are created should be built with high data integrity and the ability to

recover data if hardware fails (www.tech-faq.com, 2011).

Why do we use data base?

Storing information Database enable a user to store a large number of information of a

particular thing and handle them.

Retrieving information Database allows the user to retrieve information more

efficiently, more flexibly and more creatively.

Manipulating information Database can manipulate the information that it contains. The

fields that are filled in a database can easily be calculated and provide results.


Page 29

Printing information Database enable user to print the information contains in it on a

repots, labels, fax cover sheets and letter.

Securing data management Database increases the security to data that are stored in it.

It's less likely that private information stored within a database will be compromised, as

long as your IT department is up to snuff. Information can be classified, and it will be

easier to keep duplicate records- (Life123, 2011. www.life123.com/technology).

3.4.2 STRUCTURED QUERY LANGUAGE (MYSQL)

MySQL is the worlds most popular and some might argue best, open-source database - (Larry

Ullman, 2006.) It is the database management system (DBMS) for rationale database. It is

therefore defined as the rational database system that is used to store information.

MySQL was create and supported by MySQL AB, a company based in Sweden. Technically,

MySQL is an application than manage files called database, but you will commonly hear the

term database applied equally to both the files of data and program itself- (Larry Ullman,

2006.). It runs easily on Windows and UNIX.

Information stored in a MySQL database hosted on a web server can be accessed from

anywhere in the world with a computer. This makes it a good way to store information that needs

the ability to change over time, but also needs to be accessed over the net (MySQL Definition,

2011. Www.php.about.com).

3.4.3 MS SQL SERVER

Microsoft SQL Server is an application used to create computer databases for the Microsoft

Windows family of server operating systems. Microsoft SQL Server provides an environment

used to generate databases that can be accessed from workstations, the Internet, or other media

such as a personal digital assistant (PDA) (Introduction to Microsoft SQL Server. 2011.

www.fianga.com).

Microsoft SQL server is a closed (not open source) Microsoft product which was first release on

1988 in conjunction with Austin Tate and Sybase and it is known to work better with other

Microsoft products in small or large businesses.


Page 30

Microsoft SQL server is sensitive to hardware capability as older versions were compatible with

older hardware equipment whereas the newer versions of an application require more advanced

technology to support the resources needed by database for instance SQL Server 2008 R2 is

supported in virtual machine environments running on the Hyper-V role in Windows Server

2008 SP2 Standard, Enterprise and Datacenter editions. The virtual machine must run an

operating system supported for the specific SQL Server 2008 R2 edition (Hardware and

Software Requirements for Installing SQL Server 2008 R2 . 2011 www.msdn.microsoft.com).

3.4.4 MYMSQL AND MS SQL SEVER COMPARISONS

Both of these two database are mostly used today and having there similarity and differences.

Here is the comparison between these two databases:-

Open-source vs. Proprietary When it comes to these two databases, the differences

begins with the open-source nature of MySQL vs. the closed, proprietary structure of the

SQL Server. MySQL is an extensible, open storage database engine, offering multiple

variations such as Berkeley DB, InnoDB, Heap and MyISAM. On the other hand, with

the Microsoft product, you are limited to a Sybase-derived engine through both the good

and bad times.

When considering how MySQL integrates seamlessly with a number of programming

languages and other web-based technologies, it certainly has the advantage over MS SQL

in the way of compatibility, as the SQL Server is known to work better with other

Microsoft products.

Licensing Contrary to popular belief, the MySQL system isn't always free. On the other

hand, it is always more affordable. In regard to both products, licensing fees are based on

a two-tiered scheme. With MS SQL, the best way to obtain a developer's license is to buy

a license for the Microsoft Developer or Microsoft Visual Studio suite. Both provide you

with a free SQL Server license for development use. If you want to use the product in a

commercial environment, you need to at least purchase the SQL Server Standard Edition

(which could set you back over $1,000 for a few client connections)

Because MySQL is an open-source system under the GNU General Public License,

developers can use it at no cost as long as the associated projects are also open-source.

However, if you intend to sell your software as a proprietary product, you would need to


Page 31

purchase a commercial license, which costs about $400 for up to nine clients. Depending

on the project and your funds, MySQL may have the advantage here.

Technical Differences The open-source vs. proprietary battle alone is a leading cause

why some users choose one system over the other. However, there are a few differences

from a technical aspect as well. For instance, MySQL doesn't offer full support for

foreign keys, meaning it doesn't have all the relational features of MS SQL, which is

considered a complete relational database. Some versions of MySQL also lack full

support for stored procedures (the biggest disadvantage being the MyISAM system,

which doesn't support transactions)

Performance In the way of performance, MySQL is the clear leader, mainly due to the

format of its default table, MyISAM. MyISAM databases leave a small footprint using

little disk space, memory and CPU. While the system runs on the Windows platform

without flaw, it tends to perform better on Linux and other UNIX-like systems. Because

of its stability, many internet powerhouses such as Yahoo! use MySQL as their back-end

database. When it comes to performance, MS SQL's strength of being packed with more

features than other systems is perhaps its biggest disadvantage. Although most of these

features are designed for performance tuning, they tend to sacrifice other essential

elements. The cost here is complexity and the hogging of resources in the way of storage

and memory, which leads to poorer performance. If you lack the knowledge and

sufficient hardware to support an SQL server, you would be better off with another

database management system.

Security These two database systems are pretty much deadlocked in regards to security.

Both come with adequate security mechanisms by default, bearing you follow the

directions and keep the software updated with security patches. Both operate over known

IP ports which unfortunately attract a wealth of intruders, a downside that can be

attributed to both products. The good thing is that MySQL and MS SQL allow you to

change ports just in case the default becomes too vulnerable.

Recovery As far as recovery goes, the SQL Server has a definite advantage over

MySQL, which tends to fall a little short with its MyISAM configuration. A UPS system

is mandatory with MyISAM as it assumes uninterrupted operation. If a power outage

should occur, it could result in the corruption and loss of critical data. With the SQL


Page 32

Server, data corruption is more unlikely. The data travels through various checkpoints

while passing from your keyboard to the hard disk and through the monitor. Additionally,

the SQL Server keeps track of the process, even if the system unexpectedly shuts down.

(Hobach A, 2008. Advantages and Disadvantages to Using MySQL vs. MS SQL).

3.4.5 SELECTION OF DATA BASE

The system is intending to be build using LabVIEW and the compatibility of the database that

will match LabVIEW is to be considered by the developer. Visual Instruments (VIs) has an

ability to communicate and pass data between LabVIEW and the local or remote database

management system.

This can be done using the LabVIEW database connectivity toolkit. This allows the developer to

quickly connect to local and remote databases and perform many common database operations

without having to know structured query language (SQL) programming.

This toolkit greatly simplifies the process of making fast and repeated calls to popular databases,

such as Microsoft Access, SQL Server, and Oracle. If you need advanced database functionality

and flexibility, the Database Connectivity Toolkit also offers complete SQL capabilities. There

are numerous database formats available from a variety of software vendors.

In many cases, a developer may need to save data to multiple different types of databases. The

Database Connectivity Toolkit provides one consistent API for numerous databases to save you

the time of learning different APIs.

The toolkit can connect to any database with an ADO-compliant OLE DB provider or ODBC

driver, including popular databases such as:

Microsoft Access

Microsoft SQL Server

Oracle

Visual FoxPro

dBase

Paradox

My SQL

(Jerome Jovitha, 2010. Page 364)


Page 33

3.5 REVIEW SIMILAR SYSTEM

3.5.1 INTRODUCTION

Controlling user to access different facility is not a new thing. When it comes to physical access

there have been a number of solutions that different organizations apply to their facilities. Some

of the solution which has been implemented includes:-

Security Guard: Some Building properties have security guards that will be placed at the

main entrance so that to insure unauthorized user cannot access the building. These

security guards are there to either look familiar faces or identity cards of the authorized

users. This way unauthorized users may gain access easily since the guards as a human

being cannot be perfect all the time especially when there is a big number of users who

are trying to access the building.

Door Locks: This type of solution has been implemented in various building properties

where by the looks will be placed from main entrance to the other areas/Door to keep the

place looked and secure for unauthorized users not to be able to access it. The need of

someone to Open and close the door to Authorized users of the building or distributing

keys to all authorized users has to be in consideration. It should also kept in mind there

may be needed more than one key to access several doors or gates that are available. This

method is not secure as the authorized user can bring in unauthorized user with no

problem and of course there will be no records to keep tracks for the users who used the

building.

Access Card/Smart card: Some of the building has implemented this kind of solution that

seems to be more secure than the above solutions. Here authorized user of the building

property has to be with the smart card that will act as a key to all doors of the building.

This way the problem for a user to possess many keys to one building was solved. But

still using this way the smart cards happen to be unable to keep track to the users who

used the building and as well as controlling the Electronic equipment to the building once

the user gain access to the building.


Page 34

3.5.2 HONEYWELL

3.5.2.1 ABOUT HONEYWELL

Honeywell Access is a leader in the field of access control, security management and automation

systems. Honeywell Access' entry into the Access Control industry began in 1982 with the

introduction of the N-1000 control panel. Range of products extends from single door access

control to integrated systems capable of managing thousands of doors and alarm monitoring

points at worldwide locations.

Honeywell Access is committed to continually developing state-of-the-art technology and

providing its customers with total system solutions for their access control needs. As the leader

in access control, Honeywell Access' innovative, flexible product line meets and exceeds the

demanding needs of its customers worldwide.

Today, Honeywell Access continues to fill the needs of the access control market by offering a

full line of access control solutions. Honeywell Access current product line includes systems

which meet the needs of the small, medium and large scale applications. One of the exciting new

products is WIN-PAK 2, the most comprehensive access control software available in the

industry today. Its latest advancements to WIN-PAK include the "Quick-Start Configuration

Wizard" and integration using Rapid Eye Digital Video equipment. Honeywell Access continues

to set the pace with new software and hardware products.

(About Us - Access Systems 2011 [Online] www.honeywellaccess.com)


Page 35

3.5.2.2 HONEYWELL PHYSICAL ACCESS CONTROL SYSTEMS

Physical Access Control Systems (PACS) PACS control access to physical premises,

stationary or mobile locations. Compatible Honeywell PACS include:-

Pro-Watch This offers a complete security management solution including access

control, alarm monitoring, video badging, CCTV system interface, and DVR/DVM

interfaces.

WIN-PAK

PRO physical access software This is three-tier access control system

software with unrestricted number of operators, doors and communication servers. It

Provides the following standard features: DVR (Rapid Eye/Fusion) integration, floor

plans, badging, tracking, muster, multiple accounts and support to the NS2+, N-1000,

PW-2000 and PRO-2200 series control panels.

LobbyWorks This is Honeywells electronic visitor management system that

streamlines the registration and tracking of visitors. This includes visitor pre-registration,

management of visit approval, visitor authentication, badge generation, visitor arrival

notification, site check in and check out, as well as visitor traffic monitoring and audit log

reporting.

Vindicator This is an IT-based platform for integrating any CCTV, access control or

intrusion device with building automation Includes data networking, security, fire and life

safety, and building automation products and services.

Physical access control system. The Honeywell solution to support PACS integration is two-fold:

1. PACS integration module: A standalone application that will connect the Honeywell

PACS software platforms, including visitor management, to the PIV II infrastructure for

enrollment, use, and revocation of PIV II cards.

2. PACS data structure support throughout the hardware: Upgrades to Honeywell PACS

software and panels for the longer card numbers (up to 128-bits) specified by FIPS 201.

Also includes the addition of Omni Assure contactless readers to the PACS to read the

PIV Cards.

(Honeywell, Document 7-501321, Revision B)


Page 36

3.5.2.3 HONEYWELL PACS SOFTWARE INTEGRATION MODULE

The Honeywell software solution for physical access control leverages a software integration

module called the Honeywell SmartPlus

server to manage badge issuance, enrollment,

revocation processes, and XML interfaces for integration with identity management software.

The Honeywell software solution includes:

Badging client The badging client facilitates applicant enrollment of identification

documents, fingerprints, photograph, and demographic data. It also has interfaces to

biometric capture and vetting software plus card management software for card encoding.

The badging client also handles the printing/encoding of the card in a distributed PIV

Card issuance model.


Page 37

PACS registration client The registration client allows the security officer or other

designee to enroll a PIV cardholder into the PACS. The registration client validates the

user to the card with PIN and fingerprint verification and verifies the validity of the

cards digital certificate with the issuing CA.

SmartPlus server The SmartPlus server manages user identities for the Honeywell

PACS software and visitor management software, performs revocation checks on

enrolled PIV cardholders, and provides an industry-standard XML interface for

integration with IDMS. This server also maintains a list of trusted CA roots.

XML interface The XML interface provides an optional interface for sharing data

between IDMS and Honeywell PACS software.

Revocation process This process within the SmartPlus server is performed on a

scheduled basis to cross-reference enrolled PIV cardholders with issuing certificate

authorities to ensure that the cards are still valid and the certificates have not been

revoked. Permissions of revoked cards are then removed from the PACS software and

downstream hardware.

Pro-Watch, Vindicator, and WIN-PAK PRO Honeywell PACS for managing and

monitoring entry into secured areas.

LobbyWorks Honeywell visitor management software system for enrolling and

managing visitors.

3.5.2.4 PIV CARD (SMART CARD) CREATION

PIV (Personal Identity Verification) This is the card that carries the identity is often referred to

as a PIV Card. A physical artifact (e.g., identity card, smart card) issued to an individual that

contains stored identity credentials (e.g., photograph, cryptographic keys, biometric data) so that

the claimed identity of the cardholder can be verified against the stored credentials by another

person (human readable and verifiable) or an automated process (computer readable and

verifiable).


Page 38

The following chart reflects a typical card creation for a new employee. Completion of this

process assumes that the users background check is favorable and that he or she has accepted a

job at the government agency. This process is used for both government-direct employees and

contractors.


Page 39

Step Description

1 A sponsor initiates the process for a new applicant to get a card. A sponsor is typically an

HR representative or a hiring manager, but this is dependent upon organization processes.

2 An HR or similar system sends identity data to the IDMS, avoiding duplicate data entry

during enrollment and vetting. This is often applicant demographic data.

3 The IDMS sends a work order to the enrollment and vetting workstation to process the

individual. The enrollment and vetting workstation is often run by a registration office,

badging office, or physical security office.

4 The applicant presents two official identity documents, presents his or her ten fingerprints

for background check, has his or her photograph taken, and signs his or her name on a

signature capture pad. This can be done at a physical security desk, registration desk, or in

an HR office depending upon agency policies.

5 The enrollment and vetting station performs a fingerprint check with the FBI system and receives the results.

6 The enrollment and vetting station sends the results, two minutia fingerprints, photograph,

scanned documents, and signature to the IDMS.

7 The IDMS creates a new record in the CMS.

8 The IDMS notifies other data sources to take appropriate action and to send data for card

encoding to the CMS.

9 The CMS notifies the IDMS that it has received all expected data.

10 The IDMS notifies the CMS to create the card.

11 The CMS acquires a digital PIV II certificate from the CA.

12 The CMS notifies the station responsible for card issuance and activation to print and

encode a card for the applicant.

13 The applicant signs for and receives an activated PIV Card. This can be done at a physical

security desk, registration desk, or in an HR office depending upon agency policies.

14 The card issuance and activation station notifies the CMS that the card is activated.

15 The CMS notifies the IDMS of process completion.


Page 40

3.5.2.5 PIV CARD REGISTRATION INTO PACS

For PIV Card registrations into PACS, there are two use cases that Honeywell supports:

1. A PACS that has direct connection to an IDMS to receive/send data.

2. A PACS that does not have a direct connection to the issuing IDMS. This would always

apply to inter-agency registration and may apply to intra-agency registration depending

upon agency processes and procedures.

Honeywell recommends using the contact interface for card registration with PIN input,

fingerprint verification, and digital certificate check with a CA. This can be done at a manned

workstation or un-manned kiosk.

Below is the process for enrolling a cardholder into PACS using the PIV Card and validating the

card with the issuing CA:


Page 41

Step Description

1 A PIV cardholder presents his or her card to a PACS registration workstation or kiosk

and types his or her PIN. (The PIV cardholder in many cases has been pre-registered by a

sponsor at the site.)

2 The PACS registration workstation reads data stored on the card.

3 The PIV cardholder presents his or her finger to the fingerprint reader.

4 If the fingerprint is verified, the PACS workstation contacts the listed certificate authority

to find out if the certificate is valid. The PACS workstation also traces the listed

certificate authority back to the root authority to see if it is listed as a trusted source by

the PACS workstation.

During the PACS set up, the PACS administrator needs to supply a list of trusted roots.

5 The listed certificate authority advises whether the digital certificate is valid or invalid.

6 If the certificate is valid and the CA is trusted, the PIV cardholder can be enrolled into

PACS. If the card does not contain an electronic photograph of the PIV cardholder, the

PACS registration workstation takes a digital photograph.

7 The PIV cardholder is enrolled into PACS.

Data stored in PACS typically includes PIV cardholder demographic data (name),

CHUID data, card serial number, card number for use by PACS, digital certificate data

and source, and photograph. Additional cardholder data for legacy card interfaces such as

125 kHz proximity supported by tri-interface cards or data on magnetic stripes may also

be stored in PACS depending upon PACS needs.

8 PACS database updates are downloaded to the PACS panels. The PIV cardholder can

now use his or her card in the PACS.


Page 42

3.5.2.6 PIV CARD USE IN PACS

The use of a PIV Card in PACS will be accomplished by the addition of a contactless smart card

reader that is compatible and approved for use by the General Services Administration of the

U.S. government (GSA).

Step Description

1 A PIV cardholder presents his or her card to a door reader. The door reader reads

portions of the CHUID data plus optional HMAC per the current door reader

configuration.

2 The door reader sends the data to the PACS control panel.

3 The PACS panel grants or denies access based upon the database inside the panel.

3.5.2.7 PIV CARD REVOCATION FROM PACS

There are two main ways that a PIV Card is removed from a PACS:

1. The local PACS removes/suspends the PIV Card privileges locally because of either site

specific reasons (i.e., the cardholder is no longer on site, is on extended leave, or has a

role change) or because of system specific reasons (card is missing or stolen, cardholder

has been terminated). In the case of system specific reasons, the issuing IDMS must be

notified so the PIV Card can be revoked.

2. The local Physical access control system performs a regular verification of the validity of

cached PIV Card certificates to identify revoked certificates (PIV Cards).


Page 43

The entire process for PIV Card revocation from all systems is shown below:

Step Description

1 The IDMS is notified that a card is to be revoked by an automated notification or a

manual notification.

2 The IDMS notifies the CMS to revoke the certificate.

3 The CMS revokes the certificate at the CA.

4 The PACS validates the stored certificates for active users with the CA on a regular

schedule that does not exceed 18 hours.20

5 The CA advises whether certificates are valid or revoked.

6 The PACS updates its database to remove rights for PIV Cards with revoked

certificates and downloads updates to the PACS panels. The revocation is complete.

(Honeywell, Document 7-501321, Revision B)


Page 44

3.5.3 CONCLUSION

Honeywell Access control system does not have feature which can allow user to control

electronics equipment of the buildings such as lights and Air Conditions. Intelligent access

control system will be able to re

intelligent access control system by yusuph kileo

Documents

theoretical system

access control systems

intelligent way

ppf project proposal

psf project specification

elc electronic device

conference buildings

facilities buildings