Javascript must be enabled to continue!
A Review: Requirements Prioritization Criteria Within Collaboration Perspective
View through CrossRef
The attributes or criteria used in the requirements prioritization process become an essential reference in calculating priorities. Most of the techniques are used to increase the value impacting business success. On the contrary, there are limitations on cost, time, and resources for developing software. Therefore, the requirements prioritization process often requires collaboration from the perspectives involved. So far, the pattern and basis have not been seen in the criteria used in the requirements prioritization process. Consequently, there need to be other factors that become a reference so that the selection of criteria is appropriate. This study identifies criteria based on the categorized perspectives of requirements prioritization. A systematic literature review presents criteria for prioritizing requirements from multiple collaborative perspectives. Findings show that the criteria in requirements prioritization can be classified into beneficial and non-beneficial, where business value and development cost are the most frequently used criteria. Furthermore, the involvement of multiple perspectives in requirements prioritization focuses on the client’s and developer’s perspectives. The findings also reveal that some of the challenges in the requirements prioritization process are biases by stakeholders, reducing pairwise comparison, and scalability. In the future, it will be investigated whether the selection of criteria correlated with stakeholder perspectives will increase the accuracy of priorities. Thus, the contribution of this paper is to recommend criteria from stakeholders’ perspectives.
Universiti Putra Malaysia
Title: A Review: Requirements Prioritization Criteria Within Collaboration Perspective
Description:
The attributes or criteria used in the requirements prioritization process become an essential reference in calculating priorities.
Most of the techniques are used to increase the value impacting business success.
On the contrary, there are limitations on cost, time, and resources for developing software.
Therefore, the requirements prioritization process often requires collaboration from the perspectives involved.
So far, the pattern and basis have not been seen in the criteria used in the requirements prioritization process.
Consequently, there need to be other factors that become a reference so that the selection of criteria is appropriate.
This study identifies criteria based on the categorized perspectives of requirements prioritization.
A systematic literature review presents criteria for prioritizing requirements from multiple collaborative perspectives.
Findings show that the criteria in requirements prioritization can be classified into beneficial and non-beneficial, where business value and development cost are the most frequently used criteria.
Furthermore, the involvement of multiple perspectives in requirements prioritization focuses on the client’s and developer’s perspectives.
The findings also reveal that some of the challenges in the requirements prioritization process are biases by stakeholders, reducing pairwise comparison, and scalability.
In the future, it will be investigated whether the selection of criteria correlated with stakeholder perspectives will increase the accuracy of priorities.
Thus, the contribution of this paper is to recommend criteria from stakeholders’ perspectives.
Related Results
Evaluating the Science to Inform the Physical Activity Guidelines for Americans Midcourse Report
Evaluating the Science to Inform the Physical Activity Guidelines for Americans Midcourse Report
Abstract
The Physical Activity Guidelines for Americans (Guidelines) advises older adults to be as active as possible. Yet, despite the well documented benefits of physical a...
Requirements Prioritization Techniques for Global Software Engineering
Requirements Prioritization Techniques for Global Software Engineering
<p>Increase in globalization of the industry of software requires an exploration of requirements engineering (RE) in software development institutes at multiple locations. Re...
Multi-Stakeholder Decision Aid for Improved Prioritization of the Public Health Impact of Climate Sensitive Infectious Diseases
Multi-Stakeholder Decision Aid for Improved Prioritization of the Public Health Impact of Climate Sensitive Infectious Diseases
The effects of climate change on infectious diseases are an important global health concern and necessitate decisions for allocation of resources. Economic tools have been used pre...
Approaches for disease prioritization and decision-making in animal health, 2000–2021: a structured scoping review
Approaches for disease prioritization and decision-making in animal health, 2000–2021: a structured scoping review
This scoping review identifies and describes the methods used to prioritize diseases for resource allocation across disease control, surveillance, and research and the methods used...
Text Mining in Cancer Gene and Pathway Prioritization
Text Mining in Cancer Gene and Pathway Prioritization
Prioritization of cancer implicated genes has received growing attention as an effective way to reduce wet lab cost by computational analysis that ranks candidate genes according t...
Investigating Fitness Functions for Search-based Requirements Prioritization
Investigating Fitness Functions for Search-based Requirements Prioritization
It can be challenging for people to select the most relevant requirementamong several software system development options.Requirements prioritization defines the ordering for execu...
An ontology-based approach to engineering ethicality requirements
An ontology-based approach to engineering ethicality requirements
AbstractIn a world where Artificial Intelligence (AI) is pervasive, humans may feel threatened or at risk by giving up control to machines. In this context, ethicality becomes a ma...
Test case prioritization for changed code using nature inspired optimizer
Test case prioritization for changed code using nature inspired optimizer
The software development and maintenance phase succeeded with significant regression testing activity. The software must be re-tested every time it upgrades to preserve its quality...

