,idx,requirement,label,conflict
0,17,The _GCS_ shall transmit the UAV's past location to the _GCSMiddleware_.,Yes,Yes(16)
1,39,The _UAVActivationManager_ shall only activate UAVs that are registered.,No,No
2,1,"When requested, the _VehicleCore_ shall transition the UAV between states according to allowed state transitions as depicted in the UAV state transition diagram.",No,No
3,26,The _UIMiddleware_ shall accept and activate a mission plan upon request.,Yes,Yes(25)
4,21,The _UIMiddleware_ shall provide an interface for registering UI clients.,No,No
5,31,The _RouteCreationUI_ shall allow the user to create and modify a route.,No,No
6,2,The _VehicleCore_ shall assign a unique ID to each activated UAV.,Yes,Yes(3)
7,36,The _UAVActivationManager_ shall ensure that only one instance of each registered drone is active at any time.,No,No
8,9,The _VehicleCore_ shall support virtual UAVs.,Yes,Yes(10)
9,16,The _GCS_ shall transmit the UAV's current location to the _GCSMiddleware_.,Yes,Yes(17)
10,8,The _VehicleCore_ shall support UAVs connected via the _GCS_.,No,No
11,4,The _VehicleCore_ shall associate a UAV_TYPE for each UAV defining UAV's basic attributes.,No,No
12,7,"When a _GCS_ requests activation of a newly detected UAV, the _GCSMiddleware_ shall forward the request to Dronology.",Yes,Yes(6)
13,15,The _GCS_ shall report newly connected UAVs to the _GCSMiddleware_.,No,No
14,11,The _UAVRegistrationManager_ shall store UAV meta-data information such as the UAV's technical characteristics.,No,No
15,3,The _VehicleCore_ shall assign an ID to each activated UAV.,Yes,Yes(2)
16,33,"When the _RouteCreationUI_ is loaded, a list of all existing routes shall be displayed.",No,No
17,25,The _UIMiddleware_ shall accept and activate a mission plan automatically,Yes,Yes(26)
18,40,"If a route contains a specific UAV_ID, the _SingleUAVFlightPlanScheduler_ shall assign the route to the given UAV.",No,No
19,19,"If a client registers for notifications, the _UIMiddleware_ shall send notifications for specific events.",Yes,Yes(20)
20,14,The _GCS_ shall assign a message frequency for all UAVs.,No,No
21,12,The _InternalSimulator_ shall approximate the behavior of a UAV.,No,No
22,24,The _UIMiddleware_ shall accept commands from UIs and forwards to Dronology.,No,No
23,43,"When a UAV's current flight is cancelled, the _SingleUAVFlightPlanScheduler_ shall in turn cancel all scheduled flight plans for that UAV.",No,No
24,37,The _UIMiddleware_ shall assign one control-client at a time for each UAV.,No,No
25,32,The _RouteCreationUI_ shall allow a user to delete a route.,No,No
26,30,"When requested, the _RouteCreationUI_ shall send a newly created or modified route to dronology.",No,No
27,27,The _RouteCreationUI_ shall distinguish between starting ending and intermediate waypoint markers.,No,No
28,23,The _UIMiddleware_ shall provide a list of all existing routes.,No,No
29,20,"If a client registers for notifications, the _UIMiddleware_ shall send notifications for all events.",Yes,Yes(19)
30,6,"When a _GCS_ requests activation of a newly detected UAV, the _GCSMiddleware_ shall forward the request to Dronology.",Yes,Yes(7)
31,22,"When requested, the _SingleUAVFlightPlanScheduler_ shall schedule a route for execution.",No,No
32,41,The _RouteCreationUI_ shall only accept valid altitude and speed values for waypoint.,No,No
33,10,The _VehicleCore_ shall support up to three virtual UAVs.,Yes,Yes(9)
34,42,"If requested, the _SingleUAVFlightPlanScheduler_ shall unassign the flight plan assigned to a UAV that is awaiting execution.",No,No
35,38,The _ObjectAvoidance_ system shall only issue commands within the capabilities of the UAV.,No,No
36,13,"When the _GCS_ receives a UAV command from the _GCSMiddleware_, the _GCS_ shall forward the command to the respective UAV.",No,No
37,5,"If a command is issued by the _VaadinUI_ for an UAV, the _VaadinUI_ shall request control of that UAV.",No,No
38,18,The _GCS_ shall transmit the UAV's properties to the _GCSMiddleware_.,No,No