Scenario
A junior engineer modeled an Air Traffic Control system with 5 serious UML violations: (1) Tower Supervisor should specialize Air Traffic Controller, not the reverse; (2) Radar Sensor is an Actor and cannot have an «include» relationship with Track Aircraft; (3) Log Flight Telemetry is mandatory for Track Aircraft, not an optional «extend»; (4) Issue Storm Reroute optionally extends Track Aircraft, so its arrow direction is backwards; and (5) Authorize Emergency Landing must «include» Clear Runway, not the other way around.
Objective
Find and fix all 5 broken relationships while preserving the valid Associations (Controller -> Track Aircraft, Tower Supervisor -> Authorize Emergency Landing, Weather Feed -> Issue Storm Reroute).