System Requirements Document (SRD) for Regal-App

1. Introduction

The Regal-App is an online event booking system designed to streamline ticket sales, reservations, and event management. Developed for users in India, the platform caters to both event organizers and attendees, ensuring a seamless experience for managing and participating in events. This document outlines the system requirements for the Regal-App, incorporating the latest updates requested by Mayur Gole.

2. System Overview

The Regal-App is a dual-purpose platform designed to serve two primary user groups: event organizers and attendees. Event organizers can create, manage, and track events, while attendees can browse, book, and pay for tickets. The system will launch with a minimum of 5-7 events for each category (organizers and attendees), ensuring a diverse range of options to engage users from the outset.

The platform will support:

• Event Organizers: Tools for event creation, ticket management, and analytics dashboards.
• Attendees: Features for event discovery, seat selection, and secure payment integration.

Locale-specific defaults, such as Indian Rupees (INR) for transactions and IST (Indian Standard Time) for scheduling, will be implemented to enhance usability for users in India.

3. Functional Requirements

Event Organizers

• As an Organizer, I should be able to create and manage events.
• As an Organizer, I should be able to track bookings and view analytics through a dashboard.
• As an Organizer, I should be able to set ticket prices and availability.
• As an Organizer, I should be able to upload event-related media (e.g., images, videos).
• As an Organizer, I should be able to manage at least 5-7 events at launch.

Attendees

• As an Attendee, I should be able to browse events by category, location, or date.
• As an Attendee, I should be able to select seats for events (if applicable).
• As an Attendee, I should be able to securely purchase tickets using integrated payment gateways.
• As an Attendee, I should be able to view event details, including descriptions, schedules, and media.
• As an Attendee, I should have access to at least 5-7 events at launch.

4. User Personas

Event Organizer

• Description: Individuals or organizations hosting events, such as concerts, conferences, or workshops.
• Goals: Simplify event management, maximize ticket sales, and gain insights through analytics.
• Pain Points: Difficulty in tracking bookings, limited promotional tools, and lack of real-time data.

Attendee

• Description: Individuals looking to discover and participate in events.
• Goals: Easily find events of interest, book tickets securely, and enjoy a smooth user experience.
• Pain Points: Limited event discovery options, cumbersome booking processes, and lack of seat selection.

5. Visuals Colors and Theme

Unique Color Palette

The Regal-App will feature a vibrant and modern color scheme to evoke excitement and professionalism:

• Background: #F9F9F9 (Soft White)
• Surface: #FFFFFF (Pure White)
• Text: #333333 (Dark Charcoal)
• Accent: #FF6F61 (Coral Red)
• Muted Tones: #B0BEC5 (Cool Gray)

This palette ensures readability and a visually appealing interface while maintaining a professional aesthetic.

6. Signature Design Concept

Interactive Event Map with Dynamic Animations

The homepage of the Regal-App will feature an interactive event map that visually represents all available events. Users will see a dynamic, animated map of India, with event locations marked by glowing, pulsating pins. When a user hovers over a pin, a tooltip card will appear, showing a brief event summary, including the title, date, and a thumbnail image.

Additional features:

• Zoom and Pan: Users can zoom in on specific regions or pan across the map to explore events in different cities.
• Category Filters: A floating toolbar will allow users to filter events by category (e.g., music, workshops, conferences).
• Micro-Interactions: Clicking on a pin will trigger a smooth transition to the event details page, with a fade-in effect for content.

This unique design ensures an engaging first impression and encourages users to explore events visually.

7. Non-Functional Requirements

• The system must support at least 1,000 concurrent users at launch.
• Payment processing must comply with PCI DSS standards for secure transactions.
• The platform should load within 3 seconds on standard broadband connections.
• The system must support both desktop and mobile devices with responsive design.
• Data backups must occur daily to ensure minimal data loss in case of system failure.

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 coding-related queries

AI Tools

• Litellm for LLM Routing
• Langchain

Orchestration

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

9. Assumptions and Constraints

Assumptions

• Users will primarily access the platform from India.
• All events will initially be hosted in Indian cities.
• The platform will support English as the primary language at launch.

Constraints

• The system must comply with Indian data protection laws (e.g., IT Act, 2000).
• Payment gateways must support INR as the default currency.
• The platform must be scalable to accommodate future international expansion.

10. Glossary

• Event Organizer: A user who creates and manages events on the platform.
• Attendee: A user who browses and books tickets for events.
• PCI DSS: Payment Card Industry Data Security Standard, a set of security standards for handling cardholder data.
• IST: Indian Standard Time, the time zone used in India.