danhdct122c3/smart_campus

Purpose and Entry Points

This is a Smart Campus/employee-management platform: a React single-page frontend backed by a Python API designed for AWS Lambda, with attendance/face recognition, workforce workflows, notifications, analytics, security, and AI assistance. Frontend bootstraps at frontend/src/main.jsx and routes through frontend/src/App.jsx. Backend application assembly is in backend/app/main.py; Lambda invocation is adapted by backend/app/handler.py.

API Composition and Runtime Boundary

The backend is a modular Python API. backend/app/api/router.py is the central route aggregation boundary; each business module exposes a router and separates request schemas, service logic, and (where needed) repository access. Shared configuration, exception handling, and response conventions live in backend/app/core/config.py, backend/app/core/exceptions.py, and backend/app/core/responses.py. Environment values are represented by backend/.env.example.

Identity, Users, and Access Control

Authentication and user lifecycle are centered in backend/app/modules/auth/router.py, backend/app/modules/auth/service.py, and backend/app/modules/users/service.py. The frontend retains session/auth state in frontend/src/context/AuthContext.jsx and enforces UI access through frontend/src/components/ProtectedRoute.jsx. AWS Cognito setup is represented by aws-image/setupCognito; IAM provisioning is represented by aws-image/setupIAM.

Attendance and Biometric Flow

Attendance processing combines API handling, persistence, and policy evaluation: backend/app/modules/attendance/router.py, backend/app/modules/attendance/service.py, and backend/app/modules/attendance/rule_engine.py. Face enrollment/recognition is isolated in backend/app/modules/faces/service.py and its repository. These modules cross the AWS service boundary through backend/app/shared/aws/rekognition.py, with deployment provisioning indicated by aws-image/setupRekognition.

Operational Domain Modules

Employee-facing workflow APIs are organized by bounded domain: leave requests in backend/app/modules/leaves/service.py, task management in backend/app/modules/tasks/service.py, and notification delivery/state in backend/app/modules/notifications/service.py. Administration/security controls are handled by backend/app/modules/security/service.py and backend/app/modules/security/settings_repo.py. The corresponding SPA pages are frontend/src/pages/Leaves.jsx, frontend/src/pages/Tasks.jsx, and frontend/src/pages/Notifications.jsx.

Asynchronous Events, Notifications, and Analytics

Workers separate non-request processing from API execution: backend/app/workers/notification_worker.py, backend/app/workers/analytics_worker.py, and backend/app/workers/security_worker.py. Event and messaging integrations are encapsulated in backend/app/shared/aws/eventbridge.py and backend/app/shared/aws/sns.py; infrastructure folders also indicate EventBridge, SQS, SES, and CloudWatch usage (aws-image/setupEvenBridge, aws-image/setupSQS, aws-image/setupSES, aws-image/setupCloudWatch). Reporting services/repositories in backend/app/modules/reports/service.py and backend/app/modules/reports/repository.py likely consume Athena through backend/app/shared/aws/athena.py.

AI, Data, and AWS Deployment Surface

The AI assistant API is implemented in backend/app/modules/ai_assistant/service.py and reaches Amazon Bedrock via backend/app/shared/aws/bedrock.py; its client page is frontend/src/pages/AIAssistant.jsx. Persistence and object storage adapters are backend/app/shared/aws/dynamodb.py and backend/app/shared/aws/s3.py, with AWS setup coverage for DB, S3, Lambda, API, CloudFront, WAF, X-Ray, and CodePipeline under aws-image/. CI build entry points are buildspec-backend.yml and buildspec-frontend.yml.