Requirement prioritization (RP) is considered one of the main activities of requirement engineering (RE). The stakeholders’ feedback and viewpoints in a project form the basis of RP. Two types of stakeholders can be included in a software project, one of which is the system architect and the other is the system users. After evaluating the organization and determining the non‐functional requirements (NFRs), the system architects identify the technical relationships among these NFRs, while system users contribute usage‑driven viewpoints that reflect their operational experiences. Stakeholders possess varying levels of organizational power, which is determined by consolidating a defined set of parameters—namely influence, project involvement, and contribution—through an expert‐driven assessment. While this study focuses on these core parameters, the framework allows the incorporation of additional organizational indicators in future applications if required. This composite metric was then quantified using the 100 method to assign a final power value to each stakeholder group. An NFR’s prioritization depends on both types of stakeholders. This study aimed to prioritize NFRs by collecting and extracting data from these two categories of stakeholders, leading to a heuristic smooth average approach (SAA). This approach increased the prioritization speed compared to the genetic algorithm (GA) and analytic hierarchy process (AHP) by 19% and 41%, respectively. The ease of use in prioritization also improved by 22. 5% and 65%, respectively, compared to the other two approaches.
Ramezani et al. (Thu,) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: