How dulalsaurab/flash-flood-early-warning-systme-ffews works
Project Type and Purpose
• It ingests hydrological and satellite forecast data, stores it in a MySQL database, processes it (inundation modeling, digital terrain analysis via ArcGIS Java Beans), visualizes results (desktop Swing UI + web pages with D3.js/Bootstrap), and issues warnings (SMS).
File‐Structure Analysis
• MajorProject/src/majorproject: core Java packages (data ingestion, GIS integration via ArcGIS, charting via JFreeChart, UI forms, SMS notification).
• MajorProject/res/src and MajorProject/WebStuffs: static assets (HTML, CSS, JavaScript, D3.js, Bootstrap, LESS) for web‐based visualization.
• MajorProject/dist: packaged JAR and dependent libraries (mysql-connector, jfreechart, swt, arcobjects.jar).
• build & nbproject: NetBeans build scripts and metadata.
• Docs: thesis, proposal, final presentation – reference materials, not part of runtime.
Key Architecture Components
a. Data Sources (External)
• Hydrological sensors, satellite forecast APIs, digital terrain datasets.
b. Data Storage
• MySQL database accessed via DatabaseConnection.java.
c. Application Core
• Ingestion & Scheduling (NewThread.java)
• Business Logic & Modeling (Inundation model code, MapTest.java, BeanFactory.java)
• GIS Engine (ArcGIS.java, UseGlobeBean.java, AddLayerFileToMap.java)
• Charting & Reports (MyChartFactory.java, JFreeChart integration in LineChart.java, GraphsTab.java)
• Notification Service (SendSms.java)
d. Presentation/UI
• Desktop Swing UI (VisualizationFrame.java, VisualFrame.java, ParameterBrowse.java, GoogleMap.java forms)
• Web UI (static HTML + D3.js charts, Bootstrap CSS/LESS under res/src and WebStuffs)
e. External Services
• SMS gateway/provider
• 3rd-party map/tile servers (if any)
Relationships & Data Flows
• Data Sources → (pull/receive) → Application Core → (persist) → MySQL
• Application Core → (query/process) → GIS Engine → (map output) → UI layers
• Application Core → (query/process) → Charting module → Desktop UI & Web UI
• Application Core → (trigger) → Notification Service → SMS gateway → End Users
• Web UI assets served from the packaged JAR or a simple HTTP server
Architectural Patterns & Design Principles
• Layered Architecture: Data Access layer, Business/Model layer, Presentation layer, Integration/Notification layer.
• Modularization by feature: GIS module, Charting module, Notification module.
• Use of Factory pattern (BeanFactory, MyChartFactory) for pluggable components.
Technologies & Frameworks
• Java SE 8+, Swing, SWT (via swtgraphics2d.jar)
• ArcGIS Java Beans (arcobjects.jar)
• JFreeChart & OrsonCharts for charting
• MySQL + JDBC (mysql-connector-java)
• Bootstrap + D3.js for web visualization
• SMS API (via SendSms.java)