# Requirements Engineering for a Drone-Enabled Integrated Humanitarian Logistics Platform
## 7 Discussion: Implications for AIRDROP
Firstly, ARECH_002 and ARECH_003, despite their \"MUST\" ranking, have to be omitted from the design phase. This decision was based on the fact that academics, with their extensive expertise and experience, recognized the inherent technological complexities associated with these requirements and provided significantly lower rankings than end-users. The challenges posed by these requirements are not proportional to the benefits offered with respect to operational effectiveness. Addressing energy efficiency is a valid concern, but diving into antenna design intricacies is not warranted. Similarly, for PRE_002, end-users rated this requirement higher for its impact on situational awareness during disasters. However, academics considered the technical complexities in data integration and analysis, resulting in significantly lower rankings. Again, the complexity of dynamically predicting hazard footprints based on multiple data sources is not proportional to the benefits it offers in the context of AIRDROP when compared to real-time monitoring and assessment. In contrast, SOCI_001 and SOCI_002, despite academics' concerns about technical complexity, align with end-user priorities for real-time situational awareness. This alignment ensures that AIRDROP meets the operational needs of end-users, justifying the retention of these two requirements. RS_001 directly pertains to end-users and was identified as a potential mobility issue for them, evident in their significantly lower rankings compared to academics and disaster management professionals, as well as their open-ended responses. Given the focus on simplicity and usability for end-users, RS_001 had to be excluded from the design phase. On the contrary, CCWA_007 and CCWA_014, although rated lower by end-users compared to academics and disaster management professionals, were retained, as CCWA is tailored to cater to the needs of operational decision-makers, not end-users. As for SAM_004, in spite of lower end-user ratings, it was retained due to its potential recognized by academics and disaster management professionals for enhanced adaptability in constrained spaces. The decision to retain REL_001, a tethered communication relay, is grounded in end-users' practical experiences where traditional methods failed during disasters, thus addressing their real-world needs for effective communication. Finally, keeping TF_005 for identity verification, rated higher by disaster management professionals, aligns with their practical expertise in fraud prevention within HL. Thus, following the MoSCoW analysis and non-parametric tests, 273 requirements were identified as eligible for the design phase. These requirements sufficiently address the challenges expressed by participants familiar with similar platforms. AIRDROP includes 14 security requirements and seven scalability requirements. It also covers CBRN-related requirements, including hazardous gas and radiation monitoring. These requirements are crucial not only for environmental concentration monitoring through drones (GASRA_001, GASRA_002) but also for protecting first responders (RS_005, RS_006). Additionally, AIRDROP encompasses requirements for symptom monitoring and medical care, both applicable to biological hazards (MED_001, MED_003 to MED_005), as well as sampling for chemical hazards (SAM_001 to SAM_005, SAM_009). The platform also incorporates drones for flood detection and monitoring (FLOOD_001). In line with these requirements,AIRDROP prioritizes the establishment of robust data standards to ensure seamless data exchange among the numerous components of the system (45 data requirements). The platform also places a strong emphasis on interoperability (TF_001, INT_009), enabling it to integrate with existing disaster management systems. In addition to these requirements, two critical requirements, informed by participant feedback, were also incorporated. The first essential requirement, which pertains to the rescue module, is the \"Real-time Monitoring and Emergency Distress Signal\".