Skip to content

UC‐06

Jump to bottom
Phát Nguyễn edited this page Oct 19, 2026 · 1 revision

Use Case Specification: UC-06

Use Case Diagram1

Document Metadata

Field Content
Use Case ID UC-06
Use Case Name Monitor Traffic & System Health
Primary Actor Admin / Museum Staff (Site Administrator)
Secondary / System Actors Analytics & Logging Module, GPS Telemetry & Geofence Service, Centralized Database
Maturity Focused
Scope Outdoor Smart Audio Guide & GPS Proximity Navigation System
Author(s) @Phatnguyen3003
Date October 2026

Overview

  • Summary: The Admin / Museum Staff monitors real-time and historical visitor traffic across the outdoor heritage site (GPS proximity triggers, open-air heatmaps, multilingual audio guide consumption, dwell times) and assesses infrastructure system health (telemetry ingestion latency, audio cache storage, database query performance, and external AI services).
  • Triggers: Admin / Museum Staff logs into the Admin Portal and accesses the "Traffic & System Health" dashboard.
  • Preconditions:
    1. Actor has authenticated with administrative privileges.
    2. The Analytics & Logging Module is active and receiving telemetry events (GPS proximity detections, audio streaming requests) from visitor mobile PWAs.
  • Postconditions:
    1. Aggregated outdoor traffic metrics, visitor density heatmaps, and system health status indicators are rendered.
    2. Any operational anomalies (e.g., storage capacity thresholds, degraded AI services) are logged into the system audit trail.

Flow of Events

1. Main Event Scenario

Step Actor Action System Response
1 Admin navigates to the "Traffic & System Health" section on the Admin Dashboard. [A1] [A3] —
2 — System issues data aggregation requests to the Analytics & Logging Module for outdoor visitor telemetry.
3 — The Analytics & Logging Module queries the Centralized Database, aggregates GPS proximity events, and compiles visitor flow metrics. [E1]
4 — System renders the default Outdoor Traffic & Visitor Flow Dashboard:
1. GPS Proximity Triggers: Total count of visitors entering geofence trigger zones around POIs over time (hourly / daily trends).
2. Outdoor Map Heatmap & Visitor Density: Visual spatial density map displaying visitor concentration across the map.
3. Top Visited Outdoor POIs: Ranked list of outdoor exhibits with the highest audio playback triggers and average dwell times.
4. Multilingual Audio Distribution: Breakdown of audio guide consumption by language (vi, en, ja, ko, zh).
5. Average Dwell Time: Average duration visitors spend listening to audio within each exhibit's geofence radius.
5 Admin reviews the visitor traffic data and clicks on the "System Health" tab. —
6 — System queries server runtime diagnostics and renders the Infrastructure & System Health Dashboard:
1. Telemetry & API Latency: Response times for GPS coordinate lookups and nearby POI spatial queries.
2. Audio Streaming & Network Delivery: Throughput and error rates for .mp3 audio delivery to visitor devices over cellular networks (4G/5G).
3. Storage & Cache Status: Disk usage of pre-synthesized audio cache (/static/audio) and thumbnails. [E2]
4. Database Performance: SQLite WAL mode connection health and query execution times.
5. External AI Pipelines: Availability and response status of Translation (deep-translator) and TTS (edge-tts) engines. [E3]
7 Admin reviews system health metrics, verifies operational stability, and concludes the monitoring session or chooses an auxiliary action ([A1], [A2], [A3]). Use case ends. —

2. Alternative Paths

A1. Filter Analytics by Outdoor Zone, Specific POI, or Date Range

Step Actor Action System Response
1 Admin applies filters (e.g., selecting a specific outdoor zone, individual POI, or custom date range such as "Last 7 Days"). —
2 — System requests filtered telemetry datasets from the Analytics & Logging Module.
3 — System refreshes the traffic heatmaps, proximity trigger charts, and language distribution graphs without a full page reload. Returns to Step 4 of the Main Event.

A2. Export Traffic & System Health Report

Step Actor Action System Response
1 Admin clicks "Export Report" and selects desired format (CSV or JSON summary). —
2 — System generates the report containing aggregated visitor counts, peak outdoor hours, language demographics, and system uptime logs.
3 — System makes the report file available for download. Returns to Step 7 of the Main Event.

A3. Live Auto-Refresh & Real-Time Monitoring

Step Actor Action System Response
1 Admin toggles on the "Live Auto-Refresh" mode with a configured interval (e.g., 30s or 60s). —
2 — System periodically polls the Analytics & Logging Module and dynamically updates live visitor hotspots and active audio sessions on the outdoor map.

3. Exception Paths

  • E1: Analytics Aggregation Timeout / Query Delay:
    • At Step 3, if processing a massive volume of GPS telemetry logs times out or database write locks cause a delay:
      1. System falls back to rendering cached metrics from the previous snapshot.
      2. System displays a notification banner: "Real-time telemetry delayed. Displaying cached data from [Timestamp]. Auto-retrying..."
      3. System attempts to re-query in the background after 30 seconds.
      4. System proceeds to Step 4 of the Main Event with cached data displayed (Use case continues).
  • E2: Storage Capacity Threshold Exceeded:
    • At Step 6, if the static audio cache directory (/static/audio) or server disk usage exceeds 85% capacity:
      1. System flags the storage health indicator with a warning status (WARNING / CRITICAL).
      2. System triggers an alert on the Admin Dashboard prompting staff to prune orphaned audio files or expand storage quota.
      3. System keeps all dashboard views active and proceeds to Step 7 of the Main Event (Use case does not terminate).
  • E3: External AI Pipeline Degradation:
    • At Step 6, if the Edge-TTS engine or Translation API experiences connection dropouts, high latency, or rate limiting:
      1. System marks the corresponding service badge as DEGRADED or OFFLINE.
      2. System logs the error event into the Audit Log and notifies Admin that background audio generation for new POIs may be temporarily queued.
      3. System keeps all dashboard views active and proceeds to Step 7 of the Main Event (Use case does not terminate).

4. Supplementary Information

Field Content
Extension Points: Automated Alert Dispatch: Optional webhook or email notification when server error rates or visitor crowd density exceeds safety thresholds in outdoor zones.
Triggers: Admin navigates to the Analytics view, or system triggers an automated alert banner upon threshold violation.
Assumptions: Visitor mobile devices grant GPS location permissions; cellular network (4G/5G) coverage is available across the outdoor site; POI geofence coordinates and trigger radii are configured in the database.
Preconditions: Admin has logged into the system; Analytics & Logging Module is running and ingesting GPS telemetry events.
Post Conditions: Metrics and heatmaps are visualized for Admin review; operational events are logged to the audit trail.
Business Rules:

Activity Diagram

Activity Diagram1

Clone this wiki locally