University Institute of Information Technology,

PMAS-Arid Agriculture University,

Rawalpindi Pakistan

E-Attendance & Class Monitoring:

Empowering Class Management Using AI in
UAAR
By
Muhammad Jahangir 20-ARID-617
Muhammad Saif Ud Din Umar 20-ARID-623
Muhammad Fahad Hussain 20-ARID-609

Supervisor
Dr. Muhammad Aqib
Bachelor of Science in Computer Science (2020-2024)
Computer Science
 DECLARATION

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

Muhammad Jahangir Muhammad Saif Ud Din Umar Muhammad Fahad Hussain

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

II
 CERTIFICATE OF APPROVAL

It is to certify that the final year project of BS (CS) “E-Attendance & Class Monitoring:
Empowering Class Management Using AI in UAAR” was developed by “Muhammad
Jahangir, 20-ARID-617”, “Muhammad Saif ud Din Umar, 20-ARID-623” and
“Muhammad Fahad Hussain, 20-ARID-609” under the supervision of “Dr. Muhammad
Aqib” and that in their opinion; it is fully adequate, in scope and quality for the degree of
Bachelors of Science in Computer Science.

---------------------------------------
Dr. Muhammad Aqib
Supervisor

---------------------------------------
(Ms. Irum Rubab)
External Examiner

---------------------------------------
Director UIIT

III
 Executive Summary
In public places, there is often a need for monitoring people and different activities going on,
which can be referred later for many reasons including security. Appointing humans for this
task involves many problems such as increased employee hiring, accuracy problem, trust, no
proof for later use, and also the fact that a human can remember things till a certain time limit.
Talking about the current security system, they use dumb still cameras with a continuous
recording facility irrespective of the fact that any event may happen or not. Moreover they are
usually pointing at a specific user defined locations so more than one cameras are required to
cover the entire region.
To prevent all these problems from prevailing, the CSCS is developed. It is a surveillance
system, which provides solution to many of these problems. It is a stand-alone application
which doesn’t require any computer to operate. It monitors different situations using a camera
which is able to rotate intelligently based on sensor messages and captures the scene in the
form of video or photos later reference as well.
Customizable Surveillance Control System (CSCS) is a surveillance system that can be
assigned a sensor type as in our case a heat sensor is used, it works accordingly, rotates the
camera upon event detection and perform user defined actions like capturing video and stores
them, for the future use.
It is an embedded system consisting of Linux fox kit with embedded a running server
application also a camera, USB storage device and a sensor node base station is attached with
fox kit. LAN communication is used by user to download the videos and to operate the system
manually.

IV
 Acknowledgement

All praise is to Almighty Allah who bestowed upon us a minute portion of His boundless
knowledge by virtue of which we were able to accomplish this challenging task.

We are greatly indebted to our project supervisor “Dr. Muhammad Aqib” for personal
supervision, advice, valuable guidance and completion of this project. We are deeply indebted
to him for encouragement and continual help during this work.

And we are also thankful to our parents and family who have been a constant source of
encouragement for us and brought us the values of honesty & hard work.

Muhammad Jahangir Muhammad Saif Ud Din Umar Muhammad Fahad Hussain

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

V
 Abbreviations

UAAR University of Arid Agriculture Rawalpindi

MERN Stack MongoDB, Express js, React js, Node js

AI Artificial Intelligence
API Application Programming Interface
MVC Model-View-Controller
IP Information Page
UML Unified Modeling Language

VI
 Table of Contents
Introduction.............................................................................................................................1
Chapter 1: Introduction........................................................................................................ 1
1.1. Brief .............................................................................................................................. 1
Expected Outcomes: ................................................................................................................ 1
Tools and Methodology: .......................................................................................................... 1
1.2. Relevance to Course Modules ...................................................................................... 1
Software Engineering: ............................................................................................................. 1
Database Management: ............................................................................................................ 2
Web Application Development: .............................................................................................. 2
Artificial Intelligence and Machine Learning: ........................................................................ 2
Project Management: ............................................................................................................... 2
1.3. Project Background ...................................................................................................... 2
1.4. Literature Review ......................................................................................................... 3
1.5. Analysis from Literature Review (in the context of your project) ............................... 4
1.6. Methodology and Software Lifecycle for This Project ................................................ 6
1.6.1. Rationale behind Selected Methodology .................................................................. 7
1.6.1.1. Rationale behind Selected Methodology ............................................................... 8
2.1. Problem Statement ........................................................................................................ 9
2.2. Deliverables and Development Requirements.............................................................. 9
2.2.1. Deliverables .............................................................................................................. 9
2.2.2. Development Requirements: ................................................................................... 10
2.3. Current System (if applicable to your project) ........................................................... 11
Chapter 3: Requirement Analysis..................................................................................... 12
3.1. Use Cases .................................................................................................................... 12
3.1.1. Use Case Diagram ....................................................................................................... 12
Use Case 1: Mark Attendance ............................................................................................... 13
Use Case 2: Generate Attendance Report .............................................................................. 14
a. Functional Requirements ............................................................................................... 15
b. Non-Functional Requirements ....................................................................................... 16
Chapter 4: Design and Architecture................................................................................. 18
4.1. UML Structure Diagrams ........................................................................................... 18

VII
4.1.1. Component Diagram .................................................................................................... 18
4.1.2. Package Diagram: ........................................................................................................ 19
4.1.3. Deployment Diagram: ................................................................................................. 20
4.1.4. Class Diagram:............................................................................................................. 20
4.2. UML Behavioral Diagram .......................................................................................... 21
4.2.1. Activity Diagram: ........................................................................................................ 21
4.2.2. DFD: ............................................................................................................................ 22
4.4. Block Diagram: .............................................................................................................. 27

VIII
 List of Figures
Figure 1 Use Case Diagram ................................................................................................... 12
Figure 2 Component Diagram ............................................................................................... 18
Figure 3 Package Diagram-I .................................................................................................. 19
Figure 4 Package Diagram-II................................................................................................. 19
Figure 5 Deployment Diagram .............................................................................................. 20
Figure 6 Class Diagram ......................................................................................................... 20
Figure 7 Activity Diagram ..................................................................................................... 21
Figure 8 DFD Level 0 ............................................................................................................ 22
Figure 9 DFD Level 1 (Administrator) .................................................................................. 22
Figure 10 DFD Level 1 (Admin) ........................................................................................... 23
Figure 11 DFD Level 1 (Teacher) ......................................................................................... 24
Figure 12 DFD Level 1 (Student) .......................................................................................... 24
Figure 13 Sequence Diagram (student Detection) ................................................................ 25
Figure 14 Sequence Diagram (Teacher Detection) ............................................................... 25
Figure 15 Administrator (Sequence Diagram) ...................................................................... 25
Figure 16Admin (Sequence Diagram) ................................................................................... 26
Figure 17 Teacher (Sequence Diagram) ................................................................................ 26
Figure 18 Student (Sequence Diagram) ................................................................................. 26
Figure 19 Block Diagram ...................................................................................................... 27
 List of Tables
Table 1Use Case 1 : Mark Attendance .................................................................................. 14
Table 2 Use Case 2 : Generate Report ................................................................................... 15
 Chapter 1: Introduction
This chapter introduces the project on E-Attendance & Class Monitoring: Empowering Class
Management Using AI in UAAR. This first chapter contains a short preliminary note on the
project work, possible results, means, method and the main ideas, which will be discussed further
in the following sections.

1.1. Brief
The project features a face monitoring and class attendance system for improved classroom
supervision in education institutions. It aims at simplifying taking registers and enhancing
efficiency in administration. This results in an automated system that aims at ensuring
accuracy, decreased administrative workload, and improved classroom efficiency.
Expected Outcomes:
The project aims to achieve automated attendance tracking using facial recognition
algorithms, eliminating manual processes, and providing real-time updates.
Tools and Methodology:
The project utilizes the MERN stack (MongoDB, Express.js, React.js, Node.js) for
web application development. The Agile development methodology is chosen for its
adaptability and responsiveness to changing requirements.

1.2. Relevance to Course Modules

This project has been a part of each year and courses which discuss below. It is as if bringing
together everything I studied in class and applying it at this moment. The integration of
advanced technologies and methodologies reflects a synthesis of theoretical knowledge and
practical application, bridging the gap between academic learning and real-world
implementation.
Software Engineering:
The project draws heavily from software engineering principles, applying structured
methodologies in the development process. Concepts such as requirement analysis, design

1
patterns, and system architecture have been crucial in crafting a robust and scalable E-
Attendance & Class Monitoring system.
Database Management:
The incorporation of MongoDB in the project aligns with the principles of database
management studied during the degree. The design and management of the attendance
database adhere to best practices in normalization, schema design, and data modeling.
Web Application Development:
Courses focusing on web application development have played a pivotal role.
Leveraging the MERN stack (MongoDB, Express.js, React.js, Node.js) resonates with the
principles learned in these courses, emphasizing the importance of creating dynamic and
interactive user interfaces.
Artificial Intelligence and Machine Learning:
The project's emphasis on facial recognition technology and machine learning
integration directly correlates with coursework in artificial intelligence and machine learning.
Understanding algorithms, data training, and model integration have been instrumental in
developing the AI-based attendance system.
Project Management:
The utilization of Agile development methodology reflects a conscious application of
project management principles studied during the degree. The iterative and incremental
approach ensures adaptability to changing requirements and fosters effective collaboration
within the development team.

1.3. Project Background

It The genesis of the E-Attendance & Class Monitoring project is rooted in the imperative to
modernize and enhance the efficiency of attendance tracking in educational institutions. The
project envisions a departure from traditional manual methods, introducing advanced facial
recognition technology to automate and streamline the attendance management process.
Rationale for Project:
The traditional methods of manual attendance are labor-intensive, prone to errors, and
often result in administrative inefficiencies. Recognizing these challenges, the project seeks
to leverage technological advancements to revolutionize classroom attendance tracking.

2
Introduction to Facial Recognition:
The fundamental idea revolves around the integration of facial recognition technology
into the educational environment. Facial recognition is a biometric technology that identifies
and verifies individuals based on unique facial features. In the context of this project, it
involves capturing and analyzing facial characteristics to mark attendance accurately.
Comparison with Traditional Systems:
Comparing the proposed system with traditional methods, where attendance is
manually recorded, highlights the potential for significant improvements. The automated
system aims to mitigate common issues associated with manual attendance, such as
inaccuracies, time consumption, and susceptibility to fraudulent practices.
Conceptual Framework:
The conceptual framework of the project envisions a seamless process where students
and teachers are automatically marked as 'present' when detected in the classroom during
scheduled class times. This transition from manual to automated attendance aligns with the
broader technological advancements shaping educational methodologies.
Adaptability and Innovation:
The project is designed to be adaptable to various educational settings, accommodating
schools, colleges, universities, and even corporate training environments. It introduces
innovation by combining computer vision, machine learning, and web technologies to create
a user-friendly and efficient attendance management system.

1.4. Literature Review

The literature review serves as a comprehensive exploration of current trends, research
endeavors, and existing products relevant to the E-Attendance & Class Monitoring project.
This section lays the foundation for understanding the state of the art in attendance tracking
and facial recognition technologies.
Facial Recognition Systems:
The literature reveals a surge in the development of facial recognition systems for
attendance tracking. Notable advancements include systems utilizing deep learning
algorithms for improved accuracy. However, concerns are raised regarding their performance
under varying lighting conditions and potential inaccuracies introduced by changes in facial
appearance.

3
Student Attendance Management System:
Several studies delve into the development of Student Attendance Management
Systems. These systems, often web-based, employ technologies such as JSP, Java Servlets,
HTML, CSS, Bootstrap, and MySQL for manual attendance marking. While they offer
automation, concerns linger about errors and time consumption during the attendance
recording process.
Attendance Management System:
Literature surrounding Attendance Management Systems using HTML5, CSS3, PHP,
and MySQL highlights streamlined attendance tracking. However, potential limitations
include compatibility issues with older PHP versions and uncertainties about data security
measures.
Emerging Technologies in Education:
Beyond attendance-specific systems, there is a broader exploration of emerging
technologies in education. The integration of AI, machine learning, and computer vision is
gaining traction, indicating a paradigm shift toward more innovative and automated
educational processes.
Real-time Monitoring in Educational Technology:
Studies emphasize the importance of real-time monitoring in educational technology.
The ability to provide instantaneous updates on attendance and classroom activities is
identified as a key factor in enhancing the overall educational experience.
User Authentication and Security in Educational Systems:
The literature review also touches upon the crucial aspect of user authentication and
security in educational systems. Ensuring secure access to attendance data is emphasized,
highlighting the importance of safeguarding sensitive information within the educational
context.

1.5. Analysis from Literature Review (in the context of your project)
This This section conducts a critical analysis of the E-Attendance & Class Monitoring project
in comparison to discussions and findings from the literature review. The goal is to highlight
the project's distinct contributions, address potential challenges identified in the literature, and
emphasize the innovative advancements that set this system apart.
Facial Recognition Systems:

4
 The literature underscores concern regarding the accuracy of facial recognition
systems under varying conditions. In response, the proposed project acknowledges these
challenges and aims to implement adaptive algorithms capable of handling diverse lighting
conditions. The emphasis is on achieving high accuracy in facial identification, thereby
minimizing errors associated with changes in facial appearance.
Student Attendance Management System:
Existing student attendance management systems, while introducing automation, are
criticized for potential errors and time consumption during attendance recording. In contrast,
the proposed project aims to eliminate these issues by adopting a real-time facial recognition
approach, ensuring accuracy without compromising instructional time.
Attendance Management System:
Literature highlights concerns about the adaptability and security of attendance
management systems using PHP and MySQL. The proposed project addresses these concerns
by opting for the MERN stack, ensuring compatibility, scalability, and robust security
measures. The utilization of MongoDB for data storage aligns with modern database practices.
Emerging Technologies in Education:
The literature review suggests a broader trend toward the integration of emerging
technologies in education, including AI and machine learning. The E-Attendance & Class
Monitoring project aligns with this trend, leveraging facial recognition and machine learning
for automated attendance tracking. The emphasis is on providing a modern solution that aligns
with evolving educational needs.
Real-time Monitoring in Educational Technology:
Recognizing the importance of real-time monitoring in educational technology, the
proposed system places a strong emphasis on providing instantaneous updates on attendance.
The project aims to offer a real-time monitoring dashboard, empowering teachers and
administrators with immediate insights into attendance data during ongoing classes.
User Authentication and Security in Educational Systems:
Acknowledging the critical nature of user authentication and security, the project
integrates robust authentication mechanisms and security protocols. This ensures secure
access to the web application, addressing concerns raised in the literature regarding the
protection of sensitive attendance data.

5
1.6. Methodology and Software Lifecycle for This Project
A By choosing Agile, the project team aims to foster a collaborative and adaptive development
environment, ensuring the E-Attendance & Class Monitoring system remains aligned with
evolving educational needs.
Selected Methodology: Agile Development:
The E-Attendance & Class Monitoring project is anchored in the Agile Development
methodology, a dynamic and iterative approach to software development. Agile principles
prioritize flexibility, collaboration, and responsiveness to change, making it an ideal fit for
projects with evolving requirements.
Rationale behind Selected Methodology:
The decision to adopt Agile for this project stems from its inherent adaptability
and suitability for dynamic development environments. Here are specific reasons for
choosing Agile:
Flexibility:
Agile allows for the accommodation of changing requirements, a crucial aspect
given the potential evolution in the educational landscape and technology during the
project's lifecycle.
Iterative Development:
The iterative nature of Agile aligns with the project's goals, enabling the
development team to deliver increments of the system at regular intervals,
incorporating feedback and improvements.
Stakeholder Collaboration:
Agile emphasizes collaboration and regular communication with stakeholders.
This aligns with the need for continuous feedback from educators, administrators, and
students who will be end-users of the attendance management system.
Quick Adaptation:
Agile's iterative cycles enable quick adaptation to emerging technologies, user
preferences, and educational policies, ensuring the final product remains relevant and
effective.
Continuous Improvement:

6
 The Agile approach fosters a culture of continuous improvement, allowing the
development team to learn from each iteration and refine the system progressively.

1.6.1. Rationale behind Selected Methodology

Why The rationale behind choosing the Agile Development methodology for the E-
Attendance & Class Monitoring project is grounded in its suitability for dynamic software
development environments.
Flexibility and Adaptability:
Agile's inherent flexibility allows the development team to respond promptly to
changing requirements. In the context of attendance management, where educational needs
and technologies may evolve, Agile's adaptability ensures seamless incorporation of
modifications.
Iterative Development and Continuous Feedback:
Agile's iterative approach aligns with the project's commitment to continuous
improvement. Each iteration allows for incremental enhancements based on stakeholder
feedback, ensuring the system evolves to meet the dynamic nature of attendance management
in educational institutions.
Collaborative Development and Stakeholder Involvement:
The collaborative nature of Agile is instrumental in keeping the development team and
stakeholders, including educators and administrators, in sync. Actively involving end-users
throughout the development process ensures that the system is user-centric, meeting the
specific needs of those who will utilize the attendance management system.
Quick Adaptation to Emerging Technologies:
In a rapidly evolving technology landscape, Agile's ability to adapt swiftly to emerging
technologies is crucial. This aligns with the project's goal to integrate advanced facial
recognition and machine learning for attendance tracking, ensuring the system remains at the
forefront of technological advancements in education.
Continuous Improvement Culture:
Through the selection of Agile, the project team aims to instill a culture of continuous
improvement. Learning from each iteration, the development team can iteratively refine the
system, addressing challenges and optimizing features. This iterative refinement aligns with

7
the project's commitment to delivering a high-quality, evolving solution for attendance
management.

1.6.1.1.Rationale behind Selected Methodology

This section delves into specific considerations and key drivers behind the decision to opt for
the Agile Development methodology.
Agile's Inherent Flexibility:
The Agile methodology is chosen for its inherent flexibility, enabling the project team
to navigate and respond adeptly to dynamic changes.
Continuous Improvement through Iterative Cycles:
The iterative nature of Agile aligns seamlessly with the project's commitment to
continuous improvement.
Agile's Emphasis on Collaboration:
The collaborative nature of Agile is instrumental in keeping the development team and
stakeholders in sync.
Agile's Swift Adaptation to Technology Changes:
In a rapidly evolving technology landscape, Agile's ability to adapt swiftly to emerging
technologies is crucial.
Cultivating a Culture of Continuous Improvement:
Through the selection of Agile, the project team aims to instill a culture of continuous
improvement.

8
Chapter 2: Problem Definition

This chapter delineates the specific problem addressed by the E-Attendance & Class Monitoring
project and extends to encompass the anticipated outcomes.

2.1. Problem Statement

The manual attendance system employed in educational institutions exhibits several critical
drawbacks. These drawbacks include inaccuracies in recording attendance, such as marking
latecomers as present, unintentionally marking absent students as present, and enabling
unauthorized individuals to fraudulently register their attendance. Moreover, manual
attendance system poses administrative challenges, such as there is a lot of time consumed in
manual setting of the class attendance record. A lot of issues occur in generating the semester
attendance report of every student. A manual attendance system leads to inefficiencies in
managing attendance records.

2.2. Deliverables and Development Requirements

2.2.1. Deliverables
E-Attendance Web Application:
User-friendly web-based applications with an interface whereby teachers and
administrators can easily track attendance.
Facial Recognition Module:
A facial recognition system that is integrated for automated attendance
marking, which employs real time facial identification.

Attendance Reports:
The system produces comprehensive reports which offer analysis of the
patterns in attendance and trends as well as for each student’s and teacher’s records.

User Documentation: Extensive documentation describing the procedure for using,

features of, and upkeep practices of the E-Attendance & Class Monitoring.

9
2.2.2. Development Requirements:
Web Development Stack:
Frontend: React.js for a dynamic and interactive user interface.
Backend: Node.js with Express.js for server-side logic.
Database: MongoDB for secure and scalable data storage.

Facial Recognition Library:

Integration of a reliable facial recognition library (e.g., OpenCV, Dlib) for
accurate identification of individuals.
Authentication and Authorization:
Implementation of secure authentication mechanisms to ensure authorized
access for teachers and administrators.
Real-Time Communication:
Integration of RESTful APIs to facilitate seamless communication between
the client and server, enabling real-time updates.
Scalability Considerations:
Design and implementation considerations for scalability to accommodate
potential future expansion.
User Interface (UI) Design:
Implementation of an intuitive and visually appealing UI design to enhance
user experience.
Documentation Tools:
Utilization of appropriate documentation tools (e.g., Swagger) for creating
comprehensive user manuals and technical documentation.
Testing Environment:
Establishment of a robust testing environment to ensure the reliability and
accuracy of the facial recognition and attendance management modules.

10
2.3. Current System (if applicable to your project)
The current attendance management system in educational institutions often relies on manual
methods, including paper-based registers or basic digital spreadsheets. These conventional
systems suffer from several limitations:
Time-Consuming Process:
Manual attendance marking is time-consuming, particularly in large classes or
institutions.
Error-Prone:
The manual process is prone to errors, such as misinterpretation of handwriting
or accidental data entry mistakes.
Limited Accessibility:
Accessibility to attendance records may be restricted, making it challenging
for students and parents to monitor attendance regularly.
Lack of Real-Time Updates:
The absence of real-time updates hinders the immediate availability of
attendance data for decision-making.
Security Concerns:
Traditional systems may lack robust security measures, posing a risk of
unauthorized access to sensitive attendance records.

11
 Chapter 3: Requirement Analysis

3.1. Use Cases

In the UML, a use case diagram will summarize the following details of our system’s users
(also known as Actors) and their interaction with the system. Following are the use
cases of our project.

3.1.1. Use Case Diagram

Figure 1 Use Case Diagram

12
Use Case 1: Mark Attendance
Use Case ID: UC-1.2.1
Use Case Name: Mark Attendance
Actors: Student, Teacher
Description: The system automatically marks attendance using facial recognition
during scheduled class times. Administrators can edit attendance
records through the dashboard.
Trigger: System initiates attendance marking during scheduled class times.
Preconditions: The administrator is logged into the system.

Postconditions: Attendance is successfully marked and recorded in the system.

Normal Flow: 1. System activates facial recognition during scheduled class.
2. System identifies and marks students present.
3. Administrator reviews and confirms attendance records through
the dashboard.
Alternative 1. In step 2 of the normal flow, if the administrator is not in the
Flows: network:
[Alternative 2. System prompts the administrator to accept the network fee.
Flow 1 – Not in 3. Administrator accepts.
Network] 4. Use Case resumes at step 3.
Exceptions: In step 3 of the normal flow, if the administrator enters an invalid
parameter:
1. System displays an error message.
2. Administrator re-enters correct parameters.
3. Use Case resumes at step 3.

13
 Includes: Admin Login
Teacher Login
Students Records
Timetable
Special Usability
Requirements: Integrity
Security
Assumptions: None

Notes and The maximum size of password is 8 characters.

Issues: Add special numeric values.
Table 1Use Case 1 : Mark Attendance

Use Case 2: Generate Attendance Report

Use Case ID: UC-1.2.2
Use Case Name: Mark Attendance
Actors: Administrator
Description: Administrators can generate attendance reports for specific classes or
time periods. The system provides a comprehensive overview of
attendance data.
Trigger: Administrator initiates report generation.
Preconditions: The administrator is logged into the system.

Postconditions: Attendance is successfully marked and recorded in the system.

Normal Flow: Administrator logs into the system.
Administrator navigates to the "Generate Report" section.
System prompts for report parameters (class, period).
System compiles and generates the attendance report.
Administrator reviews and exports the report if needed.

14
 Alternative 1. In step 2 of the normal flow, if the administrator is not in the
Flows: network:
[Alternative 2. System prompts the administrator to accept the network fee.
Flow 1 – Not in 3. Administrator accepts.
Network] 4. Use Case resumes at step 3.
Exceptions: In step 3 of the normal flow, if the administrator enters an invalid
parameter:
4. System displays an error message.
5. Administrator re-enters correct parameters.
6. Use Case resumes at step 3.
Includes: Admin Login
Special Usability
Requirements: Integrity
Security
Assumptions: None

Notes and The maximum size of password is 8 characters.

Issues: Add special numeric values.
Table 2 Use Case 2 : Generate Report

a. Functional Requirements
3.2.1. Real-Time Attendance System
The system shall implement a real-time attendance tracking feature without reliance
on location-based services.
3.2.2. Facial Recognition Integration
The system shall integrate facial recognition technology to accurately identify and
mark the attendance of individuals within the camera's view during scheduled class times.

3.2.3. User Authentication

The system shall incorporate user authentication mechanisms for teachers and
administrators, ensuring secure access to the attendance system.

15
3.2.4. Role-Based Access Control
The system shall implement role-based access control, distinguishing between
administrators and teachers, each with specific permissions related to attendance management.
3.2.5. Web Application Interface
The system shall provide a user-friendly web application interface for both teachers
and administrators to access attendance-related functionalities.
3.2.6. Real-Time Monitoring Dashboard
The system shall include a real-time monitoring dashboard, offering teachers and
administrators an overview of attendance during ongoing classes.
3.2.7. Automated Attendance Recording
The system shall automatically record attendance data in real-time as individuals' faces
are detected and recognized during class times.
3.2.8. Attendance Reporting
The system shall generate automated attendance reports for specific classes or time
periods, accessible to administrators and teachers for analysis and reporting purposes.
3.2.9. Database Management
The system shall establish and maintain a robust database to securely store attendance
records and relevant information.
3.2.10. Hardware Integration
The system shall integrate with hardware components, including a camera and GPU,
to support the facial recognition and attendance tracking functionalities.
3.2.11. Security Measures
The system shall implement security measures, including encryption and secure
protocols, to protect user data and maintain the integrity of attendance records.

b. Non-Functional Requirements
3.3.1. Performance:
The system should be capable of handling simultaneous facial recognition for a
minimum of 100 individuals within a classroom setting. The response time for marking
attendance and generating reports shall not exceed 3 seconds.
3.3.2. Scalability:

16
 The system should be scalable to accommodate an increasing number of users and
classes without compromising performance.
3.3.3. Reliability:
The system shall have an uptime of at least 99.5% to ensure continuous availability
during class hours. In the event of a system failure, the recovery time for resuming normal
operations should not exceed 30 minutes.
3.3.4. Security:
Facial recognition data and attendance records shall be encrypted to ensure the
confidentiality and integrity of sensitive information. The system shall comply with industry-
standard security practices and regulations to prevent unauthorized access and data breaches.
3.3.5. Usability:
The web application interface shall be designed with user-friendly navigation and
intuitive controls. The system shall provide user training materials and documentation for
teachers and administrators.
3.3.6. Compatibility:
The system shall be compatible with commonly used web browsers such as Chrome,
Firefox, and Safari. The web application shall support access from both desktop and mobile
devices.
3.3.7. Data Storage:
The system shall have a scalable and secure database architecture capable of storing
attendance records for an academic year. Regular backups of attendance data shall be
performed, and a recovery plan shall be in place.
3.3.8. Regulatory Compliance:
The system shall comply with relevant data protection and privacy regulations,
ensuring the ethical use of facial recognition technology.

17
 Chapter 4: Design and Architecture
This chapter will discuss the design and architecture of your system.

4.1. UML Structure Diagrams

4.1.1. Component Diagram

Figure 2 Component Diagram

18
4.1.2. Package Diagram:

Figure 3 Package Diagram-I

Figure 4 Package Diagram-II

19
4.1.3. Deployment Diagram:

Figure 5 Deployment Diagram

4.1.4. Class Diagram:

Figure 6 Class Diagram

20
4.2. UML Behavioral Diagram

4.2.1. Activity Diagram:

Figure 7 Activity Diagram

21
4.2.2. DFD:

Figure 8 DFD Level 0

Figure 9 DFD Level 1 (Administrator)

22
Figure 10 DFD Level 1 (Admin)

23
Figure 11 DFD Level 1 (Teacher)

Figure 12 DFD Level 1 (Student)

24
4.3. UML Interaction Diagrams

4.3.1. Sequence Diagram:

Figure 13 Sequence Diagram (student Detection)

Figure 14 Sequence Diagram (Teacher Detection)

Figure 15 Administrator (Sequence Diagram)

25
 Figure 16Admin (Sequence Diagram)

Figure 17 Teacher (Sequence Diagram)

Figure 18 Student (Sequence Diagram)

26
4.4. Block Diagram:

Figure 19 Block Diagram

27
1