Citizen Identification and Information Management System

WOLKITE UNIVERSITY
COLLEGE OF COMPUTING AND INFORMATICS

DEPARTMENT OF SOFTWARE ENGINEERING
STUDENT IDENTIFICATION USING FACE

RECOGNITION FOR WOLKITE UNIVERSITY
NAME OF STUDENTS ID NO
1. GOSA NEGASH CIR/145/08
3. HELEN SEKO CIR/162/08
4. TIGIST ABEBAW CIR/280/08
5. MICHAEL HARKISO CIR/214/08
6. NATINAEL ENGIDA CIR/230/08
PROJECT ADVISOR: MR. ALEMU WOLDIE
Wolkite University, Wolkite, Ethiopia

February 6, 2022
WOLKITE UNIVERSITY
COLLEGE OF COMPUTING AND INFORMATICS
DEPARTMENT OF SOFTWARE ENGINEERING
STUDENT IDENTIFICATION USING FACE

RECOGNITION FOR WOLKITE UNIVERSITY
SUBMITTED TO DEPARTMENT OF SOFTWARE ENGINEERING

IN PARTIAL FULFILMENT OF THE REQUIREMENT FOR
THE DEGREE OF BACHLER OF SCIENCE IN SOFTWARE ENGINEERING
BY
NAME OF STUDENTS ID NO
3. HELEN SEKO CIR/162/08
4. TIGIST ABEBAW CIR/280/08
5. MICHAEL HARKISO CIR/214/08
6. NATINAEL ENGIDA CIR/230/08
PROJECT ADVISOR: MR. ALEMU WOLDIE
Wolkite University, Wolkite, Ethiopia

February 6, 2022
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY I

DECLARATION
This is to declare that this project work which is done under the supervision of Mr. Alemu
Woldie and having the title Student Identification using Face Recognition for Wolkite University
is the sole contribution of Gosa Negash, Gosa Negash, Helen Seko, Tigist Abebaw, Michael
Harkiso, Natinael Engida.
No part of the project work has been reproduced illegally (copy and paste) which can be
considered as Plagiarism. All referenced parts have been used to argue the idea and have been
cited properly. We will be responsible and liable for any consequence if violation of this
declaration is proven.
Date: ___________________
Group Members:
Full name signature
Gosa Negash ____________________

Gosa Negash ____________________
Helen Seko ____________________
Tigist Abebaw ____________________
Michael Harkiso ____________________
Natinael Engida ____________________
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY II

APPROVAL FORM
This is to confirm that the project report entitled Student Identification using Face Recognition
for Wolkite University submitted to Wolkite University, College of Computing and Informatics
Department of Software Engineering by Gosa Negash, Gosa Negash, Helen Seko, Tigist
Abebaw, Michael Harkiso, Natinael Engida is approved for submission.
------------------------------------------------- ------------------------------ ----------
Advisor Name Signature Date
------------------------------------------------- ------------------------------ ----------
Department Head Name Signature Date
------------------------------------------------- ------------------------------ ----------
Examiner 1 Name Signature Date
------------------------------------------------- ------------------------------ ----------
------------------------------------------------- ------------------------------ ----------
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY III

ACKNOWLEDGMENT
We want to appreciate the almighty of God for the gift of life, protection, health, academic
success and for giving us the strength to prepare the first-semester final project documentation.
We want to thanks and appreciate our Parents for their support financially, morally and by
everything and also for their praying to us. We, almighty God, grants them long life on earth to
enjoy the fruit of their labor. We want to in a special way acknowledge our project advisor Mr.
Alemu Woldie for his support in the realization of this project work by advise us in all our
activity for preparing finally project documentation. We appreciate in a special way our
department head Mr. Frezer Guteta who providing different tools that help for doing this project
by advising and monitoring our activity closely. We thank our friends and for their good wish
whose name were not mentioned, we say our Lord bless you for what you done to us.
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY IV

TABLE OF CONTENTS
DECLARATION.......................................................................................................................II
APPROVAL FORM................................................................................................................III
ACKNOWLEDGMENT.........................................................................................................IV
LIST OF TABLES.................................................................................................................VII
LIST OF FIGURES..............................................................................................................VIII
ABBREVIATIONS AND ACRONYMS...............................................................................IX
ABSTRACT...............................................................................................................................X
CHAPTER ONE........................................................................................................................1
1. INTRODUCTION...........................................................................................................1
1.1. Background of the Organization....................................................................................1
1.2. Statement of the Problem...............................................................................................2
1.3. Objective of the project...................................................................................................2
1.3.1. General Objective.....................................................................................................2
1.3.2. Specific Objectives...................................................................................................2
1.4. Feasibility Analysis of the project..................................................................................3
1.4.1. Technical Feasibility................................................................................................3
1.4.2. Operational Feasibility............................................................................................3
1.4.3. Economical Feasibility.............................................................................................3
1.5. Scope and Limitation of the Project..............................................................................4
1.5.1. Scope of the project..................................................................................................4
1.5.2. Limitation of the project..........................................................................................4
1.6. Significance of the Project..............................................................................................4
1.6.1. Beneficiary of the Project........................................................................................4
1.7.1. Data Collection Tools/Techniques..........................................................................5
1.7.2. System Analysis and Design....................................................................................5
1.7.3. System Development Model....................................................................................5
1.7.4. Testing methodology................................................................................................6
1.7.5. Development Tools and Technologies....................................................................8
1.7.5.1. Frontend Technologies.....................................................................................8
1.7.5.2. Backend Technologies......................................................................................8
1.7.5.3. Documentation and Development Tools.........................................................8
1.7.5.4. Deployment Environments...............................................................................9
1.8. Document Organization..................................................................................................9
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY V

CHAPTER TWO.......................................................................................................................9
2. DESCRIPTION OF THE EXISTING SYSTEM.........................................................9
2.1. Introduction of the Existing System..............................................................................9
2.2. Users of Existing System...............................................................................................10
2.3. Major Functions of the Existing System.....................................................................11
2.4. Forms and Other Documents of the Existing Systems...............................................11
2.5. Drawbacks of the Existing System...............................................................................11
2.6. Business Rules of the Existing System.........................................................................12
CHAPTER THREE.................................................................................................................13
3. PROPOSED SYSTEM.................................................................................................13
3.1. Functional Requirements..............................................................................................14
3.2. Nonfunctional Requirements........................................................................................14
3.2.1. User Interface and Human Factors......................................................................14
3.2.2. Hardware Consideration.......................................................................................15
3.2.3. Security Issues........................................................................................................15
3.2.4. Performance Consideration..................................................................................15
3.2.5. Error Handling and Validation............................................................................15
3.2.6. Quality Issues..........................................................................................................15
3.2.7. Backup and Recovery............................................................................................16
3.2.8. Physical Environment............................................................................................16
3.2.9. Resource Issues.......................................................................................................16
3.2.10. Documentation........................................................................................................16
CHAPTER FOUR....................................................................................................................17
4. SYSTEM ANALYSIS...................................................................................................17
4.1. System Model.................................................................................................................17
4.1.1. Use Case Model......................................................................................................17
4.1.1.1. Use Case Diagram...........................................................................................19
4.1.1.2. Use Case Description......................................................................................19
4.1.1.3. Use case Scenario............................................................................................24
4.2. Object Model..................................................................................................................26
4.2.1. Class Diagram.........................................................................................................26
4.2.2. Data Dictionary......................................................................................................26
4.3. Dynamic Model..............................................................................................................28
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY VI

4.3.1. Sequence Diagram..................................................................................................28
4.3.2. Activity Diagram....................................................................................................32
4.3.3. State Chart Diagram..............................................................................................36
CHAPTER FIVE......................................................................................................................37
5. SYSTEM DESIGN........................................................................................................37
5.1. Design Goals...................................................................................................................37
5.1.1. Performance............................................................................................................37
5.1.2. Dependability..........................................................................................................37
5.1.3. Maintenance............................................................................................................37
5.1.4. End-user..................................................................................................................38
5.2. Current System Architecture.......................................................................................38
5.3. Proposed System Architecture.....................................................................................39
5.3.1. Subsystem Decomposition and Description.........................................................40
5.3.2. Hardware/Software Mapping...............................................................................41
5.3.3. Detailed Class Diagram.........................................................................................42
5.3.4. Persistent Data Management................................................................................43
5.3.5. Access Control and Security.................................................................................45
5.4. Packages.........................................................................................................................46
5.5. Algorithm Design...........................................................................................................47
5.6. User Interface Design....................................................................................................48
6. CONCLUSION..............................................................................................................49
7. RECOMMENDATION................................................................................................50
8. REFERENCE................................................................................................................51
9. APPENDIX....................................................................................................................52
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY VII

LIST OF TABLES
Table 1-1 Software tools..................................................................................................................8
Table 1-2 Hardware tools.................................................................................................................9
Table 2-1 Business rule 1...............................................................................................................12
Table 4-1 Use case description for enter........................................................................................20
Table 4-2 Use case description for login........................................................................................20
Table 4-3 Use case description for create account.........................................................................21
Table 4-4 Use case description for face detection.........................................................................22
Table 4-5 Use case description for face recognition......................................................................22
Table 4-6 Use case description for view alert................................................................................23
Table 4-7 Use case description view message...............................................................................23
Table 4-8 Use case description for send message..........................................................................24
Table 4-9 Data dictionary for student............................................................................................27
Table 4-10 Data dictionary for message........................................................................................28
Table 4-11 Data dictionary for administrator.................................................................................28
Table 4-12 Data dictionary for system controller..........................................................................28
Table 4-13 Data dictionary for staff members...............................................................................28
Table 5-1 Access control and security...........................................................................................46
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY VIII

LIST OF FIGURES
Figure 1-1 Iterative model diagram..................................................................................................6
Figure 4-1 System use case diagram..............................................................................................19
Figure 4-2 Class diagram...............................................................................................................27
Figure 4-3 Sequence diagram for login..........................................................................................29
Figure 4-4 Sequence diagram for send message............................................................................30
Figure 4-5 Sequence diagram for face detection............................................................................31
Figure 4-6 Sequence diagram for face recognition........................................................................32
Figure 4-7 Activity diagram for login............................................................................................33
Figure 4-8 Activity diagram for send message..............................................................................34
Figure 4-9 Activity diagram for face detection..............................................................................35
Figure 4-10 Activity diagram for face recognition........................................................................36
Figure 4-11 State chart diagram for login......................................................................................37
Figure 4-13 Statechart for face detection.......................................................................................37
Figure 5-1 Current system architecture..........................................................................................39
Figure 5-2 Proposed system architecture.......................................................................................40
Figure 5-3 subsystem decomposition diagram...............................................................................42
Figure 5-4 hardware/software mapping diagram...........................................................................43
Figure 5-5 Detailed class diagram..................................................................................................44
Figure 5-6 persistent data management diagram...........................................................................45
Figure 5-7 Package diagram...........................................................................................................47
Figure 5-8 login user interface.......................................................................................................49
Figure 5-9 user interface for recognized face................................................................................50
Figure 5-10 user interface for unknown face.................................................................................50
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY IX

ABBREVIATIONS AND ACRONYMS
Admin: Administrator
BR: Business Rule
CD: Compact Disk
CPU: Central Processing Unit
HD: High Definition
ICT: Information Communication Technology
ID: Identification
LBPH: Local Binary Pattern Histogram
MD5: Message-Digest Algorithm
OOAD: Object Oriented Analysis and Design
OpenCV: Open Computer Vision
RAM: Random Access Memory
SIFR: Student Identification using Face Recognition
UML: Unified Modeling Language
WKU: Wolkite University
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY X

ABSTRACT
The current entrance system of the wolkite university is supported by both manual and
computerized system. The computerized part of entrance system is digital identification card
which is implemented in the context of the barcode reader. This system has drawback such as,
does not prohibit someone if he/she uses others student digital identification card, the barcode on
digital identification card is easily broken, blacken and scratched if this happen the barcode
reader does not read the barcode on digital identification card. Another drawback of barcode
reader is does not read the barcode from far.
The general objective of proposed project is to design and develop face recognition system for
student identification in wolkite university entrance to support the work process of wolkite
university entrance security guards. The methodology we used to develop this project is
observation and interview, in observation we gather requirements directly by observing the
workflow and perform activity of the existing system without interference of third person and we
interview student union, student and ICT application developer to gathering requirements. After
we identify the problem of existing system, we proposed and design the new and more automated
system which is called student identification using face recognition which avoid the current
problem of entrance system.
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY XI

CHAPTER ONE
1. INTRODUCTION
Face recognition is an important project and research topic in image processing field of study
because of its application in different environments and disciplines like the field of computing,
psychology, and neurology for a different purpose. On the other hand, face recognition plays its
own role in the field of security on different levels from identification to authentication for
systems. Face recognition in the field of security applies different techniques for analyzing and
processing a face image. Here, in this project, an analytical technique for face recognition is used
for extracting feature components of a face for face identification.
computerized system. The manual-based is provided for student until they obtain digital
identification card and the computerized part of entrance system is digital identification card
which is implemented in the context of the barcode reader. The digital identification card has
barcode which contain the information of student on it. This barcode reader has drawbacks. Such
as, the system does not prohibit if someone uses another student’s identification card, if barcode
becomes broken, blacken and scratched the barcode reader cannot read the barcode.
We motivate to develop automated system which is called student identification using face
recognition for wolkite university and to give a solution for the problem of existing system to
enhance security. This system is a technology capable of identifying or verifying a person based
on their facial characteristics. To identify the students the system process through preprocessing
and post preprocessing, in processing the face of students is detected by applying detection
algorithm which called haar cascade classifier OpenCV (open computer vision) library using
camera and the detected face is captured.
In postprocessing the captured face extracted using LBPH (local binary pattern histogram)
algorithm and match the extracted face with store in dataset finally identify and display the
results. It focusses on interest part of faces such as eye, nose, mouth, forehead. In general, the
system identifies the student by comparing selected facial features within is stored in database.
We can this use system in a large organization such as a university, college, and company.
STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY 1

1.1. Background of the Organization
Wolkite University (WKU) is one of the third-generation higher institutions that has been founded
in 2012 and started with 600 students. the university is located in the southern Nation
Nationalities Regional State, in Guraghe zone and 158km from Addis Ababa.it is established for
the purpose of providing and promoting higher education learning, research and outreach
programs in the country to ensure the realization of the national vision of reaching the level of
middle-income countries by 2020. During that time student identification card was manual (paper-
based) started in 2004 E.C until 2009 E.C second semester. After 2009 second semester this
paper-based identification card is replaced by digital identification.
The digital student identification is computerized and its better secured than the paper-based, but
it has some drawbacks. such as the id may be lost, broken, the barcode reader may scratch due to
age or lack of care, so when all this are happening students are obliged to get new identification
card this situation can cause economic extravagance for both students and university the other
drawback of the existing system is another person can enter in to university by the other
identification card. Because of this, we will initiate to develop another system that fixes those
problems which are called students identification using face recognition. This system is work by
capturing the image of students and verify that image if it is in the database after it verifies if it
exists display student information and if it is not displayed an alert.
1.2. Statement of the Problem

computerized system. The computerized part of entrance system is digital identification card
which is implemented in the context of the barcode reader. The barcode reader read the
information of students from digital identification card with the help of barcode on it. The barcode
reader has drawbacks such as it does not prohibit if someone uses the digital identification card of
another student this cause students to perform crimes by using another student identification card.
And another drawback of this system is if barcode becomes broken, blacken and scratched the
barcode reader cannot read the digital identification card this obligated student to get for
replacement. This cause unwanted expenditure for both student and university. The technical
problem of barcode reader does not read digital identification card from far distance unless near to
the barcode reader.

1.3. Objective of the project
1.3.1. General Objective
The general objective of this project is to design and develop face recognition system for student
and staff member identification in wolkite university entrance to support the work process of
wolkite university entrance security guards.
1.3.2. Specific Objectives
In order to achieve the general objectives, we have the following specific objectives.
 Observation and analysis of workflow on wolkite university entrance.
 Analysis of existing system operation and procedure.
 Design component of face recognition system and database.
 Test and evaluate the face recognition system.
 Demonstrate the designed face recognition system.
1.4. Feasibility Analysis of the project

The proposed system is technical, operationally and economically feasible as we have been done
the feasibility analysis and the details has been discussed as follow.
1.4.1. Technical Feasibility

This project will be developed by using current existing technology such as hardware, software
compatibility, and programming language. When we say hardware compatible it means this
system can be implement by using easily available hardware such as camera, screen board, flash.
When we say software, compatible there is available software tools used for implementation such
as PyCharm, visual paradigm, Microsoft Word-2016, and PowerPoint and since we have
knowledge of Python programming language, we prefer python programming language because
its simplicity readability, compatibility, open source library and we are familiar with this
programming language. So, the system is technically feasible and can be achieved easily from the
perspective of technical feasibility.
1.4.2. Operational Feasibility

The designed system will provide all the services and tasks that the manual system provides.
There will not be contradictory operation in the proposed system with gathered requirement.
1.4.3. Economical Feasibility

This system can be implemented with proposed budget and time. All development software tools
are free to download and computers which used to develop this project are available in the
laboratory for free at any time. There is tangible and intangible economic feasibility:

Tangible benefit: - This is the benefit that can be expressed in terms of money. So, the proposed
system will provide more benefit than expected cost.
Intangible benefit: - This benefit cannot be expressed in terms of money. The intangible benefit
that the system will give is listed as following: -
 security
 Reliable and easily manageable
So, the proposed system is economically feasible.
1.5. Scope and Limitation of the Project

1.5.1. Scope of the project
The scope of this project is identification of students and staff members using face recognition at
the entrance point of wolkite university.
1.5.2. Limitation of the project

 This system can’t differentiate identical twins.
 If a person wears a cap or a hat and damage happen on the face and cause change, the
system precision/matching efficiency will be decreased.
 This system will not recognize if the person face is mask.
1.6. Significance of the Project

 Wolkite university
After student identification using Face recognition system is deployed the university get benefit
such as greater accuracy for identify students, more reliability and support the work of guard by
enhancing security of university.
 Student and staff member
After student identification using Face recognition system is deployed the students save time
their time when they enter from outside.
 Developer
When developing the system developer can get knowledge, introduce themselves and maximize
their ability to develop the system.

1.7. Methodology of the Project
1.7.1. Data Collection Tools/Techniques
 Interview
We gather requirements for this project from the student union, students and ICT application
developer about the existing system, how it works and how activity flow, then we identify the
problem with existing system.
 observation
We gather requirements directly by observing how activity flow and what operation performed in
entrance. Through observation, we can obtain information about how the existing system is work
and we identify the problem of the existing system.
1.7.2. System Analysis and Design
To analyses the requirement, we use Object-oriented analysis and design which helps us
analyzing and designing a system, by applying object-oriented programming, as well as using
visual modeling throughout the development life cycles to faster better.
Developing in OOAD will give many advantages which help us:
 We can inherit the properties of the class that are defined in the superclass.
 We can reuse methods for avoiding redundancy.
 The data and functions are encapsulated in the objects that help us for easily debugging
purpose.
 It enables us to comprehensively model a system before we develop it.
 Modification of the object implementation is easy because objects are loosely coupled.
 Understanding the structure is easy because object-oriented modeling represents real-
world entities
1.7.3. System Development Model
We use iterative model for system development, we prefer iterative process because it starts with
a simple implementation of a small set of the software requirements and iteratively enhances the
evolving versions until the complete system is implemented and ready to be deployed.
We perform the following activities such as:
 In the planning phase, we plan how to achieve this project by dividing our activities on
time and how to perform in our group.

 In requirement gather phase, we gather the requirement by using a different methodology
in order to identify the problem of the existing system and how we solve this problem in
this system.
 In the requirement analysis phase, we analyze the gathered requirement.
 In the design phase, we design how the proposed system is divided into the different
component and how the module interacts with each other.
 In the implementation phase, we implement the designed phase.
 In the testing phase, in this phase, we examine the status of the system and validate
whether it achieves the suggested requirement.
 In the deployment phase, finally, in this phase, we deploy the implemented system.
Requirements
Planning
Design
Initialization
Implementation
Evaluation Test
Deployment
Figure 1- 1 Iterative model diagram

1.7.4. Testing methodology
Unit testing
While using unit testing is done at the source or code level for language-specific programming
errors such as bad syntax, logic errors, or to test particular functions or code modules. The unit
test cases shall be designed to test the validity of the program’s correctness.
In this level of the testing process, the face recognition developers test the different sub
procedures and functions.
Sample Tests
1. Check whether the return type of the functions is correct.

2. Check how the subprocedures or functions are called correctly.
3. Check if the correct output is produced for different inputs.
Integration testing
In this level of testing, we have examined how the different procedures work together to achieve
the goal of the subsystem. The type of integration testing that we have follow bottom up. So, we
integrate each component from single function to the main function incrementally.
Sample Tests
1. Check the interaction between individual functionality which performs the specific tasks.
2. Evaluate the functionality of the subsystem after combination all individual functionality.
3. Identify the Independence of each subsystem with another subsystem.
System testing
In this level of testing process, we have examined how the whole subsystems of face recognition
work together to achieve the desired goal (user’s requirements of the system). The goals of system
testing are to detect faults that can only be exposed by testing the entire integrated system or some
major part of it. Generally, under this testing is mainly concerned with areas such as performance,
security, validation, load/stress, and configuration sensitivity of face recognition. But we will
more focus only on function validation and performance.
Sample Tests
1. Evaluate the functionality of the subsystem after a combination of individual subsystem

whether it works correctly or not.

2. Check the coherence and coupling of each subsystem.
3. Check the overall functionality of face recognition that achieves the user’s requirement.
1.7.5. Development Tools and Technologies

1.7.5.1. Frontend Technologies
The user interface is developed using python integrated development environment since it easily
designing the front end and connected into database realizing rapid application development with
constraints on the hand.
1.7.5.2. Backend Technologies
Python, Apache software server used in developing and managing at the back-end. MySQL
software of the database system will be used in developing and managing the back end of the
system and we can use currently existing database which manage information of student that
stored during registration.
1.7.5.3. Documentation and Development Tools
Software tools: are software which installed on a computer for a different purpose from
documentation up to the implementation. We describe the software tools we use in the table
below:
Table 1-1 Software tools
Software tools Description
Python The language we use for implementation.
Windows operating system Will be used for the system since it is readily available in
laboratories.
Microsoft Word 2016 For documenting the corresponding deliverables associated

with the project.
Visual paradigm For designing unified modeling language (UML)diagrams.
Adobe Photoshop For design user interface.
PyCharm, spyder3 An editor for code.

Hardware tools: describe under the following table
Table 1-2 Hardware tools
Hardware tools Description

Computer (desktop or laptop) For documentation and implementation.
CD or flash disk For backup and storage.
Papers For take note.
Pen To write a requirement.
1.7.5.4. Deployment Environments

Deployment environment, for demonstration we will use PC(personal computer) and for
implementation, we will deploy on desktop and it required additional hardware which is camera to
perform its functionality.
1.8. Document Organization

Chapter one defines and describes concepts with regard to the introduction of the chapter that
discusses problems in the existing system. Chapter two describe the existing system. Chapter
three is about an overview of a proposed system which includes functional and non-functional
requirements. Chapter four consists of a flow of events which is the scenario, use case model with
its description of the major use cases. Chapter five deals with system design. Which includes the
overview of the system, design consideration, design goal, design tradeoffs, the architecture of the
system, subsystem decomposition, persistent data management, and class interface.

CHAPTER TWO
2. DESCRIPTION OF THE EXISTING SYSTEM

2.1. Introduction of the Existing System
The current entrance system of wolkite university is digital identification card and it is a web-
based system which is used to identify students based on a barcode in digital identification card.
This system supported by both manual and computer-based. The computerized part of entrance
system is digital identification card which is implemented in the context of the barcode reader.
The digital identification card has a barcode which contain information of student on it. The basic
components of this system are barcode reader, client(computer) and database. In barcode reader
component, the barcode reader read student information from barcode which is on digital
identification card and send information for client. Then client receive information from a barcode
reader as input and search the information from a database with the help of local area network
whether it exist or not. Finally, the information retrieve from a database is display in client side. If
the displayed student information is invalid the system controller prohibit to enter.
2.2. Users of Existing System

Students
Students are the user of the existing system who attend education in the university. The
responsibilities of students are described as the following:
 Keep the identification card from damage, lost and broken.

 If the identification is damage, lost and broken ask for a replacement.
 When student is in university, they should have to be with their digital identification
card.
 When students complete their education, they have to return digital identification card
for university.
 Giving their digital identification card for another student is forbidden by rule.

System administrator
System administrator is user of existing system who is responsible for managing student
information and who perform following activity:
 Register student information.

 Update student information.
 Search student information.
 Manage the database
 Deactivate student information
Campus police
Campus police is the user of the existing system who performs the following activity:
 The campus police Order students who have digital identification card to read their
identification card by system to check its validity.
 Check student’s identification card when they enter from outside.
System controller
System controller is the user of the existing system who perform the following activity:
check whether the system read a digital identification card or not.

check whether the system display valid information or not.
2.3. Major Functions of the Existing System

The major functionality of the existing system described as the following:
 Barcode reader read student identification card.

 Search student information from database.
 Display student information.
 Display invalid information.

2.4. Forms and Other Documents of the Existing Systems
Here there are sample scan image of reports, forms and other related documents that used in the
existing system. Appendix section have the following forms.
I. Sample of student identification
 A digital identification card used for student identification.
II. Check student page
 A page that student information display on it.
2.5. Drawbacks of the Existing System

The current entrance system of the Wolkite university is supported by both manual and
computerized system. The computerized part of entry system is digital identification card which is
implemented in the context of the barcode reader. The existing system has drawbacks such as it
does not prohibit if someone uses the digital identification card of another student this cause
students to perform crimes by using another student identification card. And another drawback of
this system is if barcode becomes broken, blacken and scratched the barcode reader cannot read
the digital identification card this obligated student to get for replacement. This cause unwanted
expenditure for both student and university.
2.6. Business Rules of the Existing System

The main business rules or principles of the existing system are: -
Table 2-3 Business rule 1
Items Details
Name Digital identification card
Id BR1
Description  The student must have valid digital identification card.
 Only one identification card allows for student.
 Keep the identification card from damage, lost and broken.
 If the identification is damage, lost and broken ask for a replacement.

Items Details
Name Add student information
Id BR2
Descriptio System administrators have responsible for import student information
n from currently existing database
Items Details
Name Deactivate student information
Id BR3
Description System administrator have a responsible for deactivate student
information when student complete education and leave from university
Items Details
Name Create account
Id BR4
Description System administrator has responsibility for creating account for system
controller.
Items Details
Name Update student information
Id BR5
Description System administrator has responsibility for updating student information
when its required
Items Details
Name Activate student information
Id BR6
Descriptio System administrator has responsibility for activate student information
n when its required

CHAPTER THREE
3. PROPOSED SYSTEM
Face recognition is an important project and research topic because of its application in different
environments and disciplines like the field of computing, psychology, and neurology for a
different purpose. On the other hand, face recognition plays its own role in the field of security on
different levels from identification to authentication for systems. Face recognition in the field of
security applies different techniques for analyzing and processing a face image. Here, in this
project, an analytical technique for face recognition is used for extracting feature components of a
face for face identification.
The system we are going to develop is desktop application which is called student identification
using face recognition for Wolkite university. Face recognition is the process of identifying a
student based on their facial characteristics. To identify the students the system process through
preprocessing and postprocessing. In preprocessing system detect face, in face detection the
system find face (location and size) in an image, the face is detected by applying detection
algorithm which called haar cascade classifier OpenCV (Open Computer Vision) library using
camera and the system capture the detected face.
In postprocessing, the captured face is extracted using LBPH (Local Binary Pattern Histogram)
algorithm and match the extracted face with store in dataset and identify the student and staff
member, finally display the information of recognized face from database. This system linked
within a current exist database which manage information of student and we develop document
database where the captured image is stored.
3.1. Functional Requirements

fdkhg
 Face detection
Face detection has the objective of finding the faces (location and size) in an image and extract
them to be used by the face recognition algorithm. This system uses haar cascades classifiers
OpenCV (open computer vision) library for face detection. This algorithm used for finding the
location of the human faces in a frame or image and gives the coordinates of x, y, w, h which
makes a rectangle box in the picture to show the location of the face or we can say that to show the
region of interest in the image. After this, it can make a rectangle box in the area of interest where
it detects the face.

 Face recognition
This system uses Local Binary Pattern Histogram (LBPH) algorithm for face recognition. It is a
simple and very efficient texture operator which labels the pixels of an image by thresholding the
neighborhood of each pixel and considers the result as a binary number.
asdfghj
 Update information
The system allows system administrator to update information of users when it required.
 Manages user account
The system allows system administrator to manage user account such as create account.
 Record threat
The system allows system controller to record threat
 Guest control
The system will provide a guest control and tracking service while the guest enter form outside
into university.
 Tracking service
The system will record the number of users exit and entering at entrance point.
3.2. Nonfunctional Requirements

3.2.1. User Interface and Human Factors
The user interface of this system is easy and not difficult because the feature of each interface is
clear and readable interface to use.
3.2.2. Hardware Consideration

The university has computers having typical storage capacity and processing speed. The system
we are going to develop is platform independent and it will interact with other hardware.
The hardware that required after develop the system is basically the following: -

Number ITEM Specification
1 CPU 64-bit Core i3(TM) 3.30 GHz
2 RAM Minimum of 2GB
3 Hard disk Minimum 22GB and others.

4 Camera Four cameras (Pixel resolution is 1280 x 1024
and HD quality camera).
3.2.3. Security Issues

Security requirement are important factors in this system as classified data/information will be
stored in the database. User validation will be done during login to ensure that the user is valid
and that the user only has access to his/her permitted information and we can add the security
capabilities of MD5 encryption and decryption.
3.2.4. Performance Consideration

The performance of this system is measured in terms of load time and response time. So, it is fast
to capture face and displays the result to achieve this we will use the best algorithm and the
university has fast network (local area network) which helps to access the information of user
from a database.
Load time: this system loads the information in a second.
Response time: This system give response to the user according to the delivery of message and
receive notification reaches in a second. The system shall support multiple users at a time depend
on the number of camera and it works very well with short response time.
3.2.5. Error Handling and Validation
The system will check user inputs to the system to handle error. It handles and show error by
showing the message” invalid input” when the user enters invalid input.
3.2.6. Quality Issues
The system qualities issues also are important non-functionary requirement. The system should
fast and efficient service to all users. Adaptability, availability, and reliability are the key issues of
this requirement. We use suitable software and hardware to develop system, will able to achieve
this requirement.

3.2.7. Backup and Recovery
The proposed system can be damaged or fail if there is virus attack and continuous power
disconnection from the source station and the data can be lost at that time. The system should be
holding a backup of the data because database backup technology is available.
3.2.8. Physical Environment

The system deployed in desktop application. To protect the server and camera from overheat and
other natural disasters like rain, high wind pressure we should have to keep away from and keep
in ventilated condition for better protection.
3.2.9. Resource Issues

 Server
The minimum hardware requirement for database is-
 CPU: 32-bit or 64 bits Core i3(TM) 3.30 GHz.
 RAM: 2GB (or higher is recommended)
 Client
The client is required for accessing the service provided by the server.
 Camera
The camera is required for capturing student face and receive face image for client.
The camera might require to include:
 High-resolution camera.
 HD quality.
 Screen board
Screen board can be used for display information of student on it.
3.2.10. Documentation
The documentation is including proposal, software requirement specification, testing
documentation and so on. Since the system we develop is a desktop application it needs basic
computer skill. However, the system might be modified to include additional features and it can
be maintained for the future. Therefore, the maintainers will provide with some technical
documentation from the organization for analysis, design, and implementation

CHAPTER FOUR
4. SYSTEM ANALYSIS
4.1. System Model
To produce a correct, complete and consistent model of the system we construct the analysis
model which focuses on structuring and formalizing the requirements of the system. Analysis
model of this system contains three models: functional, object and dynamic models. The
functional model of this system described by use case diagrams. The class diagrams of this system
describe the object model. The dynamic model of this system can also describe in terms of
sequence, state chart and activity diagrams.
4.1.1. Use Case Model

Use case
The following use cases have been identified from the system specification
 Face detection
 Upload image
 Capture face
 Training data
 Display alert
 Control camera
 Login
 Logout
 Create account

 Send message
 View message
 Block student information
 Add student information
 Enter
 Search student information
Actors
The identified actors that will be participating in the system are:
 Staff member
 Student
 Campus police
 System controller
 System administrator

4.1.1.1. Use Case Diagram
Figure 4-2 System use case diagram
4.1.1.2. Use Case Description

Table 4-9 Use case description for enter
Use case name Enter
Actor Student and staff member

Description: Student and staff member want enter from outside
Precondition No precondition
Post-condition: System detect the student face

Normal Follow Actor action System response
Step 1: student and Step 2: system detect the face
staff member enter Step 3: system recognize detected face
from outside Step 4: system display information of
recognized face
Table 4-10 Use case description for login
Use case Login

name
Actor System administrator, controller
Description: Allow login into the system.
Precondition The system administrator or controller should have an account in the

system.
Post- The administrator or controller is logged in the system and provided with
condition: privileges for actions according to their roles
Normal Actor action System response
Follow Step 1: opens the window. Step 3: The system display Login
Step 2: Select Login link. form displayed
Step4: user enter username and Step 6: The system validates
password. entered data
Step 5: user clicks on Login button Step7: system display Appropriate
page
Alternative Step 4: Invalid user name and password
1. System display invalid message
2. Step 3 repeated
Table 4-11 Use case description for create account
Use case name Create account
Actor System administrator
Description In this use case Administrator, can creates accounts for system
controller.

Precondition Must be administrator of a system
Post-condition Administrator logged to system
Normal follow Actor action System response

Step 1. Administrator click on Step 2. The system displays
create account link create account page
Step 3. Administrator entered Step 4. system validate entered
required information. data
Step 5: if it is valid information
recorded to database
Step 6: the system displays
successful message
Alternative Step 3. Invalid information
1. System display invalid message
2. Step 2 repeated
Table 4-12 Use case description for face detection
Use case name Face detection
Description System wants to detect face of student

Post-condition System detect a face student

Step 1. Student and staff member Step 2. System load algorithm
enter from outside to detect a face
Step 3. System draw rectangle
box in a face
Alternative Step 2. No face has been detected
1. Step 2 repeated
Table 4-13 Use case description for face recognition
Use case name Face recognition
Description System wants to recognize student and staff member face

Precondition face must be detected
Post-condition System display information of recognized face

Step 1. Student and Step 2. System detected student face
staff member enter Step 3. System compare the detected face
from outside with stored in database.
Step 4. System identify compared face
Step 5. System display information of
identified student face
Alternative Step 4. If student face is not identified.
1. the system display alert
Table 4-14 Use case description for view alert
Use case name View alert
Actor System controller and guard
Description System display the information of recognized student face

Precondition System must recognize the student face
Post-condition System display information of recognized face

Step 1. Student enter from Step 2. System recognize student
outside face
Step 4. System controller or Step 3. System display information
guard can view displayed of recognized student face
information or alert
Table 4-15 Use case description view message
Use case name View message

Description System administrator or control view message
Precondition System administrator or controller must have account
Post-condition System administrator or controller view a message

Step 1. System administrator or Step 2. System display
controller select view message from received message
message page
Table 4-16 Use case description for send message
Use case name Send message
Description System administrator or controller want to send message

Precondition System administrator or controller must have account
Post-condition System send delivery notification for affirmation if the message sent
successful
Step 1. System administrator or Step 2. System display send
controller select send message message form
from message page Step 4. System validate the filled
Step 3. System administrator or information
controller write message and fill Step 6. System display delivery
the provided text field notification for affirmation if the
Step 5. System administrator or message sent or not
controller click on send button
Alternative Step 2. Invalid information

1. system display invalid message
2. step 2 repeated

4.1.1.3. Use case Scenario
Scenario name: Login.
Participant actors: Solomon.
Normal flow of events:
 Mr. Solomon should have account to login.
 The System display login page.
 Mr. Solomon insert username and password then click on login button.
 The System validate input value.
 Mr. Solomon access the system which provided for him.
 End-use case.
What if it goes wrong?
 If the user can’t insert username or password and if username or password is incorrect
the system display notification such as “the field is empty or you entered wrong
username or password”
Scenario name: send message.
Participant actors: Kebede.
 Kebede should have account to send message.
 Kebede select send message from message page.
 The System display send message page.
 Kebede write a required message then click on send message button.
 The system display notification for message is send or not.
 End-use case.
What if the text area is empty or message is not written?
 If System administrator or controller can send empty text the system display text field
is empty.
Scenario name: Face Detection
Participant actor: Abebe

 Abebe enter from outside.
 Abebe stand in front of camera.
 The camera captures the face of Abebe.

 The system load algorithm for face detection.
 The system draws rectangular square on detected face.
 End-use case.
What if the system does not detect the face?

 If the face is not detected the system return into previous steps.
Scenario name: Face Recognition
Participant actor: Chala
Initial assumption: The system must detect the face of Chala.

 Chala enter from outside.
 The system detected face.
 The system compares the detected face with stored in database.
 The system identifies the detected face.
 The system displays the information of identified face.
 End-use case.
What if the system does not recognize the face?
 The system displays alert.
Scenario name: View Message
Participant actor: Bekele

 Bekele should have account to view message.
 Bekele select view message from message page.
 System display received message.
 Bekele view received message.

4.2. Object Model
4.2.1. Class Diagram
UserAccount
Recognition userName
receiveStream password
imageId login()
detectFace()
capture()
compare()
displayAlert()
User
firstName
lastName
Name
recognize
* *
*
recognize
1
1 1
Student SystemAdmin
SystemController
Image viewAlert() addInformation()
Id updateImage() importInformation()
displayValidatePass() searchStudentInformation() blockInformation()
Name
staffMember
Message
staffMemeber_id TrainingData
role messageId
sender train()
receiver
date
sendMessage()
viewMessage()
Figure 4-3 Class diagram
4.2.2. Data Dictionary

Table 4-17 Data dictionary for student
Number Column name Datatype Constraint

1 IdNumber String (12) Primary_key
2 FirstName String (15) Not null
3 MiddleName String(12)
4 LastName String (15) Not null
5 College String (20) Not null
6 Departement String (20) Not null
7 Status String (12) Not null

8 RandomId Int (10) Unique
Table 4-18 Data dictionary for message
Numbe Column name Datatype Constraint

r
1 Title String (20) Not null
2 Sender String (20) Not null
3 Receiver String (20) Not Null
4 Date Date (12) Not null
5 Message String (200) Not null
Table 4-19 Data dictionary for Login
Number Column name Data type Constraint

1 Role String Not null
(12)
2 firstName String Not null
(20)
3 lastName String Not null
(20)
4 UserName String Not Null
(17)
5 Password String Primary_key
(12)
Table 4-12 Data dictionary for staff members

1 Id_number Int (12) Primary_key
3 MiddleName String (15) Not null
5 Role String (14) Not null

6 RandomId Int (18) Not null
Table 4-20 Data dictionary for Guest

1 Id_number Int (12) Primary_key
5 Role String (14) Not null
6 RandomId Int (18) Not null
4.3. Dynamic Model

4.3.1. Sequence Diagram
A sequence diagram of use case can describe as following

Figure 4-4 Sequence diagram for login

Figure 4-5 Sequence diagram for send message

Figure 4-6 Sequence diagram for face detection

Figure 4-7 Sequence diagram for face recognition

4.3.2. Activity Diagram
Figure 4-8 Activity diagram for login

Figure 4-9 Activity diagram for send message

Figure 4-10 Activity diagram for face detection

Figure 4-11 Activity diagram for face recognition

4.3.3. State Chart Diagram
Figure 4-12 State chart diagram for login
Figure 4-13 State chart for face detection

CHAPTER FIVE
5. SYSTEM DESIGN
5.1. Design Goals
5.1.1. Performance
System will have good performance as much as possible this will be attained via easily loadable
information and fast response time in searching, updating and viewing information because we
will use good algorithm and minimize a line of code to perform specific function.
Load time: this system will be loading the information in a second.
Throughput: depends on number of cameras the system performs many operations at given time.
Response time: This system give response to the user according to the delivery of message and
notification reaches in a second. The system shall support multiple users at a time depend on the
number of camera and it works very well with short response time.
5.1.2. Dependability
This system should achieve the following dependability characteristics in order to resist crash and
be available and reliable.
 Availability: -the system is available if there is a network (local area network).

 Security: this system is secured by prevent unauthorized users to access the database
system.
 Reliability: the system is reliable by providing the correct information and give response
correctly and accurately for query from authorized user.
5.1.3. Maintenance
The system should be maintainable if there is failure in system or when the system need
modification that means we will develop this system by dividing the system into different module
which is loosely coupled and high cohesive. To be maintainable the system should meet the
following maintenance criteria:
 Extensibility: - If it is needed to add new functionality to the system, this must be

achieved by only making a separate page and integrate this page with the existing system.
 Modifiability: - If the system needs some functionality to be modified, the modification is
done to that function or page without affecting the overall system organization.

5.1.4. End-user
The user interfaces of the system should prevent users from issuing commands in the wrong
order. That means whenever user of system wants to login unnecessary command to the user
interface and progress the process toward the next function the user interface it prevents from
performing action.
5.2. Current System Architecture

Existing system is consisting of 3-tier architecture namely presentation layer, business logic layer,
and data layer. The presentation layer is client layer and topmost layer of the application. The
main functionality of this layer is to communicate with the application layer. This layer passes the
information which given in terms of keyboard action and mouse click to the application layer.
Example when user want to login into the system first see two text box and login button to enter
user name and password and click on login.
Business logic layer it is application layer which interacts with data layer and sends information
retrieved from database toward to presentation layer.it act as the mediator between presentation
layer and data layer. From above example once, the user clicks on login button application layer
interact with the database and send information towards to presentation layer. The third one is
data layer which used to store data entered by the user. In general client of our system use browser
to access the system using the internet.in this case when the user enters input and takes certain
action application server process client request to interacting with the database server.
send information
Request
Response
LAN
Client
Database
Application server server
Figure 5-14 Current system architecture

5.3. Proposed System Architecture
This proposed system is consisting of 3-tier architecture namely presentation layer, business logic
layer, and data layer. The presentation layer is client layer and topmost layer of the application.
This is the layer we see when we use this system. It is the interface to our system which takes
information from the user. The main functionality of this layer is to communicate with the
application layer. This layer passes the information which given in terms of keyboard action and
mouse click to the application layer. Example when user want to login into the system first see
two text box and login button to enter user name and password and click on login.
Business logic layer it is application layer which interacts with data layer and sends information
retrieved from database toward to presentation layer.it act as the mediator between presentation
layer and data layer. From above example once, the user clicks on login button application layer
interact with the database and send information towards to presentation layer. The third one is
data layer which used to store data entered by the user. In general client of our system use browser
to access the system using the internet.in this case when the user enters input and takes certain
action application server process client request to interacting with the database server.
Web camera
capture image
Request
Response
LAN
Client
display information
Database
Application server server
Screen
Figure 5-15 Proposed system architecture

5.3.1. Subsystem Decomposition and Description
Subsystem decompositions help to reduce the complexity of the system. The subsystems that we
take the classes that this system contains and the operation performed in the class. The following
are subsystems
 System Admin subsystem: responsible for handling action that administrator
performs such as:
 Create account
 View information
 Send message
 View message
 Login
 Training data
 Add student information
 Block student information
 Recognition subsystem- responsible for handling action that System perform such as:
 Face detection
 Face capture
 Face recognition
 Display validate pass
 System Controller subsystem: - responsible for handling action that System Controller
perform such as:
 Login
 View alert
 View message
 Send message
 Update images
 Search student information

Student Identification using Face Recognition
System Admin
subsystem
System
Controller
block subsystem
View Training
student
message data
information
search
View alert
student
information
Add student Send
information message
Send View
message message
Connection
Control
subsystem Update
camera
image
Database
Recognition
subsystem
Display
alert
Face detection
capture Face
face recognition
Figure 5-16 subsystem decomposition diagram
5.3.2. Hardware/Software Mapping

One of the major tasks in system design deals with hardware/software mapping which deals with
which components would be part in which hardware and so on.
• User interface and processing management will be deployed on the client machine.
• Student identification using face recognition will present the Graphical User Interface
(GUI) which is used for display user information.
• Student identification using face recognition use existing database which deployed on
the server.
• The data collection module deployed on any computer.

<<Device>> <<Device>>
<<Device>>
:Application Server :Database Server
:Client
Authentication
Face
detection
qu
er
y
install driver
Web Camera
receive
image
Face
recognition query Database
query
Send
ery
messaga qu
install driver
infomation
Computer y
display
er
qu
ery uery
View
q
message
qu
View alert
Update
image
Screen Display
validate pass
Figure 5-17 hardware/software mapping diagram
5.3.3. Detailed Class Diagram

UserAccount
Recognition +userName:String
-receiveStream:Image<byte>> +password:String
+imageId:int 1
+login():void
1
+detectFace():blob
+capture():blob
+compare():String have
+displayAlert():void have
User
1 *
+firstName:String
+lastName:String
view
Name
recognize
* *
*
recognize
1 1
1 1 1 1 1
Student SystemAdmin
SystemController
+Image:blob
+addInformation():void
+Id:int +viewAlert():void +importInformation():void
+displayValidatePass +updateImage():void +blockInformation():void
(firstName:String,Id:int):void +searchStudentInformation
1
():void *
1
Name 1
* * update 1 view
add
view
*
staffMember 1
Message *
+staffMemeber_id:int TrainingData
+role:String +messageId:int
+sender:String +train()
+receiver:string
+date:date
+sendMessage():void
+viewMessage():void
Figure 5-18 Detailed class diagram
5.3.4. Persistent Data Management

Student
+firstName:string SystemController SystemController
Student<<Table>>
+lastName:String +firstName:string <<Table>>
+image:blob +lastName:String
firstName firstName
+studentId:int +userName:String
lastName lastName
image +password:String
+displayValidateP userName
ass studentId<<primary key>> +viewAlert():void password<<primary key>>
(firstName:String, +updateImage():void
studentId:int):void +searchInformation():void
+login():void
SystemAdmin Message
SystemAdmin<<Table>>
+firstName:string +messageId:int Message<<Table>>
+lastName:String firstName +sender:String
+userName +receiver:String messageId<<primary key>>
lastName
password:String +date:date sender
userName
receiver
password<<primary key>>
date
+addStudentInformation():void sendMessage():void
+importStudentInformation():void viewMessaage:void
+blockStudentInformation():void
+login():void
StaffMember
+firstName:string StaffMember<<Table>>
+lastName:String
+image:blob firstName
+staffmemberId:int lastName
+role:String image
+displayValidatePass staffMemberId<<primary
(firstName:String,staff key>>
memberId:int):void role
Figure 5-19 persistent data management diagram

5.3.5. Access Control and Security
Table 5-21 Access control and security
Operation
Actor Ente Update Send View Add Block Import

r or image message message student student student
leave information information information
Student  - - - - - -
Guard - - - - - - -
System -    - - -
controller
System - -     
administrator

5.4. Packages
Student Identification using face recognition
System Controller
View update
View alert
System message image
Adminstrator
block control Send Search

Send
student camera message student
message
information information
Training
Add student
data
information
Recognition
View
message
Display alert face

recognition
database
face
student capture face
detection
Figure 5-20 Package diagram

5.5. Algorithm Design
 Login
 Window displayed.
 User click on login link
 System display login page.
 User enter user name and password.
 If user name and password is correct, then
 If user is admin, then system display admin page.
 Else if user is system controller, then system display system controller page.
 Else user username and password is not correct, then system display error message
and redisplay login page.
 Detection
• Student enter or leave the get.
• System load algorithm for detection
 System draw rectangle box in detected face
 If student face is detected, then system capture detected face in screen
 Else system searches a face to detect.
 Recognition
 face can be detected
 system compare detected face with stored in database
 System identify compared face.
 If match face is found, the system displays information of student
 Else the system display alert

5.6. User Interface Design
Figure 5-21 login user interface

Figure 5-22 user interface for recognized face
Figure 5-23 user interface for unknown face

CHAPTER SIX
6. IMPLEMENTATION AND TESTING
6.1. Implementation of the Database
The system uses relational database and document database for storing information. It uses
relation database for storing required information of user (such as student, staff member, guest,
admin and system controller) and document database for storing image of user. We have chosen
SQLite3 database because SQLite3 database is fastest database with advanced performance and
more capabilities to simplify operation of data base in a short time.
Table 6-1 Table for student

1 IdNumber String (12) Primary_key
5 College String (30) Not null
6 Departement String (30) Not null
7 Status String (12) Not null
8 RandomId Int (10) Unique
Table 6-2 Table for message
Numbe Column name Datatype Constraint

r
1 Title String (20) Not null
2 Sender String (20) Not null
3 Receiver String (20) Not Null
4 Date Date (12) Not null
5 Message String (200) Not null

6.2. Implementation of the Class Diagram
Over all interface documentation in class access modifier
Identifier type Student Identification using Face Recognition for Wolkite

University
Classes + class Admin
-Class Controller
- Class Student
- Class Staff Member
- Class Guest
- Class User Account
- Class Message
- Class Recognition
Methods  CreateAccount ();

 SendMessage ();
 ViewMessage ();
 Register ();
 UpdateImage ();
 AcivateaUserInformation();
 DiactivateUserInformation ();
 StartCamera ();
 PauseCamera ();
 StartRecord ();
 StopRecord ();
 StoreImage ();
 CaptureImage ();
Variables +VarChar FirstName; +VarChar Title;
+VarChar MiddleName; +VarChar Sender;
+VarChar LastName; +VarChar Receiver;
+VarChar IdNumber; +VarChar Message;
+VarChar College; +VarChar reason;
+VarChar Department; +Date Date ;
+VarChar Status;
+VarChar RandomId;
Student class

Class Attributes Data type Visibility
Student class FirstName Varchar Private
MiddleName Varchar Private
LastName Varchar Private
IdNumber Varchar Private
College Varchar private
Department Var char Private
Status Var char Private
RandomId Int Private
Staff Member class

Class Attributes Data type Visibility
StaffMember FirstName Varchar Private
class MiddleName Varchar Private
LastName Varchar Private
IdNumber Varchar Private
Role Varchar private
RandomId Int Private
6.3. Configuration of the Application Server

SQLite is different from other SQL databases because unlike most other SQL databases, SQLite
does not have a separate server process. It reads and writes directly to ordinary disk files.
6.4. Configuration of Application Security

In the configuration of application level security, we do message security which is services
invoked at the interface between an application and queue manage which is connected.
From the security aspect of any system, we should have to take in to account the following
activities. We implement input validations properly such as
 Validation of login system
 Validation of incorrect input
 Validation of un matched data
 Roles must be defined clear

Administrator and System controller of the system have their own account to manage all their
tasks. The administrator is the person who is responsible for register user information, activate
user information, deactivate user information send message, view message, create account and
view information. The System controller is the person who is responsible for controlling camera,
controlling guest, record threat, update user image and checking the user information is correctly
display or not.
6.5. Implementation of User Interface

The user interface of this system does not support command languages but menus and graphical
user interface. We use user model of user interface to represent different feature of end users and
roles playing in the system.
Regarding to the user interface, we have applied the following.
 The user interface that we develop is user adjusted design. It means we have to make our
user interface be attractive to users by developing compatible, well-matched and friendly
user interface
 The user interface that we develop is consistent and dependable
 the user interface is consistent and stable which does not create any confusion for users
easily understandable with clear and steady navigation.
6.6. Testing
6.6.1. Testing Tools and Environment
JetBrains PyCharm Community Edition 2018.3 are used for every module development. By
tracing and correcting bugs and errors our system’s stability is increased. Since our codes are
written in JetBrains PyCharm Community Edition 2018.3 environment it is easy to keep tracking
any mistakes especially in unit testing phase.
6.6.2. Unit Testing

Unit testing is done at the source or code level for language-specific programming errors such as
bad syntax, logic errors, or to test particular functions or code modules. The unit test cases shall
be designed to test the validity of the program’s correctness.
In this level of the testing process, the face recognition developers test the different sub
procedures and functions.
Sample Tests
1. Check whether the return type of the functions is correct.

2. Check how the subprocedures or functions are called correctly.

3. Check if the correct output is produced for different inputs.
Example: -
 Validating entered input in login field.
Test procedure are:
 Check if both are empty space.
 Check if one is empty.

 Check if both are incorrect input is entered in field.

 If both are correct.

6.6.3. Integration Testing
In this level of testing, we have examined how the different procedures work together to achieve
the goal of the subsystem. The type of integration testing that we have follow bottom up. So, we
integrate each component from single function to the main function incrementally.
Sample Tests
1. Check the interaction between individual functionality which performs the specific tasks.
2. Evaluate the functionality of the subsystem after combination all individual functionality.
3. Identify the Independence of each subsystem with another subsystem.
6.6.4. System Testing

In this level of testing process, we have examined how the whole subsystems of face recognition
work together to achieve the desired goal (user’s requirements of the system). The goals of system
testing are to detect faults that can only be exposed by testing the entire integrated system or some
major part of it. Generally, under this testing is mainly concerned with areas such as performance,

security, validation, load/stress, and configuration sensitivity of face recognition. But we will
more focus only on function validation and performance.
Sample Tests
1. Evaluate the functionality of the subsystem after a combination of individual subsystem

whether it works correctly or not.
2. Check the coherence and coupling of each subsystem.
3. Check the overall functionality of face recognition that achieves the user’s requirement.

CHAPTER SEVEN
7. CONCLUSION AND RECOMMENDATION
7.1. Conclusion
Currently Wolkite university is using digital identification in entrance, the system is developed in
web-based application implemented through barcode reader which use to read information from
digital identification using barcode on it. This system has drawback, so we plan to develop new
system which solve the drawbacks of existing system which is called student identification using
face recognition its desktop application, it has high security, reliability and accuracy.
7.2. Recommendation
The proposed system is does identify identical twins, so we recommended for any revision to
solve this problem during modification.

8. REFERENCE
[1]
Bruegge, B. (n.d.). System Design. Aerobate PDF writer 4.0 for Power Macintosh.
[2] Design system using object-oriented design techniques. (2002). Acrobat Distiller 4.0 for
windows.
[3] Face detection using OpenCV and Python. ( 2017).
[4] Ibrahim, Syed. (2018). Automatic Attendance System Using Facial Detection and
Recognition. SudhaNarang, 24372-24376.
[5] Introduction to biometrics. (n.d.). West Virginia : James .
[6] Prado, K. S. ( 2017). Face Recognition: Understanding LBPH Algorithm. Face Recognition:
Understanding LBPH Algorithm.
[7] Prado, K. S. (2017, Nov 08). Face Recognition: Understanding LBPH Algorithm. pp. 1-25.
[8] Schach, S. R. (2011). Object-Oriented and Classical Software Engineering. New York: Hill
Companies. Retrieved from https://medium.com/@smagid_allThings/uml-class-diagrams-
tutorial-step-by-step-520fd83b300b.
[9] wikipedia.org. (n.d.). Retrieved from https://en.wikipedia.org:
https://en.wikipedia.org/wiki/Facial_recognition_system

9. APPENDIX
Appendix A: forms of existing system
I. Check student page
II. Check student page
Appendix B: interview question

Interview question: to gather requirements for the project we prepare the following question for
application developer, student, and student union.
Question 1: - What is the purpose of digital identification card?

Question 2: - Who are the user of existing system?
Question 3: -What are drawbacks of existing system?
Question 4: -What are major function of existing system?
Question 5: - What are the business rule of the existing system?

Citizen Identification and Information Management System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Citizen Identification and Information Management System

Uploaded by

Copyright:

Available Formats

WOLKITE UNIVERSITY

COLLEGE OF COMPUTING AND INFORMATICS

STUDENT IDENTIFICATION USING FACE

PROJECT ADVISOR: MR. ALEMU WOLDIE

Wolkite University, Wolkite, Ethiopia

STUDENT IDENTIFICATION USING FACE

SUBMITTED TO DEPARTMENT OF SOFTWARE ENGINEERING

PROJECT ADVISOR: MR. ALEMU WOLDIE

Wolkite University, Wolkite, Ethiopia

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY I

Full name signature

Gosa Negash ____________________

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY II

------------------------------------------------- ------------------------------ ----------

Advisor Name Signature Date

------------------------------------------------- ------------------------------ ----------

Department Head Name Signature Date

------------------------------------------------- ------------------------------ ----------

Examiner 1 Name Signature Date

------------------------------------------------- ------------------------------ ----------

Examiner 2 Name Signature Date

------------------------------------------------- ------------------------------ ----------

Examiner 3 Name Signature Date

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY III

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY IV

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY V

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY VI

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY VII

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY VIII

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY IX

BR: Business Rule

CD: Compact Disk

CPU: Central Processing Unit

HD: High Definition

ICT: Information Communication Technology

LBPH: Local Binary Pattern Histogram

MD5: Message-Digest Algorithm

OOAD: Object Oriented Analysis and Design

OpenCV: Open Computer Vision

RAM: Random Access Memory

SIFR: Student Identification using Face Recognition

UML: Unified Modeling Language

WKU: Wolkite University

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY X

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY XI

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY 1

1.2. Statement of the Problem

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY 2

1.4. Feasibility Analysis of the project

1.4.1. Technical Feasibility

1.4.2. Operational Feasibility

1.4.3. Economical Feasibility

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY 3

1.5. Scope and Limitation of the Project

1.5.2. Limitation of the project

1.6. Significance of the Project

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY 4

We perform the following activities such as:

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY 5

Figure 1- 1 Iterative model diagram

STUDENT IDENTIFICATION USING FACE RECOGNITION FOR WOLKITE UNIVERSITY 6

1. Check whether the return type of the functions is correct.

1. Evaluate the functionality of the subsystem after a combination of individual subsystem