Non-Functional Requirements:

Non-functional requirements are

set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must be fast and
reliable.
Non-Functional Requirements:
Non-functional requirements are
set of requirements with specific
criteria to judge the systems
operation. These requirements have
been collected based on the
following after meetings with the
client. They cover ease of use to
the client, security, support
availability, operational speed, and
implementation considerations. More
specifically:
 The user will find it very
convenient to take photos.
 The user will inform the
students when taking a photo with
clear instructions on how to
position their faces.
 The system is very secure.
 The system will have a response
time of 10 seconds.
 The system can be easily
installed.
 The system is 100% efficient.
 The system must
be fast and reli
IIMS College
Putalisadak, Kathmandu, Nepal

Name of Course Instructor: __Mr. Rupesh Pradhan_______________________________________

Course Code: ___________ Course Name: Business Case Project

Program Name: B.Sc. Computing_ Semester: 7th Batch: __2018___

Assignment: I Assignment Type (Individual/Group): _Group_

Assignment Title: Facial Recognition Attendance System

Max. Marks: ___ Date of Allotment: 2020-02-07__ Date of Submission: ___2020-02-07___

(Write the individual/group members details below):

Name of the Student ID number Contact Number Email Id Signature

Shekhar Saud 1001849611 9843946205 Sheeekharsaud73@gmail.com

Marshall Shrestha 1001849583 9819260966 Shresthamarshall455@gmail.com
 Krbaduwal02@gmail.com
Khemraj Baduwal 1001849580 9869277313
Binod Poudel

Evaluation: ________________________ Obtained out of ________________________________

Evaluator’s Comment:
_______________________________________________________________________________________________
_______________________________________________________________________________________________

-------------------------------------------
Evaluator’s Signature & Date

Table of Content
s
Introduction.....................................................................................................................................................................1
Purpose.......................................................................................................................................................................1
Intended Audience......................................................................................................................................................1
Project Scope..............................................................................................................................................................1
Overall Description.........................................................................................................................................................2
Product Perspective....................................................................................................................................................2
Definitions:.................................................................................................................................................................2
Timeline......................................................................................................................................................................3
Project Plan.................................................................................................................................................................3
Product Features.........................................................................................................................................................4
User Classes and Characteristics................................................................................................................................4
Benefits.......................................................................................................................................................................4
Tools and technologies...............................................................................................................................................5
Data Model Design Diagrams.........................................................................................................................................6
Use case diagram........................................................................................................................................................6
Sequence diagram......................................................................................................................................................7
Sequence diagram for admin panel...........................................................................................................................7
Class diagram..............................................................................................................................................................8
Activity diagram..........................................................................................................................................................9
Activity diagram for login process............................................................................................................................10
Functional Requirements..............................................................................................................................................11
Adding a New student..............................................................................................................................................11
Use the system to attend to class..............................................................................................................................11
Admin can view a full report....................................................................................................................................11
Students missed classes............................................................................................................................................11
Non-functional Requirements.......................................................................................................................................13
Reports..........................................................................................................................................................................14
Application interface.....................................................................................................................................................14
System flow..............................................................................................................................................................15
Future Direction............................................................................................................................................................15
Conclusion....................................................................................................................................................................16

Introduction
Purpose
Checking the presence of students, staffs and maintaining the attendance is a regular process for
institute at morning and evening. Methods of taking attendance is different in each institute as per their
methods like calling names or checking the name list. Several popular automatic attendance systems
currently in use are RFID, iris, fingerprint etc. However, making queue is essential in these cases thus
requires more time. The task of the proposed system is to capture the face of each student and to store it
in the database for their attendance. The face of the student needs to be captured in such a manner that
all the feature of the student's face needs to be detected, even the seating and the posture of the student
need to be recognized. The software first captures an image of all the authorized persons and stores the
information into database. The system then stores the image by mapping it into a face coordinate
structure. There is no need for the teacher to manually take attendance in the class because the system
records a video and through further processing steps the face is being recognized and the attendance
database is updated. Next time whenever the registered person enters the premises the system
recognizes the person and marks his attendance along with the time. Therefore, the main purpose of this
project is to make secure, digitalized and easier attendance system via face. Our face is our id card
according to this project.

Intended Audience
We have worked on this project for attendance system so the audience of this system will be:
1. Students
2.Admin
Project Scope
Provides facility for the automated attendance of students.
 Uses live face recognition to recognize each individual and mark their attendance automatically.
 Utilizes video and image processing to provide inputs to the system.
 Facility of marking manual attendance
.

Overall Description
Product Perspective
The task of face recognition is to identify an already detected and scanned known or unknown face and
in more advance cases it exactly tells whose face it is. Often the problem of face recognition is confused
with the problem of face detection.

Deep Learning is one among the interesting domain that enables the machine to train itself by providing
some data sets as input and provides an appropriate output during testing by applying different learning
algorithms. Nowadays, Attendance is considered as an important factor for both the student as well as
the teacher of an educational organization. Every institute has its own method in this regard. Some are
taking attendance manually using the old paper or file based approach and some have adopted methods
of automatic attendance using some biometric techniques. Automated Attendance System is a process to
automatically estimate the presence or the absence of the student in the classroom by using face
recognition technology. It is also possible to recognize whether the student is sleeping or awake during
the lecture and it can also be implemented in the exam sessions to ensure the presence of the student.

Definitions:
Users: This means students who will get the most befits of the system.
Admin: This is for the system management, and it will be presented by the employees.
Timeline
Python learning 10 days
Python IDE + Python installation 1
Library identification for facial ??? 1
Comparison : Compatibility of Pycharm Python 5
Static image face detection using OpenCV 2
Real time face detection with Web Camera 6
Database storage 5
Comparison : Face dataset concept 3
Issue solved 3
Learning : Face Recognition Models 2
Preprocessing face dataset 2
GUI using ??? 3
Facial landmark detection 5
Eye blink detection 5
Static face recognition 2
Automated attendance making with identified 4
label
Attendance report generation 2
Integration of system 7
Testing of the system 5
total 73 days(2 months 13 days)

Project Plan
These are some of the plans that are prepared by us. As per our plan project could have took of more
than 4 months but neglected some of features and we planned to complete it in 2 months and few days
exactly.
 Detection of unique face image surrounding the other natural component such as walls and other
backgrounds.
 Detection of faces along with other face characters such as beard, spectacles etc.
 Extraction of unique characteristic features of a face useful in face recognition.
 Effective recognition of unique faces in a class (individual recognition).
 Automated update in the attendance sheet without human intervention.
 To keep the student updated with their attendance ratio.

Product Features
These are some of the features that our system will be providing. Our team tried our best to make our
system more reliable, easier to use and secure. We are quite optimistic that our work will help other
researcher in near future. Authorized by administrator.
 Registration of student details and faces.
 Automatically captures images at the time of registration
 Creation of student’s folder where images are stored is created automatically.
 Face are recognized matching with registered image
 Unknown persons are identified and invalid message pop up.
 Excel sheet and sheet is created automatically if not created.
 Reports are generated as a when required

User Classes and Characteristics

Term Definition
Student A person whose Face is to be recognized
Admin A person who handles the application and enrolls a person image in the
database
Database Collection of all the information about the image of face and data of a
person
Face detection and Control system for using human face for attendance.
recognition
Stakeholder Any person who has contributed to the project
Feature Result of information of the matrix which derives from image

Benefits
Some benefits that our system will be providing are given. We will be trying to provide more benefits in
coming days. Recently, these are some limited benefits that we think our system will definitely perform.
 Easy to use.
 Saves time and efforts as it does attendance without any interaction
 Used for security purposes.
 Unknown faces are identified.
 Stores the faces in database that are detected during registration and automatically marks attendance
faster. Providing authorized access.
Tools and Technologies

Tools
Software Components
 PyCharm
 Microsoft Excel
Hardware Components
 Web Camera
 Laptop

Technologies
 Kivy
 PyCharm libraries
Data Model Design Diagrams

Use case diagram

Sequence diagram

Sequence diagram for admin panel

Class diagram
Activity diagram
Activity diagram for login process
Functional Requirements

Adding a New student

Function: Sign up a new student to the system.
Priority: Top (Required for first release)
Requirements: To add a new user to the system, student must consult with admin in order to store the
images of him/her in a database.

Use the system to attend to class

Function: Attend to class
Priority: Top (Required for every class attended)
Requirements: when student enter in a class he/she should use the system in order to be recognized by the system
so that system will make their attendance done.

Admin can view a full report

Function: Faculty can view a current report every class.
Priority: Top
Requirements: admin can see the full reports of the students. (presents and absents days)

Students missed classes

Function: Students will mark as absent in excel sheet
Priority: High
Requirements: When a student misses a class, he/she will mark as absent in excel class.
System functional requirement describes activities and services that must provide.

 A user must be able to manage student records.

 An only authorized user must be able to use the system.
 A system must be attached to wireless camera and face recognition should be smooth.
 The administrator or the person who will be given the access to the system must login into the
system before using it.
 The information must be entered and managed properly.
Non-functional Requirements

Non-functional requirements are set of requirements with specific criteria to judge the systems
operation. These requirements have been collected based on the following after meetings with the
client. Non-functional requirements possess the following points:
 The GUI of the system will be user-friendly.
 The data that will be shown to the users will be made sure that it is correct and is available for the
time being. The system will be flexible to changes.
 The system will be extended for changes and to the latest technologies.
 Efficiency and effectiveness of the system will be made sure.
 The performance of the system will be made sure.

They cover ease of use to the client, security, support availability, operational speed, and
implementation considerations. More specifically:

 The user will find it very convenient to take photos.

 Users must be informed when taking a photo with clear instructions on how to position their
faces.
 The system is very secure.
 The system will have a response time in seconds.
 The system can be easily installed.
 The system is 100% efficient.
 The system must be fast and reliable.
Reports

The experiment was conducted in accordance to the proposed framework. Thus, the implementation of
the framework was done using Microsoft Visual Studio platform while the database was implemented
on Microsoft SQL. The experiment was performed using single image, the image was localized. Face
of a user will be scan and detected without any interaction. If the face is matched it will store a present
day in excel else, it will show sorry user invalid message. Admin can add the user, for that admin
needed to store the images of a user in a database. Admin also can delete user if necessary. The
experimental result of this study indicates that through the combination of multiple algorithms, this
system improves the matching performance, the issue of illumination and deter spoofing. The approach
considerably reduces the computation time and improves the recognition accuracy. Moreover, this
automated attendance system is quite simple requiring few components and is effective and efficient
enough to be integrated within academic environment. Based on the results of our project this system
works as we were thinking. We are pretty optimistic that our work will change and bring light in the
attendance methods.

System flow
Talking about the system analysis it has three main process of working mechanisms. At first process
student will start to show his face. In second process, image will process and try to match will the
database and in third process system will automatically update the attendance. It will mark as present if
the student’s face is detected else absent.
 Figure: System flow Diagram

Future Direction

This system is just a part of the project although we tried our best to build an effective system. facial
recognition attendance systems are not widely used in our region. Talking about the future of this
system, almost all of the offices, schools, colleges and organizations will be using it as attendance
taking system. facial recognition system is being enhanced day by day to make it more secure and easier
for the users and administrators as well. We believe that a time will come when our face will be our id
card. We will also try to enhanced our system in near future with high budget, using best accessories.

Conclusion
By the end of this project we were able to implement a complete low cost surveillance prototype that
provides complete face detection and recognition. The success of our prototype is demonstrated in the
test results. The system does not need complex installation and the portability of the prototype aloes the
user to diversify the use. We were able to complete the given project with our best team. We faced
many difficulties but we worked hand in hand to overcome those difficulties and able to root out them.
As we already said that this is only a project due to which we got limited time for it. In coming future
our team will be working on this project in detail in order to enhanced the way of facial recognition
based attendance system. we are pretty sure that our project and works will be helpful for others who
will be working on facial recognition system in near future.