We invite you to participate in our user study to evaluate the utility of recommended missing requirement concepts in the UAV (Unmanned Aerial Vehicle) domain.
- You will receive a complete document containing a set of UAV requirements, including 70% of the requirements.
- We have already removed 30% of the requirements, which are considered as missing requirements for a system.
- Your task is to:
- First, reading the 70% of the requirements to understand the context and background of the UAV domain.
- For each recommended missing requirement concept, rate it to indicate whether the concept would be helpful in writing the missing 30% of the requirements. You can use a predefined rating system, such as 1 to 5, where 1 indicates "Not Helpful" and 5 indicates "Very Helpful."
Completing the entire task may take 3-5 minutes, depending on your familiarity with the domain and your rating speed. The task includes some domain-specific knowledge in the UAV field, so it may take some additional time to understand the requirements.
You should have a certain level of familiarity with the UAV domain to effectively evaluate the practicality of the missing requirement concepts.
Your feedback is crucial for our research and will help improve the recommendation methods for missing requirements concepts, enhancing the quality and reliability of UAV systems. Thank you for participating in this study!
Here is the 70% UAV requirements description:
1 . If a UAV has pending flight plans then when UAV reaches the final waypoint of its current flight plan the Single UAV Flight Plan Scheduler shall execute the next assigned flight plan.
2 . When a UAV's current flight is cancelled the Single UAV Flight Plan Scheduler shall in turn cancel all scheduled flight plans for that UAV.
3 . The UI Middleware shall provide an interface for registering UI clients.
4 . If a command is issued by the Vaadin UI for an UAV the Vaadin UI shall request control of that UAV.
5 . When the Real Time Flight UI is loaded a map shall be displayed.
6 . If a UAV takes evasive actions the system will ensure that UAV will eventually reach its destination
7 . The Object Avoidance system only issues commands within the capabilities of the UAV
8 . When a UAV has an active onboard Obstacle Avoidance then the Obstacle Avoidance system shall not issue directives
9 . When a GCS requests activation of a newly detected UAV the GCS Middleware shall forward the request to Dronology.
10 . When the GCS loses the connection to an UAV the GCS shall attempt to reconnect
11 . The Vehicle Core shall assign a unique ID to each activated UAV.
12 . The Single UAV Flight Plan Scheduler shall only execute one flight plan at a time for each UAV.
13 . When the return to home command is issued the Flight Manager shall return the UAV to its original launch location without issuing any additional waypoint or routing commands.
14 . The Flight Route Manager 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.
15 . The Flight Route Manager shall ensure that all flight routes represent a VALID FLIGHT ROUTE.
16 . When a flight route requires a customized takeoff altitude that differs from the system's default takeoff altitude it shall be specified in the flight route.
17 . When requested the Coordinate System shall transform coordinates to alternate formats.
18 . When given two coordinates the Coordinate System shall compute the direction from the first coordinate to the second coordinate.
19 . When the hover in place command is issued the Flight Manager shall halt the UAV in place and maintain its current position.
20 . If a flight plan is active and the hover in place command is rescinded the Flight Manager shall notify the UAV to continue to the originally designated waypoint.
21 . The Mission Planner shall manage predefined Flight Patterns
22 . When requested if a mission is currently active the Mission Planner shall cancel the active mission.
23 . When requested the Single UAV Flight Plan Scheduler shall schedule a route for execution.
24 . If a route contains a specific UAV ID the Single UAV Flight Plan Scheduler shall assign the route to the given UAV.
25 . If a scheduled flight is not manually assigned to a UAV the Single UAV Flight Plan Scheduler shall assign the route automatically to an UAV
26 . If requested the Single UAV Flight Plan Scheduler shall abort the currently executing flight plan of an UAV
27 . 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.
28 . The Vehicle Core shall support UAVs connected via the GCS
29 . The Vehicle Core shall support virtual UAVs
30 . When a UAV is deactivated the UAV Activation Manager shall cancel all current and scheduled flight plans
31 . The UAV Registration Manager shall store UAV meta-data information such as the UAV's technical characteristics
32 . When given a takeoff command the Internal Simulator shall move the UAV to the takeoff altitude corresponding to its current longitude and latitude.
33 . When given a goto command the Internal Simulator shall update the location of the UAV at increments of SIMULATION STEP SIZE meters moving it towards the target destination until the destination is reached.
34 . The Internal Simulator shall approximate the state of the battery
35 . The Activity Logger shall log all flight plan related events.
36 . The Activity Logger shall log all commands sent to and messages received from a GCS.
37 . The UI Middleware shall provide a list of all existing routes
38 . The UI Middleware accepts commands from UIs and forwards to Dronology
39 . The UI Middleware shall enable the creation and modification of flight routes
40 . The UI Middleware shall accept and activate a mission plan upon request.
41 . When the Vaadin UI is activated the Vaadin UI shall be configured according to stored configuration parameters.
42 . When loading the map view it shall be positioned at the pre-defined location
43 . When a route is assigned or removed from a UAV the Route Assignment UI shall notify Dronology.
44 . When a UAV is selected the Route Assignment UI shall display its active flight plans.
45 . A user may reorder routes or remove flight plans assigned to a UAV as long as the flight has not started execution.
46 . When a user shall cancels a pending flight plan the Route Assignment UI shall notify Dronology.
47 . The Route Creation UI shall distinguish between starting ending and intermediate waypoint markers.
48 . The Route Creation UI shall only accept valid altitude and speed values for waypoint.
49 . Each route shall include a unique ID a textual description and a set of waypoints all of which are editable in the UI.
50 . When requested the Route Creation UI shall send a newly created or modified route to dronology.
51 . The Route Creation UI shall allow the user to create and modify a route.
52 . The Route Creation UI shall allow a user to delete a route.
53 . The Real Time Flight UI shall display the name and status of all currently activated UAVs
54 . The Real Time Flight UI shall display all currently active flight plans on the map.
55 . The Dronology Runtime Monitor shall provide functionality to retrieve monitoring messages and distribute them to clients
56 . When a new monitoring message is received the Dronology Runtime Monitor shall forward the message to all subscribed clients
57 . The Dronology Runtime Monitor shall be able to receive messages from any Dronology component
58 . The GCS Middleware shall handle multiple GCS
59 . The GCS Middleware shall forward commands sent from Dronology to a GCS
60 . When the connection to the GCS from the GCS Middleware is lost the GCS Middleware shall notify Dronology and deactivate all associated UAVs.
61 . The GCS shall assign a message frequency for all UAVs.
62 . The GCS shall report newly connected UAVs to the GCS Middleware.
63 . The GCS shall transmit the UAV's properties to the GCS Middleware
64 . The Mission Planner shall execute flight plans for multiple UAVs concurrently.
65 . The Map Component shall support different types of map layers (e.g. terrain satellite)
66 . Each waypoint shall be specified using coordinates that include longitude latitude and altitude.
67 . When requested the Vehicle Core shall transition the UAV between states according to allowed state transitions as depicted in the UAV state transition diagram
68 . The Single UAV Flight Plan Scheduler shall maintain a managed list of pending flight plans for Each UAV.
69 . If a client registers for notifications the UI Middleware shall send notifications for specific events
Here are the requirement concepts, you need to score them according to their usefulness：
|battery||flight manager||schedule||current mission||avoidance||activity logger||map view||map layer||phone||altitude|
|coordinates||attitude||home altitude||vector parameter||velocity parameter||obstacle parameter||obstacle detection sensor||cruise plan||landing plan||take off plan|
Thank you for taking the time to participate in this survey. Your feedback is greatly appreciated and will be invaluable for improving our understanding in our research methodology. Once again, thank you for your support!