System Requirements Document (SRD)

Project Name: OneSpot

1. Introduction

The OneSpot project is a localized Smart District Tourism and Service Platform designed to integrate essential services such as tourism guidance, emergency support, and citizen interaction into a single digital platform. Unlike large-scale commercial platforms, OneSpot focuses on district-level needs, offering a practical and user-friendly experience tailored to the real-world requirements of users in India.

The primary objectives of OneSpot are:

• To provide a centralized platform for users to access district-level information and services.
• To improve accessibility to local services for both residents and tourists.
• To enhance the travel experience for tourists by offering seamless guidance and support.
• To enable better communication between citizens and local authorities.

This document outlines the system requirements for OneSpot, ensuring that the platform is designed to meet the needs of its diverse user base effectively.

2. System Overview

OneSpot is a login-based platform that provides distinct dashboards for three primary user personas: regular users, tourists, and local authorities. Each dashboard is tailored to the specific needs of the user type, ensuring a personalized and efficient experience.

Key features of the system include:

• Tourism Guidance: Access to district-level tourism information, including attractions, events, and local highlights.
• Emergency Support: Critical features such as SOS alerts, medical assistance locators, and road assistance services.
• Citizen Interaction: A platform for users to report issues, communicate with local authorities, and stay informed about district-level updates.
• Selective Re-run Capability: Users can trigger specific system functions (e.g., refreshing dashboards or reloading emergency data) without restarting the entire application.

The system is designed to be intuitive, reliable, and aligned with the needs of users in India, ensuring accessibility and practicality for all.

3. Functional Requirements

As story points:

• As a Regular User, I should be able to log in to access my personalized dashboard.
• As a Tourist, I should be able to log in to access my personalized dashboard.
• As a Local Authority, I should be able to log in to access my personalized dashboard.
• As a Regular User, I should be able to report issues directly from my dashboard.
• As a Tourist, I should be able to report issues directly from my dashboard.
• As a Local Authority, I should be able to view reported issues on my dashboard.
• As a Regular User, I should be able to view reported issues relevant to my area on my dashboard.
• As a Tourist, I should be able to view reported issues relevant to my location on my dashboard.
• As a User, I should be able to trigger selective re-run capabilities for refreshing specific system functions like dashboards or emergency data.
• As a User, I should be able to access emergency support features such as SOS alerts, medical assistance locators, and road assistance services.

4. User Personas

1. Regular Users

• Description: Residents of the district who use the platform to access local services, report issues, and stay informed about updates.
• Key Features: Personalized dashboard, issue reporting, access to local services.

2. Tourists

• Description: Visitors to the district who use the platform for tourism guidance, emergency support, and issue reporting.
• Key Features: Personalized dashboard, issue reporting, access to tourism information.

3. Local Authorities

• Description: Government officials or representatives responsible for managing district-level services and addressing reported issues.
• Key Features: Dashboard displaying reported issues, tools for managing and resolving issues.

5. Visuals Colors and Theme

The visual identity of OneSpot reflects its focus on tourism, safety, and community engagement. The color palette is designed to evoke trust, warmth, and exploration.

• Background: #F5FAFF (Polar Ice White)
• Surface: #E1EDF7 (Soft Arctic Blue)
• Text: #0D1F33 (Deep Midnight Blue)
• Accent: #FF6F3C (Aurora Orange)
• Muted Tones: #B8D8E8 (Frosted Glacier Blue)

This palette creates a clean, modern, and approachable aesthetic that aligns with the platform's purpose.

6. Signature Design Concept

Interactive Polar Map Dashboard with Emergency Features

The landing page and dashboards will feature an interactive polar map as the central design element. This map will dynamically display key locations, reported issues, and emergency services in real-time.

• Visuals: The map will have a sleek, semi-transparent overlay with glowing markers for attractions, reported issues, and emergency services.
• Animations: Markers will pulse gently to indicate activity, and clicking on a marker will open a detailed pop-up with relevant information.
• Transitions: Smooth zoom-in and zoom-out transitions will allow users to explore the map intuitively.
• Micro-interactions: Hovering over a marker will display a brief tooltip, while clicking will provide detailed information.
• Selective Re-run Capability: Users can refresh specific map layers (e.g., emergency services, reported issues) without reloading the entire map.
• Color Shifts: The map's background will subtly change based on the time of day, transitioning from a bright, sunny theme during the day to a calm, starry theme at night.

This interactive map will serve as the focal point of the platform, offering users an engaging and visually striking way to navigate the system while maintaining high functionality.

7. Non-Functional Requirements

• The system must support a minimum of 10,000 concurrent users.
• The platform should load within 3 seconds on a standard 4G connection.
• Data accuracy must be maintained with a 99.9% reliability rate.
• The system must comply with Indian data protection laws and regulations.
• The platform should be accessible on both web and mobile devices.
• Selective re-run capabilities must execute within 1 second for seamless user experience.

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

AI Tools

• Langchain
• Litellm for LLM Routing

Orchestration

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

9. Assumptions and Constraints

• Users will have access to a stable internet connection to use the platform.
• The system will initially target a single district in India, with potential for expansion.
• Notification functionality for reported issues will be implemented in a future phase.
• Emergency services data will be provided and maintained by local authorities.
• Selective re-run capabilities will be limited to specific system functions (e.g., refreshing dashboards, reloading emergency data).

10. Glossary

• Dashboard: A user interface that provides an overview of key information and tools.
• SOS: An emergency alert feature for requesting immediate assistance.
• Local Authorities: Government officials or representatives responsible for managing district-level services.
• Interactive Polar Map: A dynamic map feature that displays key locations, reported issues, and emergency services.
• Selective Re-run Capability: A feature allowing users to refresh specific system functions without restarting the entire application.
• Micro-interactions: Small, subtle animations or responses to user actions that enhance the user experience.