Gate Access control system

Ahmad Hussain Al Ali , 208020909

Hussien Mohammed Al Quriashi, 208008686

Final Year Project Proposal

College of Computer Science & Information Technology

King Faisal University

Al-Ahsa

Kingdom of Saudi Arabia

May 2011

A report submitted in partial fulfillment of the B.Sc degree inComputer Science and Information Technology

Supervisor: Dr. Abdenour Bounsiar

Abstract

In this system we are focusing on the security issues that existedin the gate access control systems, and how it is so importantfor the organizations to keep their gates secure. So, here we areproposing a new system that will help to solve these issues. Thissystem is basically about capturing images of the vehicles platesand save them in a database with its information, which willallow the security department to monitor the security of theirgates more easily.

Acknowledgements

After we thank Allah for blessing us in this life and project, wewould like to thank our college Dean Dr. Khalid Buragga andthe vice Dean Dr. Fahad Al-Humaidan for their effort in ourcollege. After that, we would like to give a great thanks to oursupervisor Dr. Abdenour Bounsiar for his great effort to makethis project possible, and for mentor us and guide us step bystep until the very last word in this report. Also we would liketo thank all of our classmates and friends that help us throughthe implantation of this project.

Contents

List of Figures 1

List of Tables 2

1 Introduction 41.1 Statement of the problem . . . . . . . . . . . . . . . . . . . . 41.2 Scope of the system . . . . . . . . . . . . . . . . . . . . . . . . 41.3 Overview of the report . . . . . . . . . . . . . . . . . . . . . . 5

2 System Analysis 62.1 Requirements specification . . . . . . . . . . . . . . . . . . . . 6

2.1.1 Functional requirements . . . . . . . . . . . . . . . . . 62.1.2 Non-functional requirements . . . . . . . . . . . . . . . 7

2.2 Requirements analysis . . . . . . . . . . . . . . . . . . . . . . 82.2.1 Use-case modeling . . . . . . . . . . . . . . . . . . . . 82.2.2 Process modeling . . . . . . . . . . . . . . . . . . . . . 92.2.3 Data modeling . . . . . . . . . . . . . . . . . . . . . . 132.2.4 System Architecture . . . . . . . . . . . . . . . . . . . 14

3 System Prototyping 153.0.5 Login Screen . . . . . . . . . . . . . . . . . . . . . . . 153.0.6 Main Screen . . . . . . . . . . . . . . . . . . . . . . . . 163.0.7 New Profile Screen . . . . . . . . . . . . . . . . . . . . 173.0.8 Reports Screen . . . . . . . . . . . . . . . . . . . . . . 18

4 Conclusions 19

1

List of Figures

2.1 Use-Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . 82.2 Context Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 92.3 DFD Level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.4 DFD Level 2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5 DFD Level 2-2 . . . . . . . . . . . . . . . . . . . . . . . . . . 122.6 ERD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.7 System Architecture . . . . . . . . . . . . . . . . . . . . . . . 14

3.1 Login screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.3 Create new profile screen . . . . . . . . . . . . . . . . . . . . . 173.4 Reports screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2

List of Tables

4.1 Time Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3

Chapter 1Introduction

The security nowadays is one of the greatest issues in our life. All organi-zation in the world must a have a strong security system to protect theirvaluables, here we are focusing on the problem of gate access security andhow we can improve it.

1.1 Statement of the problem

In normal organizations, usually the security of their gates is monitor manu-ally by a couple of officers by the gates that check the identity of each person.This act is time consuming and may lead to some other problem. Here we areproposing an idea that will save a lot of time as well as will give the securitydepartment more control or keep them more updated to security situation.

1.2 Scope of the system

The system that we are proposing is system that will capture the plate imageof each vehicle that accesses the organization. This image will be stored in adatabase with its full information (Time, Gate, Officer etc). This system canbe installed in every gate at any organization, and can be used by the securityofficers and the security head departments. The system will save time andeffort on the security officers and will give the security head department alot more control.

4

1.3 Overview of the report

This report is divided in to four different sections. The first section willgive the reader a general view of the problem we are discussing and theproposed idea to solve this problem. The second section will be about theanalysis of the system, which will include the requirement specification anddiagrams that will describe the system (Use-Case, DFDs and ERD). In thethird section will give a snap shot of the proposed interface of the systemand the function that the system have. Finally, we will show the reader theconclusion and the result that we will get from the system and the sourcesthat been used to complete this report.

5

Chapter 2System Analysis

This Chapter is dedicated to requirements analysis.

2.1 Requirements specification

The requirements were gathered by discussing the security needs of any or-ganization with the supervisor and by consulting some people who workedin the security field.

2.1.1 Functional requirements

The functional requirement is divided in to a user requirement and systemrequirement, just to give the reader more idea about the system and itsfunctionalities.

User requirement

• Manager

– Gate

1. Insert gates data.

2. Update gates data.

3. Get reports about gates.

– Camera

1. Insert camera data.

2. Update camera data.

3. Define camera type (I/O).

6

4. Assign camera to gate.

5. Get reports about camera.

– Officer

1. Insert officer data.

2. Update officer data.

3. Assign officer to gate.

4. Assign officer to camera.

5. Get reports about officer.

• Officer

– Log in

1. Login in the right time.

2. Run the camera (start streaming).

– Images

1. Give capture order.

2. Give validation order.

3. Get report about captured images.

System requirement

1. Save the image with information.

2. Organize images with different categories.

3. Display image with information after validation.

4. Generate reports about several data.

2.1.2 Non-functional requirements

1. Speed: The system will be able to take not less than 15images per the minute.

2. Easy to use: The users of the system will have no prob-lem using the system as it has a very simple and friendlyinterface.

3. Reliability: The system should handle the pressure andnever hang.

7

2.2 Requirements analysis

Here you discuss diagrams used for requirements analysis.

2.2.1 Use-case modeling

Figure 2.1: Use-Case Diagram

8

2.2.2 Process modeling

Figure 2.2: Context Diagram

9

Figure 2.3: DFD Level 1

10

Figure 2.4: DFD Level 2-1

11

Figure 2.5: DFD Level 2-2

12

2.2.3 Data modeling

Figure 2.6: ERD

13

2.2.4 System Architecture

Figure 2.7: System Architecture

14

Chapter 3System Prototyping

3.0.5 Login Screen

Figure 3.1: Login screen

This is the first screen that will face the gate officer to insertthe user name and the password which already been entered bythe manager.

15

3.0.6 Main Screen

Figure 3.2: Main screen

This will be the main screen of the system, which will allowthe manager to control the whole system from. It is divided into four sections, Gate, Camera, Officer and Plate images.

16

3.0.7 New Profile Screen

Figure 3.3: Create new profile screen

This screen allows the system manager to add new officer tothe system. It contains all the data necessary to be saved in theofficer profile.

17

3.0.8 Reports Screen

Figure 3.4: Reports screen

This screen shows how the report will be display to the user,it will be in an easy full of information design. It also gives userthe ability to print the report.

18

Chapter 4Conclusions

The Gate Access Control System is a system that focuses mainlyon the security of organization gates. This system will help tosolve a lot of issues that existed in the manually systems. Wedivided the project in to several sections:

• Collecting the requirement, Functional and Non-Functional.

• Analyze the system, drawing the DFD’s and the ERD.

• Designing the prototype, giving a general idea of the systemfunctionality.

• Finally, writing the report.

Table 4.1: Time TableNO Task Duration Start Finish1 Discussing the useability of the system 2 Days 13/03 15/032 Collecting the requirement 7 days 15/03 22/033 Analyzing the system 32 days 22/03 23/044 Making the prototype 7 days 23/04 30/045 Writing the report 10 days 30/04 10/056 Rewriting the report using Latex 7 days 10/05 17/05

Table 4.1 Shows the process of our work during the project.

19