Rakshit Dhaba System Requirements Document

1. Introduction

Rakshit Dhaba is an online food delivery application designed to facilitate local vendors in reaching a broader customer base. This document outlines the system requirements necessary to develop and deploy the application effectively.

2. System Overview

Rakshit Dhaba aims to provide a seamless online platform for local food vendors to offer their products to customers. The system will enable users to browse menus, place orders, and receive deliveries efficiently. The application will support both web and mobile interfaces to cater to a wide range of users.

3. Functional Requirements

• As a Customer, I should be able to browse the menu of available food items.
• As a Customer, I should be able to place an order for delivery.
• As a Customer, I should be able to track my order status in real-time.
• As a Vendor, I should be able to manage my menu and update item availability.
• As a Vendor, I should be able to view and manage incoming orders.
• As a Delivery Personnel, I should be able to view assigned deliveries and update delivery status.
• As an Admin, I should be able to manage user accounts and vendor registrations.
• As an Admin, I should be able to generate reports on sales and performance metrics.

4. User Personas

• Customer: Individuals looking to order food online from local vendors.
• Vendor: Local food vendors who wish to offer their menu items through the application.
• Delivery Personnel: Individuals responsible for delivering orders to customers.
• Admin: Personnel responsible for overseeing the application’s operations and user management.

5. Core User Flows

• Customer browses menu -> selects items -> places order -> tracks order -> receives delivery.
• Vendor updates menu -> receives order notification -> prepares order -> hands over to delivery personnel.
• Delivery Personnel receives delivery assignment -> picks up order -> delivers to customer -> updates delivery status.
• Admin manages user accounts -> oversees vendor registrations -> generates sales reports.

6. Visuals Colors and Theme

• primary: #FF5733 (a vibrant orange representing energy and enthusiasm)
• primary_light: #FF8F66 (a lighter tint of the primary color for hover states)
• secondary: #4CAF50 (a fresh green for headlines and emphasis)
• accent: #FFC107 (a bright yellow for call-to-action buttons and badges)
• highlight: #FFEB3B (a warm yellow for notifications and active indicators)
• bg: #FFFFFF (a clean white background for clarity)
• surface: rgba(255, 255, 255, 0.9) (a semi-transparent white for cards and panels)
• text: #212121 (a dark gray for primary text)
• text_muted: #757575 (a softer gray for secondary text and labels)
• border: rgba(0, 0, 0, 0.1) (a subtle border color)

7. Signature Design Concept

The Rakshit Dhaba homepage will feature an interactive "Food Journey Map" where users can explore different local cuisines. As users scroll, they will navigate through a vibrant, animated map that highlights various food items and vendor locations. Each stop on the map will pop up with a brief description and an option to view the full menu. This engaging experience will be powered by framer-motion for smooth animations and gsap for scroll-triggered effects, creating an immersive journey through the culinary offerings of Rakshit Dhaba.

8. Interaction Model & Motion Direction

The landing page will employ a "parallax" interaction model, providing a layered depth effect as users scroll through the content. Decorative elements like food icons and vendor logos will move at different speeds to create a dynamic visual experience. Internal pages such as the dashboard and order management will use a "static" interaction model to prioritize clarity and ease of use.

9. Non-Functional Requirements

• The application must support high concurrency to handle multiple users simultaneously.
• The system should ensure data security and user privacy.
• The application should be responsive and accessible on both web and mobile platforms.
• The system should provide reliable uptime and quick recovery from failures.

10. Tech Stack

• Frontend: React for Web, React Native for mobile app
• Backend: Python, FastAPI
• Database: MySQL or MariaDB, using Alembic for migrations
• Local Orchestration: Docker, docker-compose
• Server-side Orchestration: Kubernetes

11. Assumptions and Constraints

• The application will initially target users in India, considering local currency (INR) and timezone (IST).
• The system will comply with local regulations and standards for online transactions and data protection.
• The application will be scalable to accommodate future growth in user base and vendor participation.

12. Glossary

• Customer: End-user placing orders through the application.
• Vendor: Local food business offering products on the platform.
• Delivery Personnel: Individuals responsible for delivering orders.
• Admin: System administrator managing the application and user accounts.
• Parallax: A visual effect where background images move slower than foreground images, creating a sense of depth.
• Framer-motion: A library for creating animations in React applications.
• GSAP: A JavaScript library for creating high-performance animations.