use case
Purpose: This document defines the functional and use case specifications for the Helicentral Flight Management Platform.
Scope: This specification covers the operational cycle of helicopter flight management including scheduling, base operations, traffic coordination, delay management, auditing, and dashboard analytics.
References: Internal system architecture and development guidelines.
Revision History: Version 1.0 – Initial Detailed Specification.
Helicentral is a modular flight management platform designed for helicopter operations. Built using Blazor WebAssembly for the frontend and ASP.NET 9 Web API for backend services, the system centralizes all flight data and allows role-based collaboration among operations staff, ground teams, and management.
Actors: Scheduler / Dispatcher
Preconditions: User authenticated with scheduling rights.
Trigger: User navigates to the Scheduling page.
Main Flow:
1. Select base(s) and date.
2. View Scheduled and Departed flights.
3. Add or edit flight details: NNumber, Call Sign, Model, Take-off Time.
4. Validate and save.
Alternative Flows: Permission denied, invalid data.
Postconditions: Flight visible to Base Admin and Traffic Coordinator modules.
Technical: POST /api/flights, GET /api/flights?base=ID&date=YYYY-MM-DD
Actors: Base Administrator, Ground Staff
Preconditions: Flight scheduled.
Trigger: User opens Base Admin page.
Main Flow:
1. Select base(s) and date.
2. View flights as cards.
3. Update cargo/fuel details and complete operational checks.
4. System records timestamps for each check.
5. When all checks complete → flight marked Ready for Traffic Review.
Alternative Flows: Missing check prevents readiness.
Technical: PATCH /api/flights/{id}/checks
Actors: Traffic Coordinator
Preconditions: All base checks complete.
Main Flow:
1. Review checklist timestamps.
2. Perform traffic checks.
3. Enable Take-Off when all verified.
4. Mark flight Departed.
Technical: POST /api/flights/{id}/depart
Actors: Manager / KPI Analyst
Preconditions: Flight delayed (>50 min) or cancelled.
Main Flow:
1. Tabs: Uncategorized, Pending, Confirmed.
2. Assign Delay Code, Type, and Comments.
3. Submit for approval.
4. Manager approves/rejects.
Alternative Flows: Rejected flights can be resubmitted.
Technical: PATCH /api/delays/{id}
Actors: System (Audit Service)
Trigger: Any CRUD operation.
Main Flow:
1. Record UserID, Timestamp, FlightID, ActionType.
2. Display highlights for changed fields.
Technical: Stored in AuditLog table linked to FlightID.
Actors: All Users
Preconditions: User has base access.
Main Flow:
1. Select base(s).
2. System displays:
– Weather widget per base.
– Client summary with Scheduled/VIP/Passenger counts.
– Canceled/Delayed flight KPIs.
3. Drill down for details.
Alternative Flows: No base selected → placeholder message.
Technical: GET /api/dashboard?baseIds=[]
Actors: All Users
Main Flow:
1. Fetch real-time data from external weather API.
2. Display temperature, wind, and warnings.
Technical: /api/weather integrated via backend cache.
Actors: Managers, Analysts
Main Flow:
1. Aggregate flights by client.
2. Display totals for Scheduled, VIP, Passengers.
Technical: GET /api/clients/stats?base=ID
Actors: Managers, KPI Analysts
Main Flow:
1. Retrieve delay/cancellation metrics.
2. Visualize trends and KPIs.
Technical: GET /api/delays/stats
Helicentral integrates all aspects of helicopter operations into one comprehensive system.
Its modular architecture supports seamless scheduling, operational checks, delay management, auditing, and analytical dashboards.
The specification herein ensures technical consistency, scalability, and operational efficiency across all flight activities.
