System Requirements Document (SRD)

Project Name: sweet-chat

1. Introduction

The sweet-chat project is a real-time chat application designed as a university project by Aaron in India. The primary goal of this project is to create a functional and user-friendly platform where users can communicate instantly, share files, and organize group chats. The application will demonstrate key features such as message storage, online status, notifications, and secure communication, tailored to meet the needs of academic environments.

This document outlines the system requirements for sweet-chat, including functional and non-functional specifications, user personas, design concepts, and technical considerations.

2. System Overview

sweet-chat is a real-time chat application aimed at facilitating seamless communication among users, particularly in a university setting. The system will allow students, faculty, and staff to register, create chat rooms or groups, and exchange messages securely and efficiently.

Key features include:

• Instant messaging with message storage and retrieval.
• Online/offline status display for users.
• Push notifications for new messages or updates.
• File and media sharing capabilities.
• A simple and intuitive interface optimized for both web and mobile platforms.

The system will prioritize performance, security, scalability, and reliability to ensure a smooth user experience.

3. Functional Requirements

As User:

• I should be able to register and log in to the application.
• I should be able to send and receive messages instantly.
• I should be able to create chat rooms or groups for communication.
• I should be able to view the online/offline status of other users.
• I should be able to access message history.
• I should receive push notifications for new messages or updates.
• I should be able to share files and media within chats.

4. User Personas

1. Student

• Description: Primary users of the application. Students use the platform for study groups, event planning, and casual communication.
• Needs: Instant messaging, group chats, file sharing, and notifications.

2. Faculty

• Description: Professors and academic staff who use the platform for sharing resources, announcements, and coordinating with students.
• Needs: Secure communication, file sharing, and group creation.

3. Admin

• Description: System administrators responsible for managing user accounts, monitoring system performance, and ensuring security.
• Needs: User management, system monitoring, and access to logs.

5. Visuals Colors and Theme

Color Palette:

The sweet-chat application will feature a vibrant yet professional color scheme to appeal to university users:

• Background: #F5F5FA (Soft Lavender Gray)
• Surface: #FFFFFF (Pure White)
• Text: #333333 (Charcoal Black)
• Accent: #4A90E2 (University Blue)
• Muted Tones: #B0BEC5 (Cool Gray)

This palette ensures readability, professionalism, and a welcoming aesthetic suitable for academic environments.

6. Signature Design Concept

Interactive Campus Map Homepage

The homepage of sweet-chat will feature an interactive campus map design. Users will see a stylized map of a university campus, with clickable buildings representing different chat functionalities:

• Library: Study group chats.
• Cafeteria: Casual chats.
• Classrooms: Academic discussions.
• Admin Office: System settings and admin controls.

Hovering over each building will display animations like glowing outlines or subtle pulsations. Clicking on a building will transition users into the respective chat room or feature with smooth zoom-in animations.

The map will include micro-interactions such as:

• Animated pins for active chat rooms.
• A dynamic day/night cycle reflecting the user’s local time.
• A subtle background soundtrack of campus ambiance (optional).

This design concept will make the application visually engaging and memorable while reinforcing its academic theme.

7. Non-Functional Requirements

• Performance: Messages must be delivered in under 1 second.
• Security: All messages and files must be encrypted using industry-standard protocols.
• Scalability: The system should handle concurrent usage by multiple users without degradation.
• Usability: The interface must be simple, intuitive, and accessible for users of varying technical expertise.
• Reliability: The system uptime should exceed 99.9%.
• Compatibility: The application must function seamlessly on both web and mobile platforms.

8. Tech Stack

Frontend:

• React for Web
• React Native for Mobile

Backend:

• Python
• FastAPI

Database:

• MySQL (preferred for relational data)
• MongoDB (for NoSQL requirements)

AI Models:

• GPT 5.4 for user-friendly responses.
• Claude 4.6 Opas for academic or coding assistance.

AI Tools:

• Litellm for LLM Routing.
• Langchain for advanced AI workflows.

Orchestration:

• Docker and docker-compose for local development.
• Kubernetes for server-side orchestration.

9. Assumptions and Constraints

Assumptions:

• Users will primarily access the application via university-provided devices or personal smartphones.
• Internet connectivity will be stable within the university campus.
• The application will be used for academic and casual communication, not for commercial purposes.

Constraints:

• Development must be completed within the academic semester timeline.
• The system must adhere to university IT policies and data protection regulations.
• Limited budget for hosting and infrastructure.

10. Glossary

• Real-Time Messaging: Communication where messages are delivered instantly without noticeable delay.
• Push Notifications: Alerts sent to users’ devices to notify them of new messages or updates.
• Encryption: The process of converting data into a secure format to prevent unauthorized access.
• Scalability: The ability of the system to handle increased user load without performance degradation.
• LLM Routing: The process of directing queries to the appropriate large language model for optimal responses.

End of Document