How ezekiellazaro/tropadev-it works
Barangay FixTrack lets residents submit facility-damage reports and officials review, filter, update, and monitor them. The principal flow runs from browser forms through the Java HTTP API into report handling and configured storage; dashboards and user-account management are additional capabilities. The README documents photo uploads, search/filtering, status updates, and dashboards, though several corresponding backend classes are not in the supplied tree. Arrows are limited to relationships shown in excerpts or the README; unsampled domain links are omitted.
Main entry points: WebServer.java HTTP API and Static Server · Main.java Application Startup · service Report Handling · LoginManager.java Authentication and Accounts
Components 17
Resident and Official UI
- Web Interface
frontend/app.js - Report Submission
frontend/app.js - Dashboards and Search
frontend/app.js
HTTP Application
- Application Startup
backend/src/barangaydamagereporter/web/Main.java - HTTP API and Static Server
backend/src/barangaydamagereporter/web/WebServer.java - Project Paths
backend/src/barangaydamagereporter/web/AppPaths.java - JSON Encoding
backend/src/barangaydamagereporter/web/Json.java
Identity and Access
- Authentication and Accounts
backend/src/barangaydamagereporter/service/LoginManager.java - User Roles
backend/src/barangaydamagereporter/model/User.java
Report Domain
- Report Operations Contract
backend/src/barangaydamagereporter/interfaces/ReportActions.java - Report Handling
backend/src/barangaydamagereporter/service
Report Storage
- SQLite Report Store
backend/src/barangaydamagereporter/service - Text File Report Store
backend/src/barangaydamagereporter/service - Report Data
backend/src/barangaydamagereporter/service - Uploaded Photos
backend/src/barangaydamagereporter/web/WebServer.java
Other components
- Resident
- Browser
Connections 23
- Resident → Browser: uses
README.md - Browser → Web Interface: loads
README.md - Web Interface → Report Submission: renders
frontend/app.js - Web Interface → Dashboards and Search: renders
frontend/app.js - Report Submission → HTTP API and Static Server: submits JSON
frontend/app.js - Dashboards and Search → HTTP API and Static Server: requests data
frontend/app.js - Application Startup → HTTP API and Static Server: starts
backend/src/barangaydamagereporter/web/Main.java - Application Startup → Authentication and Accounts: creates
backend/src/barangaydamagereporter/web/Main.java - Application Startup → Report Handling: configures
backend/src/barangaydamagereporter/web/Main.java - Application Startup → SQLite Report Store: selects if available
backend/src/barangaydamagereporter/web/Main.java - Application Startup → Text File Report Store: selects fallback
backend/src/barangaydamagereporter/web/Main.java - HTTP API and Static Server → Authentication and Accounts: authenticates
backend/src/barangaydamagereporter/web/WebServer.java - HTTP API and Static Server → Authentication and Accounts: lists and adds accounts
backend/src/barangaydamagereporter/web/WebServer.java - Authentication and Accounts → User Roles: checks credentials
backend/src/barangaydamagereporter/service/LoginManager.java - HTTP API and Static Server → Report Handling: handles report requests
backend/src/barangaydamagereporter/web/WebServer.java - HTTP API and Static Server → Report Handling: builds report data
backend/src/barangaydamagereporter/web/WebServer.java - HTTP API and Static Server → Uploaded Photos: saves uploads
backend/src/barangaydamagereporter/web/WebServer.java - HTTP API and Static Server → JSON Encoding: encodes responses
backend/src/barangaydamagereporter/web/WebServer.java - Application Startup → Project Paths: locates project files
backend/src/barangaydamagereporter/web/Main.java - Report Operations Contract → Report Handling: implemented by
backend/src/barangaydamagereporter/interfaces/ReportActions.java - Report Handling → Report Data: manages
- SQLite Report Store → Report Data: persists
- Text File Report Store → Report Data: persists