SMART ATTENDANCE

Introduction

The Smart Attendance Management System is a modern application designed to digitize the college attendance process. It replaces traditional paper registers and manual attendance with a secure, QR-based, GPS-validated, cloud-connected system. This document outlines the system requirements for the Smart Attendance project, focusing on its functionalities, user roles, workflows, and design elements.

System Overview

The Smart Attendance Management System aims to streamline and automate the attendance process for colleges. It provides a comprehensive solution that includes secure login, real-time analytics, and automated attendance calculations. The system is designed to support four primary user roles: Student, Subject Staff, Mentor, and Management. Each role has specific functionalities and limitations to ensure a secure and efficient attendance process.

Source Content Inventory

• User Roles: Student, Subject Staff, Mentor, Management
• Attendance Workflow: QR-based, GPS-validated, biometric confirmation
• Technology Stack: Flutter, Dart, Firebase Authentication, Cloud Firestore, Firebase Storage, Firebase Cloud Messaging, Riverpod, GoRouter, MVVM + Repository Pattern, Material Design 3

Functional Requirements as Story Points

• As a Student, I should be able to log in securely.
• As a Student, I should be able to view my attendance percentage.
• As a Student, I should be able to view subject-wise and semester attendance.
• As a Student, I should be able to display my personal dynamic QR during attendance.
• As a Student, I should be able to apply for Medical Leave and On Duty (OD).
• As a Student, I should be able to upload Medical/OD certificates.
• As a Student, I should receive notifications about attendance and leave status.
• As a Subject Staff, I should be able to log in and select the department, year, section, and subject.
• As a Subject Staff, I should be able to start an attendance session and scan student QR codes.
• As a Subject Staff, I should be able to review and submit attendance after biometric verification.
• As a Mentor, I should be able to review submitted attendance and edit it before semester finalization without entering a reason.
• As a Mentor, I should be able to approve or reject Medical Leave and OD requests.
• As a Mentor, I should be able to monitor attendance percentages and finalize semester attendance.
• As Management, I should be able to create and manage students, staff, mentors, departments, and subjects.
• As Management, I should be able to view analytics, generate reports, and export them in various formats.

User Personas

1. Student: Engages with the system to view attendance, submit leave requests, and receive notifications.
2. Subject Staff: Responsible for conducting attendance sessions and submitting attendance records.
3. Mentor: Oversees attendance records, approves leave requests, and finalizes attendance.
4. Management: Manages system configurations, user roles, and generates reports.

Core User Flows

• Student Attendance: Student logs in -> Views attendance -> Displays QR code -> Subject Staff scans QR -> Attendance is validated and recorded.
• Leave Application: Student applies for leave -> Uploads certificate -> Mentor reviews and approves/rejects -> Student receives notification.
• Attendance Session: Subject Staff logs in -> Selects class details -> Starts session -> Scans QR codes -> Reviews and submits attendance.
• Attendance Finalization: Mentor reviews attendance -> Edits if necessary -> Finalizes attendance at semester end -> Management accesses reports.

Visuals Colors and Theme

• primary: #1E88E5 (Deep Blue)
• primary_light: #BBDEFB (Light Blue)
• secondary: #FF7043 (Coral)
• accent: #FFC107 (Amber)
• highlight: #FFEB3B (Gold)
• bg: #F5F5F5 (Light Gray)
• surface: rgba(255, 255, 255, 0.8)
• text: #212121 (Dark Gray)
• text_muted: #757575 (Muted Gray)
• border: rgba(0, 0, 0, 0.1)

Signature Design Concept

Interactive QR Code Experience: The landing page features an interactive QR code that dynamically changes as users hover over it. This QR code represents the core of the attendance system. As users interact, the QR code animates to reveal different layers of information, such as student ID, session token, and timestamp. This interaction is powered by motion/react, providing a seamless and engaging user experience. The QR code refreshes every few seconds, symbolizing the dynamic nature of the system.

Landing Hero Motion Brief

The hero section showcases a student's journey through the attendance process. The animation begins with a student entering a classroom, displaying their QR code, which then transforms into a digital attendance record. This transformation highlights the system's efficiency and security. The animation loops every 10 seconds, with smooth transitions and a focus on the QR code's role in the process.

Interaction Model & Motion Direction

• Intended Interaction Model: Animated
• Description: The landing page features moderate scroll-triggered reveals and hover transitions. Interactive elements, such as the QR code, have spring physics to enhance user engagement. Each section on the landing page has a distinctive core mechanic, ensuring a unique and memorable experience.

Non-Functional Requirements

• The system must ensure data security and privacy through encrypted QR codes and secure authentication.
• The application should be scalable to accommodate multiple campuses and large user bases.
• The system must provide real-time analytics and reporting capabilities.

Tech Stack

• Frontend: Flutter
• Backend: Firebase Authentication, Cloud Firestore
• Storage: Firebase Storage
• Messaging: Firebase Cloud Messaging
• State Management: Riverpod
• Routing: GoRouter
• Design Pattern: MVVM + Repository Pattern

Assumptions and Constraints

• The system assumes that all users have access to smartphones with GPS and camera capabilities.
• The application is constrained to operate within the college's Wi-Fi network for optimal performance.
• The QR code system requires periodic updates to ensure security and functionality.

Glossary

• QR Code: A machine-readable code used for attendance marking.
• GPS Validation: A process to ensure the student is within the designated area for attendance.
• Biometric Verification: Using Face ID or Fingerprint to confirm attendance submission.
• MVVM: Model-View-ViewModel, a software architectural pattern.
• Riverpod: A state management library for Flutter applications.

This document provides a comprehensive overview of the Smart Attendance Management System, detailing its functionalities, user roles, workflows, and design elements. The system is designed to be secure, scalable, and user-friendly, offering a modern solution to college attendance management.