Page 1

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 in Computer Science and Information Technology

Supervisor: Dr. Abdenour Bounsiar


Abstract

In this system we are focusing on the security issues that existed in the gate access control systems, and how it is so important for the organizations to keep their gates secure. So, here we are proposing a new system that will help to solve these issues. This system is basically about capturing images of the vehicles plates and save them in a database with its information, which will allow the security department to monitor the security of their gates more easily.


Acknowledgements

After we thank Allah for blessing us in this life and project, we would like to thank our college Dean Dr. Khalid Buragga and the vice Dean Dr. Fahad Al-Humaidan for their eort in our college. After that, we would like to give a great thanks to our supervisor Dr. Abdenour Bounsiar for his great eort to make this project possible, and for mentor us and guide us step by step until the very last word in this report. Also we would like to thank all of our classmates and friends that help us through the implantation of this project.


Contents

List of Figures

1

List of Tables

2

1 Introduction 1.1 Statement of the problem . . . . . . . . . . . . . . . . . . . . 1.2 Scope of the system . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Overview of the report . . . . . . . . . . . . . . . . . . . . . .

4 4 4 5

2 System Analysis 2.1 Requirements speciďŹ cation . . . . . 2.1.1 Functional requirements . . 2.1.2 Non-functional requirements 2.2 Requirements analysis . . . . . . . 2.2.1 Use-case modeling . . . . . 2.2.2 Process modeling . . . . . . 2.2.3 Data modeling . . . . . . . 2.2.4 System Architecture . . . . 3 System Prototyping 3.0.5 Login Screen . . . 3.0.6 Main Screen . . . . 3.0.7 New ProďŹ le Screen 3.0.8 Reports Screen . .

. . . .

. . . .

4 Conclusions

. . . .

. . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

. . . .

. . . . . . . .

6 . 6 . 6 . 7 . 8 . 8 . 9 . 13 . 14

. . . .

15 15 16 17 18

. . . .

19

1


List of Figures

2.1 2.2 2.3 2.4 2.5 2.6 2.7

Use-Case Diagram . Context Diagram . . DFD Level 1 . . . . . DFD Level 2-1 . . . DFD Level 2-2 . . . ERD . . . . . . . . . System Architecture

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

8 9 10 11 12 13 14

3.1 3.2 3.3 3.4

Login screen . . . . . . . Main screen . . . . . . . Create new proďŹ le screen Reports screen . . . . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

15 16 17 18

2


List of Tables

4.1

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

3


Chapter

1

Introduction The security nowadays is one of the greatest issues in our life. All organization in the world must a have a strong security system to protect their valuables, here we are focusing on the problem of gate access security and how we can improve it.

1.1

Statement of the problem

In normal organizations, usually the security of their gates is monitor manually 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 are proposing an idea that will save a lot of time as well as will give the security department 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 image of each vehicle that accesses the organization. This image will be stored in a database with its full information (Time, Gate, Officer etc). This system can be installed in every gate at any organization, and can be used by the security officers and the security head departments. The system will save time and effort on the security officers and will give the security head department a lot more control.

4


1.3

Overview of the report

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

5


Chapter

2

System Analysis This Chapter is dedicated to requirements analysis.

2.1

Requirements specification

The requirements were gathered by discussing the security needs of any organization with the supervisor and by consulting some people who worked in the security field.

2.1.1

Functional requirements

The functional requirement is divided in to a user requirement and system requirement, just to give the reader more idea about the system and its functionalities. 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. 2. 3. 4. 5.

Insert officer data. Update officer data. Assign officer to gate. Assign officer to camera. 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 15

images per the minute. 2. Easy to use: The users of the system will have no problem using the system as it has a very simple and friendly interface. 3. Reliability: The system should handle the pressure and never 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

3

System Prototyping 3.0.5

Login Screen

Figure 3.1: Login screen

This is the ďŹ rst screen that will face the gate oďŹƒcer to insert the user name and the password which already been entered by the manager.

15


3.0.6

Main Screen

Figure 3.2: Main screen

This will be the main screen of the system, which will allow the manager to control the whole system from. It is divided in to four sections, Gate, Camera, OďŹƒcer 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 to the system. It contains all the data necessary to be saved in the officer 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 user the ability to print the report.

18


Chapter

4

Conclusions The Gate Access Control System is a system that focuses mainly on the security of organization gates. This system will help to solve a lot of issues that existed in the manually systems. We divided 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 system functionality. • Finally, writing the report. Table 4.1: Time Table NO Task Duration 1 Discussing the useability of the system 2 Days 2 Collecting the requirement 7 days 3 Analyzing the system 32 days 4 Making the prototype 7 days 5 Writing the report 10 days 6 Rewriting the report using Latex 7 days

Start Finish 13/03 15/03 15/03 22/03 22/03 23/04 23/04 30/04 30/04 10/05 10/05 17/05

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

Accsess gate control  

Accsess gate control

Read more
Read more
Similar to
Popular now
Just for you