Activity 1 · Architecture

System Architecture
Design Overview

Complete technical architecture of the Barangay Baligatan Incident Reporting System — built for clarity, security, and scale.

System Architecture Diagram

System Architecture Diagram
Click diagram to expand · full size

Figure 1.1: Complete system architecture — presentation, application, and data layers with authentication flow, external integrations, and real-time notification pipeline.

Three-Tier Architecture

Presentation (UI), Application (PHP business logic), Data (MySQL) — modular, maintainable, and clearly separated.

Security Architecture

bcrypt hashing, PDO prepared statements, CSRF tokens, XSS sanitization, session hardening, and input validation.

Notification Architecture

Database-driven queue, in-app alerts, email for critical updates, and push notification support for incident status changes.

Technical Components & Data Flow

Frontend Stack

HTML5, CSS3, JavaScript, Bootstrap 5, AOS, Font Awesome — fully responsive, accessible, and optimized for all devices.

Backend Stack

PHP 7.4+ (OOP, PDO), session-based auth, RESTful routing, service layer separation, and error handling.

Database Design

MySQL with normalized schema: users, incidents, categories, responses, announcements, activity logs, notification queues.

Data Flow

User input → validation → business logic → database → response rendering → client feedback with real-time status updates.

Architecture Note: MVC-inspired pattern with role-based access (Public, Resident, Official, Admin). The diagram above (Figure 1.1) visualizes all interconnected components.