Repository navigation
UC‐05
| Field | Value |
|---|---|
| Use Case Number: | UC 5 |
| Use Case Name: | Monitor Traffic & System Health |
| Actor(s): | Admin / Museum Staff |
| Maturity: | Completed |
| Summary: | Allows the Admin or Museum Staff to monitor visitor traffic, Audio Guide usage behavior, and system health status through analytical and monitoring dashboards. |
| Basic Course of Events: | 1. Admin/Staff accesses the "Traffic & System Health" feature from the management Dashboard. 2. The system collects analytical data from the Analytics & Logging Module. 3. The system aggregates GPS Telemetry data, Geofence events, and Audio Guide usage statistics. 4. The system displays the visitor traffic Dashboard including: - Number of GPS Proximity triggers. - Visitor density heatmap. - Most accessed POIs. - Audio Guide usage statistics by language. - Average interaction time at each POI. 5. Admin views the traffic data and switches to the "System Health" tab. 6. The system displays the system health Dashboard including: - Telemetry and API latency. - Audio streaming performance. - Storage and caching status. - Database performance. - Status of AI services (Translation, TTS). 7. Admin reviews visitor traffic and system health metrics, evaluates operational status, and determines whether further actions are required. 8. The use case ends. |
| Alternative Paths: |
A1. Filter Analytical Data: 1. Admin selects a specific zone, POI, or time range to view. 2. The system retrieves data based on the applied filters. 3. The system updates the heatmap, charts, and corresponding statistics. 4. Resume at Step 4 of the Basic Course of Events. A2. Export Report: 1. Admin selects "Export Report". 2. Admin chooses CSV or JSON format. 3. The system generates traffic and system statistical reports. 4. The system provides the file for download. 5. Resume at Step 7 of the Basic Course of Events. A3. Real-Time Monitoring: 1. Admin enables the "Live Auto-Refresh" mode. 2. Admin configures the data refresh interval. 3. The system automatically updates the Dashboard in real-time. 4. Returns to Step 4 or Step 6 of the Basic Course of Events. |
| Exception Paths: |
E1. Data Aggregation Timeout: 1. The system fails to process analytical data within the permitted time frame. 2. The system displays data from the most recently saved record. 3. The system displays a notification: "Real-time data is temporarily delayed; displaying cached data." 4. The system continues to retry updating later. E2. Storage Capacity Threshold Exceeded: 1. The system detects that storage usage exceeds the warning level. 2. The system marks the status as WARNING or CRITICAL. 3. The system displays an alert to the Admin. 4. The use case continues. E3. AI Services Degraded or Down: 1. The system detects unstable performance in Translation or TTS services. 2. The system marks the status as DEGRADED or OFFLINE. 3. The system logs the event into the Audit Log and displays an alert to the Admin. 4. The use case continues. |
| Extension Points: | - Automated Alert Dispatch: Triggered to send emails or notifications when visitor density or system errors exceed allowable thresholds. |
| Triggers: | Admin or Museum Staff accesses the "Traffic & System Health" screen. |
| Assumptions: | - Visitors' devices have granted GPS permissions. - The system is actively collecting telemetry from the visitor mobile application. - POIs have been configured with valid Geofences. |
| Preconditions: | - The user is logged in with administrative privileges. - The Analytics & Logging Module is active and recording telemetry data. |
| Postconditions: | - Visitor traffic and system health dashboards are successfully displayed. - Any alerts or anomalies are recorded within the system. - Admin has access to traffic analytics and system health information for operational decision-making. |
