# Requirements Engineering for a Drone-Enabled Integrated Humanitarian Logistics Platform
## 6 Results
### Descriptive Analysis
#### 6.1.3 MoSCoW Requirement Prioritization
Unlike the other services, for which data are inherently relevant to the specific disaster scenario, VR training content could potentially be generated from various alternative sources, including historical disaster data, or simulations created explicitly for training purposes. Similarly, information about pest control efforts specifics can be acquired using a combination of methods and data sources, such as environmental sensors, local reports, historical data, and satellite imagery. MED_002 is the only requirement of the rescue service that was not ranked as \"MUST\" and was ranked as \"SHOULD\". This requirement describes the need for the UAV to use ML algorithms to recognize human actions (e.g., coughing and sneezing). According to a technology expert specialized in AI and ML, this feature might not provide significant advantages but could add unnecessary computational complexity and costs. Additionally, they emphasized the potential risk of false positives, in which the ML algorithms might mistakenly interpret non-threatening motions as coughing or sneezing, leading to unnecessary alerts and potentially diverting resources from more critical tasks. As far as the sampling service is concerned, six \"MUST\" and three \"SHOULD\" requirements were reported. Less emphasis was placed on enabling the teleoperation of the MGV via a UAV relay (SAM_006), enabling the UAV to transport the MGV (SAM_007) as well as equipping the MGV with a water capturing mechanism (SAM_008). This ranking is reasonable since these requirements complement the other sampling requirements. In particular, the UGV is already equipped with a camera and water capturing mechanism. Also, the need for the UAV to transport the MGV would only be applicable to sampling scenarios where the MGV needs to reach AoIs it cannot navigate on its own, e.g., hard-to-access locations or disaster-affected areas with debris. Analyzing the transparent funding service, eight requirements were ranked as \"MUST\" and four as \"SHOULD\", which include the TF_003 (smart contracts), TF_004 (tokenization), TF_006 (real-time donation tracking), and TF_010 (governance and consensus mechanisms) requirements. While these features enhance transparency and efficiency, their applicability varies based on the scale and complexity of the disaster management operation. Also, a disaster management professional commented that TF_010 might introduce unnecessary overhead in smaller-scale operations. In the VR training service, 11 requirements received a \"MUST\" and 4 a \"SHOULD\" ranking. Among the \"SHOULD\" requirements, VR_010 emphasizes that training and materials should be exclusively in English, which might not align with local needs, as mentioned by two academics. VR_011 necessitates specific training equipment and room conditions, thus potentially limiting adaptability in resource-constrained areas. VR_002 specifies that training cannot be excessively lengthy and VR_013 describes the need for modelling additional VR objects to make visualizations more representative of real disasters. Both requirements were deemed to be of lesser importance for the service's success. All 12 warehouse inventory management, 5 pest control, and 5 physical manipulation requirements were ranked as \"MUST\". Concerning reconstruction, five out of six requirements were evaluated as \"MUST\", with RE_003, which pertains to tethering a UAV to a construction machine, categorized as a \"SHOULD\" requirement. Finally, 25 UI requirements were ranked as \"MUST\" and 2 as \"SHOULD\". This ranking diminishes the importance of specifying a click limit in UI interactions (UI_005), considering that the complexity of interfaces can vary, and certain actions may inherently require more clicks, as noted by a technical expert among the participants, with experience in such interfaces. Similarly, adhering to external standards (UI_015) may not always be practical in cases where standards conflict or customized interfaces are required.