,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 39,89,The _InternalSimulator_ shall provide the exact state of the battery.,Yes,Yes(88) 40,88,The _InternalSimulator_ shall approximate the state of the battery.,Yes,Yes(89) 41,83,"When given a goto command, the _InternalSimulator_ shall update the location of the UAV at increments of SIMULATION_STEP_SIZE meters moving the UAV towards the target destination until the destination is reached.",No,No 42,100,The _MapComponent_ shall support same types of map layers.,Yes,Yes(99) 43,81,A flight pattern shall document the longitude latitude and altitude of waypoints in a flight route as offsets from the starting position of the UAV.,No,No 44,105,The _MissionPlanner_ shall manage predefined FlightPatterns.,No,No 45,87,"When given two coordinates, the _CoordinateSystem_ shall compute the direction from the first coordinate to the second coordinate.",Yes,Yes(86) 46,84,"When given a landing command, the _InternalSimulator_ shall move the UAV to the ground altitude corresponding to UAV's current longitude and latitude.",No,No 47,85,"When requested, the _CoordinateSystem_ shall transform coordinates to alternate formats.",No,No 48,93,"When a new monitoring message is received, the _DronologyRuntimeMonitor_ shall forward the message to all subscribed clients.",No,No 49,110,The _UIMiddleware_ shall enable an existing route to be assigned to an active UAV.,No,No 50,116,The _MissionPlanner_ shall execute flight plans for multiple UAVs independently.,Yes,Yes(115) 51,98,The _GCSMiddleware_ shall forward commands sent from Dronology to a _GCS_.,No,No 52,97,The _GCSMiddleware_ shall handle state messages monitoring messages and mode change messages received from an _GCS_.,No,No 53,108,The _UIMiddleware_ shall provide a list of all active UAVs.,No,No 54,86,"When given two coordinates, the _CoordinateSystem_ shall compute the distance from the first coordinate to the second coordinate.",Yes,Yes(87) 55,95,The _GCSMiddleware_ shall handle multiple _GCS_.,No,No 56,90,The _ActivityLogger_ shall log all commands sent to and messages received from a _CGS_.,No,No 57,102,The _FlightRouteManager_ shall define flight routes as an ordered sequence of waypoints in which the first waypoint represents the first target location and the final waypoint represents the final target location.,No,No 58,111,The _RouteAssignmentUI_ shall provide means to select an existing routes and assign them to a UAV.,Yes,Yes(112) 59,114,"When a UAV is selected, the _RouteAssignmentUI_ shall display UAV's active flight plans.",No,No 60,91,"When the _VaadinUI_ is activated, the _VaadinUI_ shall be configured according to stored configuration parameters.",No,No 61,101,The _SingleUAVFlightPlanScheduler_ shall maintain a managed list of pending flight plans for Each UAV.,No,No 62,79,"When a flight plan is activated for a UAV currently in the air, the _FlightSchedulingandExecution_ shall notify the UAV to takeoff vertically until UAV reaches the prescribed altitude.",Yes,Yes(78) 63,106,"When a group of UAVs are assigned flight patterns as part of a mission, the system shall provide a warning if any paths overlap.",No,No 64,82,"When given a takeoff command, the _InternalSimulator_ shall move the UAV to the takeoff altitude corresponding to UAV's current longitude and latitude.",No,No 65,104,The _FlightRouteManager_ shall persist flight routes.,No,No 66,115,The _MissionPlanner_ shall execute flight plans for multiple UAVs concurrently.,Yes,Yes(116) 67,109,The _UIMiddleware_ shall enable the creation and modification of flight routes.,No,No 68,113,"When requested by the user, the _RouteAssignmentUI_ shall display details about the selected UAV and UAV's flight plans.",No,No 69,99,The _MapComponent_ shall support different types of map layers.,Yes,Yes(100) 70,107,The _ActivityLogger_ shall log all flight plan related events.,No,No 71,94,The _DronologyRuntimeMonitor_ shall be able to receive messages from any Dronology component.,No,No 72,78,"When a flight plan is activated for a UAV currently on the ground, the _FlightSchedulingandExecution_ shall notify the UAV to takeoff vertically until UAV reaches the prescribed altitude.",Yes,Yes(79) 73,103,The _FlightRouteManager_ shall ensure that all flight routes represent a VALID_FLIGHT_ROUTE.,No,No 74,92,The _DronologyRuntimeMonitor_ shall provide functionality to retrieve monitoring messages and distribute them to clients.,No,No 75,96,The _GCSMiddleware_ shall follow a predefined set of steps to establish a connection between a _GCS_ and Dronology.,No,No 76,112,The _RouteAssignmentUI_ shall provide means to select an existing routes and assign them to multiple UAV.,Yes,Yes(111)