DREAM(project) System Requirements Document

1. Introduction

The DREAM(project) aims to develop a comprehensive software solution that interfaces with various car sensors to analyze and report on the condition and functionality of car parts. This application will be accessible to both users and mechanics, providing detailed insights into the car's performance and maintenance needs. Additionally, the application will include a car parts shopping section that connects directly to the respective car company.

2. System Overview

The DREAM(project) will integrate with multiple car sensors to monitor and report on the vehicle's condition. The application will provide real-time data on fuel percentage, tire pressure, engine status, and overall functionality of car parts. It will feature an interactive 3D 360-degree realistic car model with per-part damage percentage overlays. The system will allow for additional sensor integration for overall damage assessment with replacement suggestions. It will also offer a shopping section for car parts with prices in Indian Rupees. The system will be designed to allow for the addition of new features as needed.

3. Functional Requirements

• As a User, I should be able to access real-time data from the Crankshaft Position Sensor.
• As a User, I should be able to access real-time data from the Camshaft Position Sensor.
• As a User, I should be able to access real-time data from the Throttle Position Sensor.
• As a User, I should be able to access real-time analysis of car part conditions and functionality status.
• As a User, I should be able to access real-time data from the Mass Air Flow (MAF) Sensor.
• As a User, I should be able to access real-time data from the Manifold Absolute Pressure (MAP) Sensor.
• As a User, I should be able to access real-time data from the Intake Air Temperature (IAT) Sensor.
• As a User, I should be able to access real-time data from the Coolant Temperature Sensor.
• As a User, I should be able to access real-time data from the Fuel Temperature Sensor.
• As a User, I should be able to access real-time data from the Oxygen (O2) Sensor.
• As a User, I should be able to access real-time data from the NOx Sensor.
• As a User, I should be able to access real-time data from the Oil Pressure Sensor.
• As a User, I should be able to view the car's fuel percentage.
• As a User, I should be able to view the car's tire pressure.
• As a User, I should be able to view an interactive 3D 360-degree realistic car model with per-part damage percentage overlays.
• As a User, I should be able to view the engine status.
• As a User, I should be able to check if all car parts are functioning well.
• As a User, I should be able to view the condition and damage status of each part before and after an accident in percentage and 3D model format.
• As a User, I should be able to receive suggestions on which parts are more damaged and need replacement based on overall car damage percentage.
• As a User, I should be able to see prices in the shopping section in rupees.
• As a User, I should be able to view the condition and damage status of each part in percentage and 3D model format.
• As a User, I should be able to access a car parts shopping section that connects directly to the car company.
• As a User, I should be able to integrate additional sensors for overall damage assessment with replacement suggestions.

4. User Personas

• User: A car owner who wants to monitor the condition and performance of their vehicle.
• Mechanic: A professional who requires detailed diagnostic information to service and repair vehicles.

5. Core User Flows

• User accesses the app -> selects a sensor -> views real-time data and condition.
• User checks overall car status -> views fuel percentage, tire pressure, engine status.
• User navigates to the parts shopping section -> selects a part -> connects to the car company for purchase.
• Mechanic accesses the app -> selects a sensor -> views diagnostic data -> performs maintenance.

6. Visuals Colors and Theme

• primary: #1E3A8A (Deep Blue)
• primary_light: #3B82F6 (Sky Blue)
• secondary: #F97316 (Vibrant Orange)
• accent: #10B981 (Emerald Green)
• highlight: #F59E0B (Amber)
• bg: #F3F4F6 (Light Gray)
• surface: rgba(255, 255, 255, 0.8)
• text: #111827 (Dark Gray)
• text_muted: #6B7280 (Muted Gray)
• border: rgba(209, 213, 219, 0.2)

7. Signature Design Concept

The DREAM(project) homepage will feature an interactive 3D car model that users can rotate and zoom into. Each part of the car will be clickable, providing detailed information about its condition and functionality. The 3D model will update in real-time to reflect the current status of the car's components. This immersive experience will be powered by @react-three/fiber and @react-three/drei, allowing users to explore their vehicle in a virtual environment. The interface will include smooth transitions and animations using framer-motion to enhance user interaction.

8. Interaction Model & Motion Direction

The landing page will utilize a "parallax" interaction model, creating a layered depth effect as users scroll through the content. This will be complemented by animated transitions and hover effects to provide a dynamic and engaging user experience. Internal pages will adopt a "static" model for clarity and ease of navigation.

9. Non-Functional Requirements

• The system must provide real-time data updates with minimal latency.
• The application should be accessible on both web and mobile platforms.
• The user interface must be intuitive and easy to navigate.
• The system should be scalable to accommodate additional features in the future.

10. Tech Stack

• Frontend: React for Web, React Native for mobile app
• Backend: Python, FastAPI
• Database: MySQL or MariaDB
• AI Models: Not specified
• AI Tools: Not specified
• Local Orchestration: Docker, docker-compose
• Server Side Orchestration: Kubernetes

11. Assumptions and Constraints

• The application will initially support a limited set of car models and sensors.
• Additional features can be added later as needed.
• The system will rely on existing sensor data; no new hardware development is required.

12. Glossary

• Sensor: A device that detects or measures a physical property and records, indicates, or otherwise responds to it.
• 3D Model: A digital representation of a physical object in three dimensions.
• Parallax: An effect where the position or direction of an object appears to differ when viewed from different positions.
• Interactive: Allowing a two-way flow of information between a computer and a computer-user; responding to a user's input.