System Requirements Document (SRD)

Project Name: coral-mare

1. Introduction

The coral-mare project is a web-based platform designed to simplify attendance tracking for children participating in sabhas (community gatherings). This system will allow administrators to store and manage details such as name, contact number, grade, and birthday for each child. Additionally, it will provide tools for recording attendance and generating reports to ensure transparency and efficiency in managing sabha participation.

This document outlines the system requirements for coral-mare, tailored to meet the needs of Prajapati Harshit and the sabha community in India. Locale-specific considerations, such as date formats (DD/MM/YYYY), timezone (IST), and language preferences, have been incorporated to ensure the platform aligns with the user's expectations.

2. System Overview

The coral-mare system will consist of the following components:

• Database: A secure repository for storing children's details and attendance records.
• Admin Dashboard: A user-friendly interface for administrators to manage attendance, view reports, and analyze trends.
• Attendance Module: A streamlined process for recording attendance during sabhas.
• Reporting Tools: Features to generate attendance summaries and insights.

The platform will be accessible via web browsers and optimized for mobile devices, ensuring ease of use for administrators on the go.

3. Functional Requirements

Story Points:

• As Admin, I should be able to add a child's details (name, contact number, grade, birthday).
• As Admin, I should be able to record attendance for children during sabhas.
• As Admin, I should be able to view attendance summaries and generate reports.
• As Admin, I should be able to edit or delete a child's details if needed.
• As Admin, I should be able to filter attendance records by date, grade, or individual child.

4. User Personas

Admin

• Role: Manages the platform, records attendance, and generates reports.
• Needs: Easy-to-use dashboard, secure data storage, and efficient reporting tools.

Child

• Role: Participant in sabhas whose attendance is tracked.
• Needs: Accurate record-keeping of their participation.

5. Visuals Colors and Theme

Color Palette:

• Background: #F3F8FF (Soft Sky Blue)
• Surface: #FFFFFF (Pure White)
• Text: #2B2D42 (Deep Navy Blue)
• Accent: #FF6F61 (Coral Red)
• Muted Tones: #B0BEC5 (Soft Gray)

The theme reflects a calm and welcoming atmosphere, suitable for a community-focused platform. The coral red accent symbolizes energy and enthusiasm, aligning with the sabha's lively spirit.

6. Signature Design Concept

Concept: Interactive Attendance Tree

The homepage will feature a dynamic attendance tree. Each child added to the system will appear as a leaf on the tree, with their name, grade, and birthday displayed when hovered over. The tree will grow visually as more children are added, symbolizing the flourishing sabha community.

• Animation: Leaves gently sway as if in a breeze, creating a lively and engaging visual.
• Interaction: Clicking on a leaf opens a modal with detailed attendance records for that child.
• Transitions: Smooth fade-ins and color shifts when navigating between sections.
• Micro-interactions: Buttons and icons subtly pulse when hovered over, enhancing user engagement.

This design will make the platform memorable and emphasize the growth and unity of the sabha community.

7. Non-Functional Requirements

• Performance: The system should handle up to 10,000 child records without performance degradation.
• Security: All data must be encrypted in transit and at rest.
• Scalability: The platform should support future expansion, including additional features or increased user load.
• Accessibility: The interface must comply with WCAG 2.1 Level AA standards.

8. Tech Stack

Frontend

• React for Web

Backend

• Python
• FastAPI

Database

• MySQL (preferred for structured data storage)
• Alembic for migrations

AI Tools

• GPT 5.4 for user-friendly responses

Local Orchestration

• Docker
• docker-compose

Server-Side Orchestration

• Kubernetes

9. Assumptions and Constraints

Assumptions

• The sabha community will primarily access the platform via web browsers.
• Administrators will have basic technical proficiency.
• Attendance tracking will occur in real-time during sabhas.

Constraints

• The system must operate within the Indian timezone (IST).
• Data storage must comply with local data protection regulations.

10. Glossary

• Sabha: Community gathering or event.
• Admin: User responsible for managing the platform and attendance records.
• Dashboard: The interface where admins interact with the system.
• Attendance Tree: A visual representation of children participating in sabhas.