Multiple student attendance system using face recognition

Abstract

  Maintaining  attendance  in  every  institution  is  compulsory  and  an  important  part  of  the  academic 
performance  of  students.  This  attendance  system  can  play  a  major  role  for students. Instructor has to 
mark attendance carefully without making any wrong attendance. This process is time consuming.  
 
  The  aim  is  to develop the automated system for detection and recognition of faces using the live stream 
from  camera.  This would enable the education system or the organizations to manage their attendance 
efficiently.This  project  has  applications  such  as  real  time  multiple  students  attendance  when  they 
enter into a room. 
 
 
Implementation

It has three phases of implementation:

● Training dataset & Applying Facial recognition Algorithm

● Get live feed from IP camera
● Marking the attendance

Proposal Timeline
Before April 20​:

Acquiring the dataset and studying on face recognition algorithms

April 20 – May 23 (Before the official coding time):

To start self working on developing the system. I would discuss the procedures and the
possibilities to be tested or implemented for the best outcome. Algorithms and other things
could be further discussed with the mentor to finalize the efficiency.
This would give me a straight direction to achieve the goal efficiently.

May 23 – June 18 (Official coding period starts):

Implementing all the procedures and functions of the code. Analyzing the efficiency of the
system.

June 18 – July 5:

Bringing about the decided changes in the functionality of the code or in its implementation.
Implementing all of the discussed and agreed functionality of the code.
Testing of the whole code and generating some test results.

JULY 6th MID TERM EVALUATION

July 6 – July 15:

Making further changes in the code to improve the Functionality, Exception handling, Bug
Removal.
July 15 – July 25:

To be in constant touch with the Mailman3’s developers and to let them know about our
progress.
Most of the time will be consumed for rigorous testing and bug fixes.
July 25 – July 31​:

For Documentation
A buffer of two weeks has been kept for any unpredictable delay.