# Requirements Engineering for a Drone-Enabled Integrated Humanitarian Logistics Platform
## 5 Research Methodology
### Requirement Validation for the AIRDROP Platform
#### 5.2.4 Questionnaire Analysis  
With the aim of gaining valuable insights from the responses and providing a comprehensive analysis, descriptive statistics were employed to summarize and understand the data. For starters, descriptive statistics were used for the introductory part of the questionnaire and included visualizations to showcase the distribution of professional backgrounds among respondents along with their years of experience. This not only provided valuable context for interpreting the subsequent data but also laid a foundation for the execution of non-parametric tests. Additionally, their expertise in different disaster management as well as general domains was also visualized to better comprehend their background and knowledge, thus enabling a clearer insight into their views and potential influence on the requirement prioritization process. The process of requirement prioritization plays a crucial role in assessing the results of the questionnaire. By assigning priorities to the identified requirements, valuable information can be gained, with regard to the needs and preferences of potential stakeholders, who, through their responses, shall contribute to pinpointing the most important features and functionalities. This is a structured approach to decision-making, ensuring that the most vital requirements are given the highest priority and receive the necessary attention during the next implementation stages, while the less important ones are postponed or even ignored. Requirement prioritization techniques range from simple and qualitative procedures to advanced analytic prioritization approaches that fall under the genre of optimization algorithms [24]. For instance, the application of the Kano model involves the assessment of participant contentment and discontentment to classify requirements into distinct scoring groups [89; 90]. Amongst quantitative techniques, simple ranking involves the meticulous ranking of requirements based on predefined criteria [91], while in more elaborate approaches, such as the analytic hierarchy process (AHP) and the prioritization matrix, numerous criteria are integrated, such as effort, value, and risk, to facilitate requirement prioritization [92]. Employing computational techniques in conjunction with expert insights, search-based software engineering (SBSE) acts as an valuable tool, effectuating the automation of requirement selection and providing dynamic assistance across the software engineering lifecycle [93]. Another common prioritization strategy in requirement prioritization, selected to be employed for the prioritization of the AIRDROP requirements, is the MoSCoW methodology [94]. This strategy aids in classifying requirements according to their urgency and priority by providing a simple and easy-to-understand framework, which is particularly well-suited for the case of AIRDROP due to its ability to handle a large volume of requirements. \"MoSCoW\" is an acronym for:  
**MUST**: These are the requirements that, in order for the solution to be declared successful, must be fulfilled. In this research, requirements with scores between 5 and 4 were assigned in this category. **SHOULD**: These requirements need to be met as closely as possible due to their critical nature. Although not essential, like the MUST requirements, their inclusion considerably increases the project's overall value and effectiveness. In this research, requirements with scores between 4 and 3 were assigned in this category. **COULD**: These requirements are desirable but not obligatory. They encompass additional features or capabilities that could be taken into account if time and resources allow. These requirements may be deprioritized or deferred to a later stage. In this research, requirements with scores between 3 and 2 were assigned in this category. **WOULD**: These requirements are optional and may be considered for future improvements or iterations. Since they hold the lowest priority, they can be delayed or disregarded without adversely affecting the project's essential functions.