SUSPECT DETECTION USING IMAGE

PROCESSING

By
Zeeshan Liaqat
(15-Arid-992)
Ahsan
(15-Arid-826)

Kashif Qureshi
(15-Arid-872)

Supervised by
Ms. Farkhanda Qamar

UNIVERSITY INSTITUTE OF INFORMATION TECHNOLOGY

PMAS ARID AGRICULTURE UNIVERSITY
RAWALPINDI
2019
SUSPECT DETECTION USING IMAGE
PROCESSING

By
Zeeshan Liaqat
(15-Arid-992)
Ahsan
(15-Arid-826)
Kashif Qureshi
(15-Arid-872)

Supervised by
Ms. Farkhanda Qamar

A PROJECT SUBMITTED IN PARTIAL FULFILLMENT OF THE

REQUIREMENTS OF THE DEGREE OF

BACHELOR OF SCIENCE IN COMPUTER SCIENCE

(BSCS)

UNIVERSITY INSTITUTE OF INFORMATION TECHNOLOGY

PMAS ARID AGRICULTURE UNIVERSITY
RAWALPINDI
2019

II
Dedicated to our beloved parents and to all those,
whose prayers always pave to the success for us

III
 PROJECT IN BRIEF

Project Title: Suspect Detection using Image Processing

Organization: University Institute of Information Technology

Undertaken By: Zeeshan liaqat (15-ARID-992)

Ahsan (15-ARID-826)
Kashif Qureshi (15-ARID-872)

Supervised by: Ms. Farkhanda Qamar

Date Started: 1st October, 2018

Date Completed: 1rd July, 2019

Technology Used: C# with OpenCV library

Operating System: Windows 10

System Used: Dell Ci7, 700 GB HDD, 8 GB RAM

IV
 ACKNOWLEDGMENT

Our deepest gratitude goes to ALMIGHTY GOD who has provided all that was
needed to complete this project and the program for which it was undertaken for.
There was never lack or want. Throughout this entire study, He took care of
everything that would have stopped us in our tracks and strengthened us even through
our most difficult times.

We would like to thank and sincerely acknowledge the help of our supervisor Ms.
Farkhanda Qamar whose complete guidance, support and encouragement gave us a
real motivation in doing this project. Sincere Thanks for her support and helpful
suggestions, we will be forever thankful to you.

We would like to thank all the volunteers especially Sir Imran Khurram who helped
us out while testing of this application and all the faculty members of UIIT
department for their help, time, and support that was gladly given to us on the time of
need.

Not least of all, we owe so much to our families for their undying support, their
unwavering belief that we can achieve so much. Unfortunately, we cannot thank
everyone by name because it would take a lifetime but, we just want you all to know
that you count so much. Had it not been for all your prayers and benedictions; were it
not for your sincere love and help, we would never have completed this project. So
thank you all.

Zeeshan Liaqat

(15-ARID-992)

Ahsan

(15-ARID-826)

Kashif Qureshi

(15-ARID-872)

V
 DECLARATION

We hereby declare that this project, neither whole nor as a part has been copied out
from any source. It is further declared that we have developed this project and
accompanied report entirely on the basis of our personal efforts. If any part of this
project is proved to be copied out from any source or found to be reproduction of
some other. We will stand by the consequences. No Portion of the work presented has
been submitted of any application for any other degree or qualification of this or any
other university or institute of learning.

Zeeshan Liaqat

(15-ARID-992)

Ahsan

(15-ARID-826)

Kashif Qureshi

(15-ARID-872)

VI
 CERTIFICATION

It is certified that the contents and form of the project entitled “SUSPECT
DETECTION USING IMAGE PROCESSING” submitted by Zeeshan liaqat (15-
arid-992), Ahsan (15-arid-826) and Kashif Qureshi (15-arid-872) has been found
satisfactory for the requirements of

PMAS – Arid Agriculture University, Rawalpindi

For the award of the degree of

BACHELOR OF SCIENCE IN COMPUTER SCIENCE (BSCS)

Supervisor:
Ms. Farkhanda Qamar

Examiner 1:
Mr. Asif Nawaz

Examiner 2:
Ms. Bushra Hamid

Dated: 5th August, 2019

Director: ________________________

Prof. Dr. Mobushir Raiz Khan

VII
 ABSTRACT

Over the years, a lot of security approaches have been developed that help in keeping
confidential data secured and limiting the chances of a security breach. Face
recognition which is one of the few biometric methods that possess the merits of both
high accuracy and low intrusiveness is a computer program that uses a person’s face
to automatically identify and verify the person from a digital image or a video frame
from a video source. It compares selected facial features from the image and a face
database, or it can also be a hardware which used to authenticate a person. This
technology is a widely used biometrics system for authentication, authorization,
verification and identification. A lot of company has been using face recognition in
their security cameras, access controls and many more. Facebook has been using face
recognition in their website for creating a digital profile for the people using their
website. In developed countries, the law enforcement creates face database to be used
with their face recognition system to compare any suspect with the database or to
authenticate a verified person. For example, we have seen many cases where
unauthorized person enters the organization having fake Ids. On the other hand, it’s
also common that many students instead of sitting himself in examination halls send
to some other person who attempts a exam on the behalf of invoker student which is
also a leading issue in order to ensure integrity of any educational institute. The
intended system is all concerned about dealing with security issues, or unauthorized
entry, or infiltration. The system takes the images of authorized person/users via
special camera and stores the capture images into the Database. Then at entry point, or
in the premises where the system is installed, it takes the pictures of passing persons
and compare it with the current Database, if pictures matches with the current
database, it means the person is authorized and if the captured picture is not matched,
It will consider it as SUSPECT, then it generates an alert to control room, or admin
room and they will take precaution measurements action against suspect.

VIII
 TABLE OF CONTENTS

PROJECT IN BRIEF ............................................................................................ IV

ACKNOWLEDGMENT .......................................................................................... V

DECLARATION .................................................................................................... VI

CERTIFICATION ................................................................................................ VII

ABSTRACT ......................................................................................................... VIII

TABLE OF CONTENTS ....................................................................................... IX

LIST OF FIGURES ............................................................................................. XIII

LIST OF TABLES ................................................................................................ XIV

Chapter 1....................................................................................................................1

INTRODUCTION ......................................................................................................1

1.1 BRIEF .................................................................................................................2

1.2 PROJECT AIM .....................................................................................................2

1.3 PROJECT OBJECTIVES ......................................................................................2

1.3 SCOPE OF THE PROJECT .................................................................................3

1.4 PROBLEM STATEMENT ...................................................................................3

1.5 PROPOSED SOLUTION......................................................................................4

1.6 CHAPTER SUMMARY .......................................................................................6

Chapter 2....................................................................................................................7

REQUIREMENT ANALYSIS ....................................................................................7

2.1 PROJECT DESCRIPTION ...................................................................................7

2.2 FUNCTIONAL REQUIREMENTS ......................................................................7

2.3 NON-FUNCTIONAL REQUIREMENT ...............................................................8

2.4 CHAPTER SUMMARY .......................................................................................8

Chapter 3....................................................................................................................9

IX
SOFTWARE DESIGN ................................................................................................9

3.1 USE CASE DIAGRAM ........................................................................................9

3.2 ACTIVITY DIAGRAM ...................................................................................... 10

3.5 CLASS DIAGRAM ............................................................................................ 12

3.6 DEPLOYMENT DIAGRAM .............................................................................. 14

3.7 COMPONENT DIAGRAM ................................................................................ 14

3.8 ENTITY-RELATIONSHIP DIAGRAM .............................................................. 16

3.9 SEQUENCE DIAGRAM .................................................................................... 17

3.8 CHAPTER SUMMARY ..................................................................................... 17

Chapter 4.................................................................................................................. 20

PROJECT MANAGEMENT .................................................................................... 20

4.1 MILESTONES .................................................................................................... 20

4.2 PROJECT CLOSEOUT REPORT ....................................................................... 21

4.3 OPERATION AND MANAGEMENT PLAN ..................................................... 22

4.4 PROJECT RESOURCES .................................................................................... 22

4.5 RISK MANAGEMENT ...................................................................................... 23

4.6 RISK-RESPONSE .............................................................................................. 23

4.7 CHAPTER SUMMARY ..................................................................................... 24

Chapter 5.................................................................................................................. 25

PROJECT IMPLEMENTATION............................................................................... 25

5.1 PROGRAMMING LANGUAGE ........................................................................ 25

5.2 FRAMEWORK................................................................................................... 25

5.3 SYSTEM REQUIREMENTS .............................................................................. 25

5.4 CHAPTER SUMMARY ..................................................................................... 26

Chapter 6.................................................................................................................. 27

SOFTWARE TESTING ............................................................................................ 27

X
6.1 DERIVING TEST ............................................................................................... 27

6.2 TEST ENVIRONMENT ..................................................................................... 27

6.3 TESTING IDENTIFICATION ............................................................................ 27

6.4 TEST PROCEDURE ........................................................................................... 27

6.5 TESTING TECHNIQUES................................................................................... 28

6.5 TEST CASES...................................................................................................... 29

6.7 CHAPTER SUMMARY ..................................................................................... 35

Chapter 7.................................................................................................................. 36

CONCLUSION AND FUTURE WORK ................................................................... 36

7.1 DISCUSSION ..................................................................................................... 36

7.2 CONCLUSION ................................................................................................... 37

7.3 LIMITAITIONS .................................................................................................. 37

7.4 FUTURE WORK ................................................................................................ 38

Chapter 8.................................................................................................................. 39

SCREENSHOTS ...................................................................................................... 39

8.1 REGISTRATION PAGE ..................................................................................... 39

8.2 LOGIN PAGE ..................................................................................................... 40

8.3 ADMINISTRATOR PANEL ............................................................................... 41

8.4 MODEL TRAINING........................................................................................... 42

8.5 ADMINISTRATOR PASSWORD CHANGING ................................................. 43

8.6 RECORD REPOSITORY.................................................................................... 44

8.7 DATABASE REGISTRATION ........................................................................... 45

8.8 SYSTEM MAINTENANCE ............................................................................... 46

8.9 DATA TIME........................................................................................................ 47

Chapter 9.................................................................................................................. 48

REFERENCES AND BIBLIOGRAPHY .................................................................. 48

XI
9.1 REFRENCES ...................................................................................................... 48

XII
 LIST OF FIGURES

FIGURE 1.1: PROJECT AIM ................................................................................ 2

FIGURE 1.2: PROPOSED SOLUTION................................................................. 5

FIGURE 1.3: PROPOSED SOLUTION................................................................. 6

FIGURE 3.1: USE CASE DIAGRAM ................................................................... 9

FIGURE 3.2: TRAINING AND STORING IMAGES.......................................... 11

FIGURE 3.3 MATCHING FROM LIVE FOOTAGE ........................................... 12

FIGURE 3.4: CLASS DIAGRAM ....................................................................... 13

FIGURE 3.5: DEPLOYMENT DIAGRAM ......................................................... 14

FIGURE 8.4: MODEL TRAINING ..................................................................... 42

FIGURE 8.5: ADMINISTRATOR PASSWORD CHANGING ............................ 43

FIGURE 8.6: RECORD REPOSITORY .............................................................. 44

FIGURE 8.7: DATABASE REGISTRATION ...................................................... 45

FIGURE 8.8: SYSTEM MAINTENANCE .......................................................... 46

FIGURE 8.9: DATE TIME .................................................................................. 47

FIGURE 3.5: COMPONENT DAIGRAM ........................................................... 15

FIGURE 3.6: ENTITY RELATIONSHIP DIAGRAM ......................................... 16

FIGURE 3.7.1: LOGIN........................................................................................ 17

FIGURE 3.7.2: CAPTURING AND MATCHING IMAGES ............................... 18

FIGURE 3.7.3: SAVING IMAGES ...................................................................... 19

FIGURE 8.1: REGISTRATION PAGE ................................................................ 39

FIGURE 8.2: LOGIN PAGE ................................................................................ 40

FIGURE 8.3: ADMINISTRATOR PAGE ............................................................. 41

XIII
 LIST OF TABLES

TABLE 4.1: MILESTONES ................................................................................. 20

TABLE 4.2: PROJECT CLOSEOUT REPORT..................................................... 21

TABLE 4.6: RISK REPONSE .............................................................................. 23

TABLE 6.1: TEST CASE 1 .................................................................................. 29

TABLE 6.2: TEST CASE 2 .................................................................................. 30

TABLE 6.3: TEST CASE 3 .................................................................................. 31

TABLE 6.4: TEST CASE 4 .................................................................................. 32

TABLE 6.5: TEST CASE 5 .................................................................................. 33

TABLE 6.6: TEST CASE 6 .................................................................................. 34

XIV
 Chapter 1

INTRODUCTION

Over the years, a lot of security approaches have been developed that help in keeping
confidential data secured and limiting the chances of a security breach. Face recognition
which is one of the few biometric methods that possess the merits of both high accuracy
and low intrusiveness is a computer program that uses a person’s face to automatically
identify and verify the person from a digital image or a video frame from a video source.
It compares selected facial features from the image and a face database, or it can also be a
hardware which used to authenticate a person. This technology is a widely used
biometrics system for authentication, authorization, verification and identification. A lot
of company has been using face recognition in their security cameras, access controls and
many more. Facebook has been using face recognition in their website for creating a
digital profile for the people using their website. In developed countries, the law
enforcement creates face database to be used with their face recognition system to
compare any suspect with the database or to authenticate a verified person. For example,
we have seen many cases where unauthorized person enters the organization having fake
Ids. On the other hand, it’s also common that many students instead of sitting himself in
examination halls send to some other person who attempts exam on the behalf of invoker
student which is also a leading issue in order to ensure integrity of any educational
institute. The intended system SUSPECT DETECTION USING IMAGE
PROCESSING is all concerned about dealing with security issues, or unauthorized entry,
or infiltration. The system takes the images of authorized person/users via special camera
and stores the capture images into the Database. Then at entry point, or in the premises
where the system is installed, it takes the pictures of passing persons and compare it with
the current Database, if pictures matches with the current database, it means the person is
authorized and if the captured picture is not matched, It will consider it as SUSPECT,
then it generates an alert to control room, or admin room and they will take precaution
measurements action against suspect .

1
1.1 BRIEF

Suspect Detection System is all concerned about dealing with security issues, or
unauthorized entry, or infiltration. As over the past few years, we learnt about different
cases of intrusion in UIIT where outsider students attempted to sit in exams on the behalf
of another student which is an emerging issue and we need to take swift actions to tackle
this sort of problems. So, the proposed system is used to detect intruders and adopts
proactive approach to avoid unpleasant experience. The system takes the images of
authorized person/users via special camera and stores the capture images into the
Database. Then at entry point, or in the premises where the system is installed, it takes the
pictures of passing persons and compare it with the current Database, if captured image
matches with the current database of authorized people, it means the person is authorized
and if the captured picture is not matched, It will consider it as SUSPECT or INTRUDER,
then it generates an alert to control room, or administration room and they will take
precaution measurements action against suspect.

1.2 PROJECT AIM

Our aim is to develop an application that ensure security or to avoid any sort of intrusion
or illegal entrance to place where only authorized people are allowed to enter. It also deals
to tackle any sort of unpleasant situation in advance and Security issues.

Figure 1.1: Project Aim

1.3 PROJECT OBJECTIVES

 Detects unauthorized personnel entry and provides a prompt notice for the response
force to respond to an alarm event.

2
 To achieve such a security system which will provide a better way to overcome
intrusion or any sort of infiltration within organization.
 Different type of tools and technologies makes it possible to develop such system,
different hardware equipment’s like Camera’s will also be entertained in it.
 Ensures integrity or safety of organization or university.
 Give new possibilities to do old things, thus removing the fear about new technologies
as hinderer of old fashions.

1.3 SCOPE OF THE PROJECT

Administrator: First administrator will perform registration and logins into system.
System enables administrator to login to system with specified credentials and it monitors
the application with given Admin Dashboard. Administrator can further register and
delete security users who monitor application. Security User: Security user must have
valid username and password to login to System. After logging in, user can monitor live-
footage of connected camera. User can also train model of images and further can
perform database registration of individuals such as student, teacher and staff member.
Suspect Detection Engine: I installed or connected camera with the application takes
picture of individual person crossing a door or even sitting in examination hall. System
will have a database which saves pictures of authorized person only. So at the point of
entry camera takes pictures of person and matches it with the database using face
recognition or image processing algorithms using deep learning and if picture matches
with the database then its fine otherwise it generates an alert to admin indicating that
suspect might have entered the organization and then administrator of the system takes an
appropriate actions to tackle any sort of unpleasant event.

1.4 PROBLEM STATEMENT

Over the years, we have seen many cases where outsider who are not a part of
organization like they are not a student of university, entered the university and attempted
to sit in examination hall on the behalf of another student. Security guards are also not
able to identify the students properly, because they identify students based on ID card.
Security guard is also not paying heed, they are just checking the card and mostly people
show fake card and they allow them to enter. So, in that case, such issue can cause be a
3
big security threat to the university. By doing this project we will able to overcome this
issue.

1.5 PROPOSED SOLUTION

Proposed system can be utilized effectively to handle above mentioned problems. It will
have three components, first an installed camera which will take picture of authorized
people, second a database to store that images for further processing and then suspect
detection engine. So first we will take images of authorized people and store it into
database, after that camera will be placed at the entry position where it will capture
images of passing person and will pass it to suspect Detection Engine to compare it the
stored images in the database, if image matches it means that person is authorized,
otherwise it generates an alert and administrator take further action to avoid any sort of
unpleasant experience.

4
1.5.1 PRIMARY STAGE:

Figure 1.2: Proposed Solution

5
 1.5.2 SECONDARY STAGE:

Figure1.3: Proposed Solution

1.6 CHAPTER SUMMARY

In this chapter we told all about our project that we have done in our project like how we
manage the monthly bills, monthly grocery order remainder, daily cooking items
remainder, payable/receivable remainder, and mobile modes changing notification on
specific places, too much time to call someone remainder. So in this chapter we conclude
that how our project flows in specific time and how it works after final product.

6
 Chapter 2

REQUIREMENT ANALYSIS

2.1 PROJECT DESCRIPTION

The intended system SUSPECT DETECTION USING IMAGE PROCESSING is all

concerned about dealing with security issues, or unauthorized entry, or infiltration. The
system takes the images of authorized person/users via special camera and stores the
capture images into the Database. Then at entry point, or in the premises where the system
is installed, it takes the pictures of passing persons and compare it with the current
Database, if pictures matches with the current database, it means the person is authorized
and if the captured picture is not matched, It will consider it as SUSPECT, then it
generates an alert to control room, or admin room and they will take precaution
measurements action against suspect.

2.2 FUNCTIONAL REQUIREMENTS

Functional Requirement 1
ID: FR1.
Title: Admin registration.
Description: Admin logged in with valid credentials.

Functional Requirement 2
ID: FR2.
Title: Live footage capturing.
Description: From live footage, system take picture of person entering in the
university and send it to the detection engine for processing.

Functional Requirement 3
ID: FR3
Title: Train the model.
Description: System first takes the images at least 20 per person for proper
training of model and then the algorithm will process them.
7
 Functional Requirement 4

ID: FR4

Title: Matching with saved images.

Description: Matches the image with the saved image of student .if picture
doesn’t match, admin has been alarmed and he/she take particular action against
suspect.

2.3 NON-FUNCTIONAL REQUIREMENT

2.3.1 USABILITY

Our project is helpful/useful all kinds of users. Our system met (effectively) user goals in
an efficient manner .Our system will be used in a context where people don’t have time to
manage daily life activities. It is useful for expansion of stores business.

2.3.2 RELIABILITY

Our system is reliable and efficient when internet connection is on otherwise our system
may fail to fulfil module requirement.

2.3.3 INTEGRITY

Our system save all the states and used even after recovery.

2.3.4 PERFORMANCE

Our project save user time and send timely Notification. Our system helps to prevent from
penalties and user save recourses.

2.4 CHAPTER SUMMARY:

This chapter concludes that how our project works and the main discussions in this
chapter are the functional and non-functional requirements of our project.

8
 Chapter 3

SOFTWARE DESIGN

3.1 USE CASE DIAGRAM

Figure 3.1: Use Case

9
3.2 LOGIN ACTIVITY DIAGRAM

Figure 3.2: Login

10
3.3 TRAINING AND STORING IMAGE ACTIVITY DIAGRAM

Figure 3.3 Training and Storing Images

11
3.4 MATCHING FROM LIVE FOOTAGE ACTIVITY DIAGRAM

Figure 3.4: Matching From Live Footage

12
3.5 CLASS DIAGRAM

Figure 3.5: Class Diagram

13
3.6 DEPLOYMENT DIAGRAM

Figure 3.6: Deployment Diagram

14
3.7 COMPONENT DIAGRAM

Figure 3.7: Component Diagram

15
3.8 ENTITY-RELATIONSHIP DIAGRAM

Figure 3.8: Entity Relationship Diagram

16
3.9 LOGIN SEQUENCE DIAGRAM

Figure 3.9: Login

17
3.10 CAPTURING AND MATCHING IMAGES SEQUENCE
DIAGRAM

Figure 3.10: Capturing and Matching Images

18
3.11 SAVING IMAGES

Figure 3.11: Saving Images

3.8 CHAPTER SUMMARY

In this chapter, we briefly described the UML part of our project which includes user case,
extended use case, sequence, activity diagram (which model the work flow of the system
and sequence of activities in a process), class diagram, component diagram, deployment
diagram (which represent physical relationship different components) and ERD diagram
as well .These diagrams elaborates the project efficiently.

19
 Chapter 4

PROJECT MANAGEMENT

4.1 MILESTONES

In a reference to project management, a milestone is a special event that requires special

attention. Milestones can add significant value to project scheduling. They help project
managers to more accurately determine whether or not the project is on schedule. We
assign priorities to the milestones of our project so in this way we can achieve our goal
more easily.

Table 4.1: Milestones

Milestone Name: Description:

Requirement’s This phase includes collection of functional and non-

Collection: functional requirements of the project.

Idealistic view of the desired outcomes to be produced after

Project’s Vision:
successful project completion.

Software Requirements In this phase we have to collect the entire Software

specification: requirement Specification.

At this point, we assure weather, our system fulfilling all the

Assuring the System:
functional and non-functional requirements and have all the
basic need that are leading to successful completion of
system.

20
4.2 PROJECT CLOSEOUT REPORT

Project close-out finalizes all project activities completed across all phases of the project
to formally close the project and transfer the completed or cancelled project as
appropriate. The purpose of project closeout is to assess the project, ensure completion,
and derive any lessons learned and best practices to be applied to future projects.

At the end of any project, a close out report has to be submitted. This means that there has
to be an official conclusion to a project, indicating that the project has come to an end;
that funds and resources will not be needed anymore and the business operations will
continue as normal prior to the conception of the project. Manpower will have to be
restored back to their respective departments and contracts with suppliers will have to be
terminated.

Table 4.2: Project Closeout Report

Deliverables Date Condition

Proposal: November 2018 We will develop suspect detection

system using image processing
technique.

Software December 2018 We will list-down all the Functional and

requirements NF requirements for the SDIP.
specifications

Design Feb 2019 We have to make all the required

interfaces of our system.

Development March 2019 We have to code face detection and

recognition.

Testing May 2019 We’ll make sure that all requirements

21
 must be fulfill.

Debugging 30 May 2019 We will debug the system using some

tools.

Code Review June 2019 Review the code after all the testing and
debugging.

Documentation July 2019 We will design the help/booklet for the

user’s guide.

4.3 OPERATION AND MANAGEMENT PLAN

Operations and maintenance is an integral part of project management. The maintenance

basically defines the post software maintenance to make the system more reliable. All the
testing operation is performed to check the accuracy of our system, to check whether it
exactly perform in the way we want. The task of this phase is the proper function of the
system. Software management plan involves detecting and correcting errors, as well as
expanding and improving software itself. If any changes are required, we immediately
take action to make it more efficient system. The system is capable of performing the
multiple operations with good response time.

4.4 PROJECT RESOURCES

In project management, resources are required to carry out the project tasks. They can be
people, equipment, facilities, funding, or anything else capable of definition (usually other
than labor) required for the completion of a project activity. The lack of a resource will
therefore be a constraint on the completion of the project activity. Resources may be
storable or non-storable. Storable resources remain available unless depleted by usage,
and may be replenished by project tasks which produce them. Non-storable resources
must be renewed for each time period, even if not used in previous time periods.
Resource scheduling, availability and optimization are considered key to successful
project management.

22
4.5 RISK MANAGEMENT

Risk Management involves identifying, analyzing and responding to a risk factors

thorough out the life of project and the best interest of its objectives. A good system is a
one who manages all the risks that could occur in the future. Could system minimize the
risk to almost zero? We are trying our best to provide risk free system. Risks are generally
avoided or accepted.

4.6 RISK-RESPONSE

The risk response planning involves determining ways to reduce or eliminate any threats
to the project, and also the opportunities to increase their impact. Project managers should
work to eliminate the threats before they occur. Some of the risks that can occur in our
project completion are given below:

Table 4.6: Risk Response

Risk Priority Risk # Risk Name Responsible Action

person

High RSK-1 Database DB Admin Show message

crashed to overlook it.

Low RSK-2 Camera System installer Notify about

cam
failed
connection.

High RSK-3 System Crash Developer Handle all

exceptions.

23
4.7 CHAPTER SUMMARY

In this chapter we assign milestone to our project according to our project analysis. We
also provide a very short description of each milestone of our project from requirement
gathering to the project testing phase. After assigning milestone to our project, we prepare
a project closeout report, in short deliverables of our project. We provide each
deliverables of our project with the time to be delivered. Then we cover the operation and
the management plan phase. In this phase, we describe how our project can be managed
in order to perform well and how to detect errors and maintenance. The performance
requirement of the system is listed in detail that describes response time, accuracy and
efficiency of the system.

24
 Chapter 5

PROJECT IMPLEMENTATION

5.1 PROGRAMMING LANGUAGE

The language we’ve used in our project is C# with EmguCV. C# provides better
functionalities as compared to other programming languages. The main purpose to use C#
is to make system better and efficient. EmguCV is image processing library that we have
used for facial detection and recognition.

5.2 FRAMEWORK

A framework is an abstraction in which providing generic functionality can be selectively

changed by additional user-written code, thus providing application-specific software.
A software framework provides a standard way to build and deploy applications.

5.2.1: NET FRAMEWORK:

It is a programming infrastructure for building, deploying, and running applications and

services that use .NET technologies, such as desktop applications and Web services etc.
We have used it because it provides better interaction with C# code and also with C++.

5.3 SYSTEM REQUIREMENTS

 This software requires system above Pentium 4.

 System must have minimum dual core processors
 Minimum 2GB of RAM.
 5GB of internal storage.
 OS can be windows 7, 8 or 10.
 System must have .Net Framework Support.
 System is able to support the latest version of SQL server.

25
5.4 CHAPTER SUMMARY

In this chapter, we explained the implementation phase of the project. Programming

language explains which language has been used to develop this application. Framework
has described which platform is used to design this application. System requirements
show on which devices this application can be run upon. We have discussed all the above
parameters in the detail.

26
 Chapter 6

SOFTWARE TESTING

6.1 DERIVING TEST

The desktop - Application upgraded (added features) occasionally for different reasons.
Requirement listed in SRS document were used as a baseline for testing to ensure that the
existing and new functionality are working. Test case is derived for each requirement as a
way of proving that the system or changes being implemented is ready for day to day
business use without error and/or adverse impact on the existing functionality.
Requirement itself changed from time to time and some become obsolete and to be
removed together with the test case.

6.2 TEST ENVIRONMENT

This desktop application is tested with the required hardware and software requirements.
The software configuration is Windows 10 Home edition on the given hardware devices:
 Dell Vostro i7 7th generation.
 HP core i5 5th generation.

6.3 TESTING IDENTIFICATION

A test was planned for every requirement to test the application. The test procedure
adopted was detailed so that the system meets all requirements listed in SRS. The tests
were executed systematically and its output verified, sequentially.

6.4 TEST PROCEDURE

Manual testing is the process of manually testing software for defects. It requires a tester
to play the role of an end user whereby they utilize most of the application's features to
ensure correct behavior. To guarantee completeness of testing, the tester often follows a
written test plan that leads them through a set of important test cases.

27
6.5 TESTING TECHNIQUES
Three types of testing techniques were used to make wellbeing of Application.

6.5.1 Smoke Test

Smoke Testing, also known as “Build Verification Testing”, is a type of software testing
that comprises of a non-exhaustive set of tests that aim at ensuring that the most important
functions work. The results of this testing is used to decide if a build is stable enough to
proceed with further testing.

6.5.2 Functional Test

Functional testing is a software testing process used within software development in

which software is tested to ensure that it confirms to all requirements. Functional testing
is a way of checking software to ensure that it has all the required functionality that's
specified within its functional requirement.

6.5.3 System Testing

When all the units were working properly and unit testing was performed then came
time for system testing in which we will check all the integrated components and so
looked for whole possible discrepancies, which could have arisen after the integration

6.5.4 Recovery Testing

The application should be fault tolerant. So it has ability to recover from the errors as
soon as possible and resume the working which has been affected.

28
6.6 TEST CASES

The following test cases are prepared for each test that needs to be performed. The test
cases result in development of test reports, which will be further used for test-output
analysis.

Table 6.6.1 TestCase-1

TestCase-1

Software: SDIP Module: Registration Module

Test Name: Registration Test ID: TestCase-1

Test Description: This test Registers the Administrator at the time of system
initialization.

Pre-Condition: Administrator can access registration page.

Post-Condition: Administrator is successfully registered.

Action Action(s) Valid Invalid Input Required Output

Performed Input Input Output
Output

Enter user Displayed Same Either of Valid Successfully As

name and in allotted UserName or both the Registered. required
password. fields. and user name
Password and
will be password
used for is
sign in. incorrect.

Tested By: Zeeshan Liaqat

29
 Table 6.6.2 TestCase-2

TestCase-1

Software: SDIP Module: Login Module

Test Name: Authentication Test ID: TestCase-2

Test Description: The test verifies the user name and password to get access on system.

Pre-Condition: User can successfully login.

Post-Condition: User is successfully signed up.

Action Action(s) Valid Invalid Input Required Output

Performed Input Input Output
Output

Enter user Displayed Correct Either of Valid Successfully As

name and in allotted name and or both signed in. required
password. fields. correct the user
password, name or
password
absolutely
is
same as
incorrect
when you
sign up a
form.

Tested By: Zeeshan Liaqat

30
 Table 6.6.3 TestCase-3

TestCase-3

Software: SDIP Module: Security User Registration

Test Name: User Registration Test ID: TestCase-3

Test Description: Application must be able to receive data from database And send data
to database server.

Pre-Condition: Application must be in running phase.

Post-Condition: Order Data Showed.

Action Action(s) Valid Invalid Input Required Output

Performed Input Input Output
Output

Enter User- Entered Assign Required Click Regarding As

Name and data will be appropriate fields not Save status will required
Password stored in username filled button on be shown.
for new the and correctly form.
user. database. password
that doesn’t
exist
already

Tested By: Zeeshan Liaqat

31
 Table 6.6.4 TestCase-4

TestCase-4

Software: SDIP Module: Security user Module

Test Name: Authentication Test ID: TestCase-4

Test Description: The test verifies the user name and password to get access on system
as user

Pre-Condition: User can successfully login

Post-Condition: User is successfully signed up

Action Action(s) Valid Input Invalid Input Required Output

Performed Input Output
Output

Enter user Displayed Correct name Either of Valid Successfully As

name and in allotted and correct or both logged in. required
password. fields. password, the user
name and
absolutely
password
same will be
is
used as
incorrect.
registered by
Administrator

Tested By: Zeeshan Liaqat

32
 Table 6.6.5 TestCase-5

TestCase-5

Software: SDIP Module: Model/Image Training

Test Name: Face Recognition Model Training Test ID: TestCase-5

Test Description: This test takes face images of persons and trains the face recognition
model.

Pre-Condition: Application must be in running phase.

Post-Condition: Successfully trained faces for detection and recognition in future.

Action Action(s) Valid Input Invalid Input Required Output

Performed Input Output
Output

System Once Face must Not Train Successfully As

uses install trained, be trained training detected trained required
camera to System with different frontal face and Model
detect face will expressions face and assign
of person recognition for accuracy training label to
and then person enhancement. images that face
train the when where such as
model with detected in face is name of
faces. camera not person
with its covered or ID.
given label properly.

Tested By: Zeeshan Liaqat

33
 Table 6.6.6 TestCase-6

TestCase-6

Software: SDIP Module: Model Face Recognition Accuracy

Test Name: System’s Face Recognition Test ID: TestCase-6

Accuracy Testing

Test Description: This test examines that either System recognizes the trained faces and
detects the unknown or untrained faces.

Pre-Condition: Application must be in running phase.

Post-Condition: System successfully identifies trained or untrained faces.

Action Action(s) Valid Invalid Input Required Output

Performed Output Input Input Output

System If Face Not Detected System As

uses install detected must be showing face will successfully required
camera to face is detected face automatically distinguishes
detect face trained with correctly passed to trained and
of person face then proper to being model to untrained
and then displays face detected check that faces and
matches its label, attributes, by either its generates
that with otherwise based on System. trained or alert in case
already frontal untrained. of untrained
consider
trained face. face.
it
images unknown

Tested By: Zeeshan Liaqat

34
6.7 CHAPTER SUMMARY

We have discussed about testing. The test cases show the functionality of Application.
Each test is assigned a Test Name & Test Number. Test description shows what the aims
of this test procedure are. What are the points need to be considering while testing are
discussed in Item to be tested. Specifications describe what input is given to the System,
what may be happening in output is described in expected out. What should be the output
is described in Actual output. At the end steps to perform the test are described in
Procedure Step to show how an actual test has been performed

35
 Chapter 7

CONCLUSION AND FUTURE WORK

7.1 DISCUSSION

In this chapter we will review the entire research thesis objectives and results. We will
emphasis on the scientific contributions that this research work made. At the end we will
give some prospective points for the future work of this research.

7.1.1. ACHIEVEMENTS

It’s a sense of achievement having developed our final project successfully. We thank
ALLAH Almighty for this grant. Before going through this project we had a good
knowledge of software engineering, but now we are independent. We had a very good
interaction with our respected supervisor’s Ms. Farkhanda Qamar who helped us
develop the system in time. During the development of the project, we learnt a lot. Our
learning is summarized below.

7.1.2. TIME & PROJECT MANAGEMENT

It had to be competed in 4 months timeframe. This goal was achieved through proper
planning of our project. In starting a careful analysis was prepared to enlist all the goals
and milestones for our project. After enlisting the goals we crafted a plan for time
management. Split the goals into small deliverables. Each deliverable was divided into
many smaller markers.

7.1.3. HOW TO INTERACT WITH THE USER

Since Application is developed for everyone, so we had a huge sea of potential users. So
we made use of a few of them. This helped us improve our understanding to manage a
complete project.

7.1.4. A GOOD KNOWLEDGE OF SYSTEM DESIGNING AND MODELING

A compete architecture design of the software is created during the software designing
phase. This design explains the static and dynamic behavior of the software and code as

36
well. The design of the software helped us in creating and implements the code
successfully.

7.1.5. LATEST TOOLS AND TECHNOLOGIES

C# is the most frequently updated and most used technology, whose market in the
software industry is very vast. Our project which is an desktop-based application helped
us in learning this new technology. For the development of our project we learnt and used
many different tools and technologies. This has greatly increased our learning experience.

7.2 CONCLUSION

Our system is a proof-of-concept that how new technologies like C# and its libraries can
help build better services and visuals for a better detection of intruders as compared to
other ones. And the database SQL server which provided us the vast storage for images
and it’s descriptions.

Completing our project in a very less budget, we can surely say that anyone who what
proper functionality of a system with least price tag can avail and deploy this software.

7.3 LIMITAITIONS

 First the system is not able to match the distant person’s face. Due to camera range
it can only detects and matches the person’s face with in 1 or 2 meter distance.
 System can’t detect the objects in low light, because in low light our software is
not able to detect the proper shape of anyone’s face.
 We can’t use more than one camera. As it only detects and matches only who is
in front of it.
 Using run time image capturing and matching, can result in flicker. I.e. will be a
bit shaky.
 The IP camera can be malfunction due to severe weather conditions. But we have
tried our best to used special camera that can deal with weather conditions.
 The cabling connected to camera and system can be burn out any time due to
voltage fluctuations. As it is an electronic thing.
 The software is not compatible with MAC , Linux , iOS, Android , Macintosh etc.
Only compatible with windows 7 and above.
37
7.4 FUTURE WORK

 We will use the latest surveillance camera that can detect far objects, faces etc. to
make our system more efficient.
 We make the software that is compatible with other Operating systems.
 Will make advancement so that anyone can connect more than one camera.
 Will use latest algorithms for detection and recognition of distant objects.
 Perform Better working also in low light.
 In future, we also looking forward to develop web based suspect detection
application

38
 Chapter 8

SCREENSHOTS

8.1 REGISTRATION PAGE

Figure 8.1 Registration Page

39
8.2 LOGIN PAGE

Figure 8.2 Login Page

40
8.3 ADMINISTRATOR PANEL

Figure 8.3 Administrator Page

41
8.4 MODEL TRAINING

Figure 8.4 Model Training

42
8.5 ADMINISTRATOR PASSWORD CHANGING

Figures 8.5 Administrator Password Changing

43
8.6 RECORD REPOSITORY

Figure 8.6 Record Repository

44
8.7 DATABASE REGISTRATION

Figure 8.7 Database Registration

45
8.8 SYSTEM MAINTENANCE

Figure 8.8 System Maintenance

46
8.9 DATA TIME

Figure 8.9 Date Time

47
 Chapter 9

REFERENCES AND BIBLIOGRAPHY

9.1 REFRENCES

 http://www.emgu.com/wiki/index.php/Main_Page
 https://ahmedopeyemi.com/main/face-detection-and-recognition-in-c-using-
emgucv3-0-opencv-wrapper-part-1/
 https://www.researchgate.net/publication/326348387_Real_Time_Facial_Recognition_
Using_Principal_Component_Analysis_PCA_And_EmguCV

48