DQRM System Requirements Document

Introduction

The DQRM project aims to develop an application for restaurants to create and manage menus, allowing customers to order via a QR code. This system will support multi-tenancy and cater to various user types, including customers, waiters, kitchen staff, service desk personnel, and delivery drivers. The application will enable restaurants to create custom menus optimized for multiple screen sizes and quickly update item availability and prices.

System Overview

The DQRM system is designed to streamline the restaurant ordering process by providing a digital platform for menu management and customer ordering. Restaurants can create and manage their menus, which customers can access via QR codes at their tables. The system supports multiple user roles, ensuring efficient communication and order processing from the customer to the kitchen and delivery.

Functional Requirements

• As a Restaurant Owner, I should be able to create and manage custom menus optimized for smartphones, tablets, and monitors.
• As a Restaurant Owner, I should be able to quickly update item availability and prices on the menu.
• As a Customer, I should be able to scan a QR code at my table to view the restaurant's menu.
• As a Customer, I should be able to place an order directly from the menu on my device.
• As a Waiter, I should be able to view and manage customer orders.
• As a Kitchen Staff, I should be able to receive and prepare orders placed by customers.
• As a Service Desk Personnel, I should be able to oversee the order process and handle any issues.
• As a Delivery Driver, I should be able to receive delivery orders and update their status.

User Personas

• Restaurant Owner: Manages the restaurant's menu and pricing, oversees operations.
• Customer: Scans QR codes to view menus and place orders.
• Waiter: Manages customer orders and assists with service.
• Kitchen Staff: Prepares food based on customer orders.
• Service Desk Personnel: Oversees order processing and resolves issues.
• Delivery Driver: Delivers orders to customers and updates delivery status.

Core User Flows

• Customer scans QR code -> views menu on device -> places order -> order is sent to kitchen -> kitchen prepares order -> waiter serves order.
• Restaurant Owner updates menu -> changes reflect on all devices -> customers see updated menu.
• Delivery Driver receives order -> picks up from restaurant -> delivers to customer -> updates delivery status.

Visuals Colors and Theme

• primary: #2A9D8F (deep teal)
• primary_light: #A8DADC (light teal)
• secondary: #E76F51 (coral)
• accent: #F4A261 (sandy orange)
• highlight: #E9C46A (golden yellow)
• bg: #F1FAEE (off-white)
• surface: rgba(255, 255, 255, 0.8)
• text: #264653 (dark slate)
• text_muted: #6D6875 (muted gray)
• border: rgba(38, 70, 83, 0.2)

Signature Design Concept

The DQRM application will feature an interactive "Menu Canvas" on the homepage. This canvas will allow users to drag and drop menu items to customize their view, with animations that mimic the flipping of a physical menu. Using framer-motion for smooth transitions, users can hover over items to see detailed descriptions and images. The canvas will adapt to different screen sizes, ensuring a seamless experience on smartphones, tablets, and monitors.

Interaction Model & Motion Direction

The landing page will utilize a "parallax" interaction model, with layered depth effects as users scroll through the menu. Decorative elements will move at varying speeds to create a dynamic visual experience, while the main content remains easily accessible. Internal pages, such as the dashboard and settings, will follow a "static" model for clarity and ease of use.

Non-Functional Requirements

• The system must support multi-tenancy to allow multiple restaurants to use the platform independently.
• The application should be responsive and function seamlessly across different devices and screen sizes.
• The system should ensure data security and privacy for all users.

Tech Stack

• Frontend: React for Web
• Backend: Python, FastAPI
• Database: MySQL or MariaDB, with alembic for migrations
• AI Tools: Not specified
• Local Orchestration: Docker, docker-compose
• Server-side Orchestration: Kubernetes

Assumptions and Constraints

• The application will be deployed in the UK and should comply with local data protection regulations.
• The system should be scalable to accommodate a growing number of restaurants and users.
• Internet connectivity is required for accessing the application and its features.

Glossary

• QR Code: A machine-readable code used for accessing digital content.
• Multi-Tenancy: A software architecture where a single instance serves multiple tenants.
• Responsive Design: An approach to web design that makes web pages render well on various devices and screen sizes.