How en765/disastermaster works
Main Components
a) Frontend Layer (React.js):
• User Interface Components
• Authentication Module
• Disaster Reporting Interface
• Notification Center
• Resource Information Display
• Integration (OpenStreetMap)
b) Backend Layer (Spring Boot):
• REST API Controllers
• Authentication Service (OAuth 2.0)
• Disaster Management Service
• Notification Service (Twilio)
• Report Generation Service
• Resource Management Service
c) Database Layer:
• User Data Store
• Disaster Reports Storage
• Resource Information Storage
d) External Services:
• Twilio (for notifications)
• OpenStreetMap Integration
• OAuth 2.0 Provider
Component Relationships
• Frontend → Backend (REST API calls)
• Backend → Database (data persistence)
• Backend → External Services (third-party integrations)
• Backend → Notification Service (email notifications)
User Role Flows
Separate flows for different user types:
• Regular Users (disaster reporting, resource viewing)
• Authorities (report management, status updates)
• Humanitarian Organizations (resource management)
Key Architectural Patterns to Highlight
• Client-Server Architecture
• RESTful API Design
• Microservices-like separation of concerns
• Event-driven notification system
Additional Details
Annotations for:
• Security layers (OAuth 2.0)
• Data flow directions
• API endpoints
• Service boundaries