System Requirements Document (SRD)

Project Name: hollow-cabs

1. Introduction

Welcome to the System Requirements Document (SRD) for hollow-cabs, an innovative intercity ride-sharing platform envisioned by Ujjwal Jain. This document outlines the requirements and specifications for building a web-based platform that allows users to book individual seats in shared cabs, with flexible routes, timings, and real-time driver assignment.

The platform is designed to cater to the Indian market, ensuring locale-specific defaults such as INR currency, IST timezone, and culturally relevant user experiences. With a focus on instant bookings and seamless user interactions, hollow-cabs aims to redefine intercity travel convenience.

2. System Overview

hollow-cabs is a web-first intercity ride-sharing platform that enables users to book individual seats in 7-seater vehicles (Ertiga model: 1 driver + 6 passengers). The system supports:

• Seat-specific pricing to maximize flexibility and affordability.
• Multiple pickup and drop-off points within and across cities, with a hop-on/hop-off system for intercity routes.
• Flexible timing options to accommodate diverse schedules.
• Real-time driver assignment and management via a dedicated driver app.
• A robust backend system (GDS) to manage trips, pricing, routes, and services efficiently.

The platform prioritizes instant bookings to ensure a seamless and fast user experience.

3. Functional Requirements

User Stories:

• As a User, I should be able to book a single seat based on my preference, with seat-specific pricing.
• As a User, I should be able to view and select routes with multiple pickup and drop-off points, including intercity hop-on/hop-off options.
• As a User, I should be able to choose from different timing options for my trip.
• As a Driver, I should be able to receive real-time trip assignments via a dedicated driver app.
• As an Admin, I should be able to manage trips, pricing, services, routes, and driver assignments through a backend system (GDS).

4. User Personas

1. User (Passenger)

• Description: Individuals looking for affordable and flexible intercity travel options.
• Goals: Book seats in shared cabs, choose routes and timings, and enjoy seamless travel.
• Pain Points: High costs of private cabs, lack of flexible routes, and inconvenient booking systems.

2. Driver

• Description: Professional drivers responsible for operating the shared cabs.
• Goals: Receive real-time trip assignments, manage routes, and ensure passenger satisfaction.
• Pain Points: Inefficient trip management and lack of clarity in assignments.

3. Admin

• Description: Platform operators managing backend systems and overall operations.
• Goals: Oversee trip management, pricing, services, routes, and driver assignments.
• Pain Points: Complexity in managing dynamic pricing and route configurations.

5. Visuals Colors and Theme

Color Palette:

The visual identity of hollow-cabs will reflect a modern, professional, and approachable aesthetic, emphasizing trust and convenience.

• Background: #F3F4F6 (Soft Gray)
• Surface: #FFFFFF (Pure White)
• Text: #333333 (Deep Charcoal)
• Accent: #0078D7 (Vivid Blue)
• Muted Tones: #A0AEC0 (Neutral Blue-Gray)

6. Signature Design Concept

Concept: Interactive Route Map with Dynamic Seat Selection

The homepage of hollow-cabs will feature an interactive route map that visually displays all available routes, pickup/drop-off points, and timings. Users can hover over cities to see detailed route information and dynamically select their preferred seat in the cab.

Key Features:

1. Dynamic Seat Visualization:

   • A 3D model of the cab interior will appear when users select a route.
   • Users can click on individual seats to view pricing and availability.

2. Animated Route Map:

   • Routes will be displayed as animated lines connecting cities, with glowing markers for pickup/drop-off points.
   • Clicking on a marker will reveal detailed timing options and seat availability.

3. Micro-Interactions:

   • Smooth transitions between route selection, seat booking, and payment.
   • Subtle animations for hover effects and real-time updates on seat availability.

This bold and interactive design will make the booking process engaging and memorable, ensuring users feel in control of their travel plans.

7. Non-Functional Requirements

• Performance: The system must support up to 10,000 concurrent users during peak hours.
• Scalability: The backend must be scalable to accommodate future expansion to additional cities and routes.
• Security: Implement SSL encryption and secure payment gateways to protect user data.
• Availability: Ensure 99.9% uptime for the web platform.
• Localization: Support INR currency and IST timezone by default.

8. Tech Stack

Frontend:

• React for Web

Backend:

• Python
• FastAPI

Database:

• MySQL (with 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:

• Users will primarily access the platform via web browsers.
• Instant bookings will be the default mode of operation.
• Drivers will have access to smartphones for using the driver app.

Constraints:

• The platform will initially support only intercity routes within India.
• The system must comply with local regulations for ride-sharing services.

10. Glossary

• GDS: Global Distribution System, a backend system for managing trips, pricing, routes, and services.
• IST: Indian Standard Time, the timezone used for scheduling trips.
• SSL: Secure Sockets Layer, a protocol for encrypting data during transmission.
• Micro-Interactions: Small, subtle animations or feedback mechanisms that enhance user experience.