How ahmedaziz703/student-attendance-system works
Project Type & Purpose
• Full-stack web application for managing student attendance in schools.
• Core features: secure admin/teacher login, class management, student/teacher CRUD, attendance recording, and reporting.
Inferred File Structure & Layers
• Presentation layer: HTML, CSS, JavaScript files served to the browser.
• Application layer: PHP scripts (authentication, business logic, CRUD modules).
• Data layer: MySQL database storing users, classes, attendance records.
Main Architectural Components
A. Client (Browser)
– Renders UI pages (login, dashboards, forms, reports).
– Makes HTTP(S) requests (GET/POST) to the server.
B. Web Server / Application Server
– PHP runtime (e.g., Apache + mod_php or Nginx + PHP-FPM).
– Modules/services:
• Auth Service: handles login, session management.
• Class Management Service: CRUD for classes.
• Teacher Management Service.
• Student Management Service.
• Attendance Service: recording check-ins, check-outs.
• Reporting Service: aggregates attendance stats.
C. Database Server
– MySQL instance.
– Tables: admins, teachers, students, classes, attendance_records.
D. (Optional) External Services
– SMTP for email notifications (if used).
– CDN for static assets (CSS/JS/images).
Component Interactions & Data Flow
• User → Browser: interacts via UI.
• Browser → Web Server: sends HTTP requests (login, manage entities, submit attendance).
• Web Server → DB: queries/inserts/updates data.
• Web Server → Browser: returns HTML views or JSON responses.
• Reporting Service → DB: reads aggregated data → renders charts.
Architectural Patterns & Principles
• Three-Tier Architecture (Presentation / Application / Data).
• Modular PHP services separated by functional domain.
• Stateless HTTP interactions with session-based authentication.
• Separation of concerns: each service module handles its own entities.