Disaster Response Time

Introduction

The "Disaster Response Time" project aims to enhance emergency response and disaster assistance by providing real-time information and guidance during natural disasters such as floods, earthquakes, cyclones, and accidents. This document outlines the system requirements for the project, focusing on utilizing Git for version control, adding new features, and deploying the project on GitHub.

System Overview

The Disaster Response Time system is designed to assist individuals and emergency responders by providing critical information during disasters. It will help users locate shelters, identify safe roads, access medical help, and determine necessary emergency supplies. The system will be developed using Git for version control and will be deployed on GitHub for accessibility and collaboration.

Functional Requirements

• As a User, I should be able to find the nearest shelters during a disaster.
• As a User, I should be able to identify which roads are safe to travel.
• As a User, I should be able to access information on how to get medical help.
• As a User, I should be able to know what emergency supplies are needed.
• As a Developer, I should be able to use Git for version control to manage the project's codebase.
• As a Developer, I should be able to deploy the project on GitHub for collaboration and accessibility.

User Personas

• General User: Individuals affected by disasters seeking information on shelters, safe roads, medical help, and emergency supplies.
• Emergency Responder: Professionals involved in disaster management and response operations.
• Developer: Individuals responsible for maintaining and enhancing the system using Git and deploying it on GitHub.

Core User Flows

• General User searches for nearby shelters -> System displays available shelters with directions.
• General User checks road safety -> System provides a list of safe and unsafe roads.
• General User seeks medical help -> System lists nearby medical facilities and contact information.
• General User checks for emergency supplies -> System suggests necessary supplies based on the disaster type.
• Developer updates codebase using Git -> Pushes changes to GitHub -> Collaborators review and merge changes.

Visuals Colors and Theme

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

Signature Design Concept

The homepage will feature an interactive disaster map using @react-three/fiber and @react-three/drei. Users can click on different disaster icons (e.g., flood, earthquake) to view real-time data and resources. The map will have a dynamic weather overlay that changes based on the selected disaster type, providing an immersive experience. Hovering over icons will display quick info pop-ups, and clicking will expand detailed information panels.

Interaction Model & Motion Direction

The landing page will use a "parallax" interaction model, with layered depth effects as users scroll through the page. Decorative elements like atmospheric clouds and animated disaster icons will move at different speeds to create a sense of depth. Real content will scroll naturally, providing a visually rich first impression while maintaining usability.

Non-Functional Requirements

• The system must be highly available and reliable, especially during disaster events.
• It should provide real-time updates and information.
• The user interface must be intuitive and accessible to users of all ages and technical abilities.
• The system should support multiple languages to cater to diverse user demographics.

Tech Stack

• Frontend: React for Web
• Backend: Python, FastAPI
• Database: MySQL or MariaDB
• Version Control: Git
• Deployment: GitHub

Assumptions and Constraints

• The system assumes internet connectivity for accessing real-time data.
• It is constrained by the availability of accurate and timely disaster data from external sources.
• The deployment on GitHub assumes compliance with GitHub's terms of service and usage policies.

Glossary

• Git: A distributed version control system for tracking changes in source code.
• GitHub: A platform for hosting and collaborating on Git repositories.
• Parallax: An effect where background images move slower than foreground images, creating an illusion of depth.
• React: A JavaScript library for building user interfaces.
• FastAPI: A modern, fast (high-performance) web framework for building APIs with Python.