System Requirements Document (SRD) for Sweet-Form

1. Introduction

The Sweet-Form project is a CLI/DI (Customer Lifetime Insights/Data Insights) assessment form and dashboard system designed to provide users with an intuitive and visually appealing interface for managing and analyzing data. This document outlines the system requirements for the Sweet-Form project, ensuring alignment with the project's goals and user expectations.

This SRD has been tailored for admep bza, based in India (IN), and incorporates locale-specific considerations such as time zones (IST) and user preferences for a clean, modern design with a soothing yet professional aesthetic.

2. System Overview

The Sweet-Form system is a dual-purpose platform that combines:

1. Assessment Forms: For collecting and managing CLI/DI data.
2. Dashboards: For visualizing and analyzing the collected data.

The system aims to:

• Provide a seamless user experience with a focus on usability and aesthetics.
• Utilize a clean, modern UI framework with a professional yet approachable design.
• Support both administrators and end-users in managing and interpreting data effectively.

The system will be accessible via web and mobile platforms, ensuring flexibility and convenience for users.

3. Functional Requirements

• As a User, I should be able to fill out CLI/DI assessment forms with ease.
• As a User, I should be able to view my submitted forms and their statuses.
• As an Admin, I should be able to create, edit, and manage assessment forms.
• As an Admin, I should be able to view and analyze data insights through dashboards.
• As a User, I should be able to export my data in multiple formats (e.g., PDF, CSV).
• As an Admin, I should be able to manage user roles and permissions.
• As a User, I should receive notifications for form submission deadlines.
• As an Admin, I should be able to generate reports based on collected data.

4. User Personas

4.1 Admin

• Role: Manages forms, user roles, and data analysis.
• Needs: Tools for creating/editing forms, managing users, and generating reports.
• Skills: Intermediate to advanced technical proficiency.

4.2 User

• Role: Completes assessment forms and views dashboards.
• Needs: Intuitive forms, data export options, and notifications.
• Skills: Basic to intermediate technical proficiency.

5. Visuals Colors and Theme

Color Palette

The Sweet-Form project will use a clean and modern color palette with a soothing yet professional aesthetic:

• Background: #F5F9FF (Soft Blue-White)
• Surface: #FFFFFF (Pure White)
• Text: #2E3A59 (Deep Navy Blue)
• Accent: #5A9BD5 (Calm Sky Blue)
• Muted: #A6B1C0 (Soft Gray-Blue)

Fonts

• Primary Font: "Inter" (Sans-serif, clean and professional)
• Secondary Font: "Roboto" (Sans-serif, modern and approachable)

6. Signature Design Concept

Glassmorphism Dashboard with Interactive Data Widgets

The Sweet-Form homepage/dashboard will feature a glassmorphism design with the following elements:

1. Background: A subtle gradient transitioning from soft blue (#F5F9FF) to light purple (#E8EAF6), creating a calming and professional atmosphere.
2. Glass Panels: Semi-transparent cards with frosted glass effects, slight blurs, and soft shadows. These panels will house key dashboard widgets such as form statuses, data insights, and notifications.
3. Interactive Widgets:
   • Hover Effects: Widgets will slightly "lift" with a shadow effect when hovered over, providing a tactile feel.
   • Real-Time Animations: Data charts will animate in real-time, with smooth transitions for updates.
   • Micro-Interactions: Buttons and icons will feature subtle animations, such as color shifts or slight scaling, upon interaction.
4. Call-to-Action Buttons: Prominent buttons with gradient fills (e.g., #5A9BD5 to #4A90E2) and rounded corners for a modern look.
5. Navigation: A sticky top navigation bar with a glassmorphic effect, ensuring easy access to key sections.

This design will make the Sweet-Form dashboard visually striking and highly engaging, leaving a lasting impression on users.

7. Non-Functional Requirements

• Performance: The system should load within 2 seconds for all users on a standard broadband connection.
• Scalability: The backend should support up to 10,000 concurrent users.
• Security: User data must be encrypted both in transit (TLS 1.3) and at rest.
• Accessibility: The UI must comply with WCAG 2.1 Level AA standards.
• Localization: The system should support Indian time zones (IST) and currency formats.

8. Tech Stack

Frontend

• React for Web
• React Native for Mobile App

Backend

• Python
• FastAPI

Database

• MySQL (with Alembic for migrations)

AI Models

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

AI Tools

• Litellm for LLM Routing
• Langchain

Orchestration

• Docker for local orchestration
• Kubernetes for server-side orchestration

9. Assumptions and Constraints

Assumptions

• Users will primarily access the system via modern browsers (Chrome, Edge, Firefox).
• The majority of users will have basic to intermediate technical proficiency.

Constraints

• The system must operate within the constraints of Indian data protection laws.
• The design must accommodate both desktop and mobile users.

10. Glossary

• CLI: Customer Lifetime Insights
• DI: Data Insights
• Glassmorphism: A design trend characterized by frosted glass-like elements with transparency and blur effects.
• WCAG: Web Content Accessibility Guidelines
• LLM: Large Language Model
• IST: Indian Standard Time