# Requirements Engineering for a Drone-Enabled Integrated Humanitarian Logistics Platform
## 6 Results
### Descriptive Analysis
#### 6.1.3 MoSCoW Requirement Prioritization
In scenarios without such threats, this requirement may not be as crucial, justifying its classification as \"SHOULD\". Remarkably, all MPS requirements were universally ranked as \"MUST\", a reasonable consensus given the criticality of these requirements for successful mission execution, leaving no room for compromise. In the communication service, 26 requirements were ranked as \"MUST\" and 3 as \"SHOULD\". LINK_004 specifies latency restrictions for telemetry messages, which are intrinsically less important than C2 messages. BME_004 focuses on video streaming bandwidth restrictions, which, while crucial for certain tasks, might have been recognized by participants as less essential for some disaster management operations that do not require extensive video streaming. Similarly, CROW_001, which pertains to RSSI-enabled crowd counting, was categorized as \"SHOULD\". An end-user noted the multitude of missing person detection mechanisms already presented by AIRDROP, which led to a lower priority for this particular requirement in the overall system. Regarding the recharging requirements, 17 out 19 were ranked as \"MUST\" and 2 as \"SHOULD\". ARECH_011 recognizes that requiring dedicated UAV charging infrastructure on UGVs may not be as essential, since alternative charging methods (MIMO recharging configuration and dedicated UAV recharging infrastructure) are available as described by the requirements from ARECH_001 to ARECH_10. As pinpointed by an end-user, mandating UAV battery charging when it drops below 50% state-of-charge (ARECH_013) might not always be practical, especially in time-sensitive missions. Eight social media sensing requirements were ranked as \"MUST\" and seven as \"SHOULD\", including all location extraction methods (from SOCI_007 to SOCI_012). This ranking emphasizes the need for flexibility in extracting locations from multiple sources for enhanced system robustness. SOCI_013, i.e., real-time social media data pre-processing and de-noising, was also ranked as a \"SHOULD\" requirement, acknowledging its potential resource-intensive nature while allowing for flexibility in data processing. Shifting towards the prediction service, four requirements were ranked as \"MUST\" and three as \"SHOULD\". PRE_001 emphasizes the use of social media data for prediction, which might not be feasible or necessary in all cases, depending on data availability and reliability. According to an end-user, AIRDROP already incorporates a plethora of powerful disaster insight mechanisms, and the addition of the less reliable social media data may not provide as significant value. A similar rationale applies to PRE_006 and PRE_007, which involve predicting initial demand patterns with regard to funding as well as evacuation and shelter needs, respectively, using historical data. Such data, according to a subject matter expert, are not important for all hazards. Some disasters may have predictable patterns that can be informed by historical data, while others may not, rendering the use of historical data less critical. Looking into the DSS service, 26 requirements were ranked as \"MUST\" and 6 as \"SHOULD\". Some requirements, i.e., accessing video streaming (INT_015) and photos (INT_016) through the DSS, the use of Docker images (INT_017) and the ability to conduct communication effectiveness and network traffic analyses (ANA_014) were rated lower in importance. These rankings could be attributed to the complexity and resource-intensive nature of these tasks as well as their limited applicability in certain disaster scenarios. For example, real-time video streaming might be critical in a wildfire response but less so in a flood situation. Additionally, resource constraints, such as limited bandwidth, can affect practicality. Furthermore, in scenarios involving sensitive data, such as medical emergencies, the use of Docker images and network analyses may raise privacy and security concerns. Providing the VR training (INT_012) and pest control (INT_010) services with data was also considered less essential.