Requirements Prioritization Techniques Research Articles

Choosing a Suitable Requirement Prioritization Method: A Survey

Software requirements prioritization plays a crucial role in software development. It can be viewed as the process of ordering requirements by determining which requirements must be done first and which can be done later. Powerful requirements prioritization techniques are of paramount importance to finish the implementation on time and budget. Many factors affect requirement prioritization such as stakeholder expectations, complexity, dependency, scalability, risk and cost. Therefore, finding the proper order of requirements is a challenging process. Hence, different types of requirements prioritization techniques have been developed to support this task. In this survey we propose a novel classification that can classify the prioritization techniques under two major classes: relative and exact prioritization techniques class where each class is divided into two subclasses. We also provide an overview about fifteen different requirements prioritization techniques that are classified under our proposed classification. Moreover, we make a comparison between methods that are related to the same subclass to analyze their strengths and weakness. Based on the comparison results, the properties for each proposed subclass of techniques are identified. Depending on these properties, we present some recommendations to help project managers in the process of selection the most suitable technique to prioritize requirements based on their project characteristics.

Selection Criteria for Requirement Prioritization Techniques for software development: Data Analysis

Requirement analysis is a critical stage in the software development lifecycle that drives project success. Elicitation techniques that are in line with stakeholders' needs, including both functional and non-functional factors, have a significant impact on software results. Finding the best approach to requirement prioritising is difficult, even with the wide range of approaches available. Value-based requirements are carefully woven into particular priority criteria by this study, which pioneers an approach that assesses requirement prioritisation techniques based on four important elements. The work emphasises the computation of full scores for different methods, providing definitive graphical representations that enable comparison assessments. This novel method simplifies requirement-prioritising analysis and selection by providing a structured framework for assessing and selecting the best solution in a particular situation. Through the integration of many elements and alignment with stakeholder requirements, this approach provides a systematic framework designed to improve the effectiveness of requirement prioritising in software development. Its diverse approach tackles the intricacies present in these procedures, ultimately leading to more efficient decision-making in software development projects.

PRIUS: Applying Gamification to User Stories Prioritization

In the context of agile development methodologies, due to the volatile nature of requirements and constant changes, prioritizing requirements is often a problem. Requirements prioritization is a complex, collaborative, continuous, cyclical, and laborious process, resulting in low engagement. Gamification is a viable strategy for improving engagement in such processes, as it enhances activities by promoting experiences akin to those found when playing games. This paper proposes a gamified approach, called PRIUS, for requirements prioritization in agile software development. The approach combines a requirements prioritization technique - Wiegers Matrix - with game elements, aiming to promote stakeholders' engagement in the activity. The PRIUS Gamified approach was developed, and a supporting system was implemented. They promote the integration of gamification elements for prioritizing agile artifacts asynchronously. A controlled experiment was conducted, comparing the gamified version of PRIUS with a non-gamified version in an academic environment. The results suggest that the gamified approach positively impacts some aspects of engagement of users in requirements prioritization using agile software development.

Literatur Review: Penerapan Metode Analytic Hierarchy Process Sebagai Teknik Prioritas Kebutuhan Perangkat Lunak

AHP is one of the popular techniques used in prioritizing software requirements. This study aims to determine the application of AHP as a software requirements priority technique by reviewing thirty literature related to the application of AHP as a software requirements prioritization technique pub-lished in 2017 to 2023. The results of the study explain that the application of AHP has several ad-vantages, but on the other hand AHP also has some drawbacks. Over time, a number of literatures have discussed the development of AHP which aims to minimize weaknesses in the application of AHP. The development of AHP is by integrating AHP with Planning Game, MoSCoW, QFD, and Fuzzy. In addition, development is also carried out by adding new algorithms, namely ReDCCahp and Enhanced AHP. The results of this study provide a useful reference for researchers and practitioners in the field of requirements engineering in prioritizing software requirements using AHP.

Exploring Software Requirements Prioritization techniques: Types, Evolution, and Metrics for effective Decision-Making

Exploring Software Requirements Prioritization techniques: Types, Evolution, and Metrics for effective Decision-Making

Exploratory study of existing research on software requirements prioritization: A systematic literature review

AbstractRequirements prioritization is giving priority to software requirements on the basis of its importance. The current research paper addresses the importance and limitations of existing research on requirements prioritization. A lot of requirements prioritization techniques are presented by authors, but these techniques have certain limitations. Not all techniques are either applied or suitable to prioritize all types of requirements. Similarly, in these techniques, only few are scalable for large size requirements. The objective of the current research is to identify all possible software requirements prioritization techniques and to show the suitability of these techniques to prioritize different types and sizes of requirements. To achieve research objectives, a systematic literature review (SLR) is carried out. In conducting SLR, planned protocol is designed, which include all the necessary steps necessary for SLR process. As a result of SLR, 60 primary studies were selected for data extraction as a result of SLR. Outcome of SLR shows that not all techniques are scalable to prioritize any size requirements. Also, there are few techniques found that are either applied on all types of requirements or not suitable to prioritize all types of requirements as these techniques are specifically designed for particular types of requirements.

A Gender-Based Comparative Evaluation of O2O Food Delivery Characteristics : A Requirements Prioritization Approach

This article intended to assess enablers and deterrents to online-to-offline (O2O) food delivery (OFD) use from users and non-users perspectives at the sub-dimension level. The study aimed to parallelly evaluate these sub-dimensions for both genders and provide a self-comparison of preferences. An online survey was conducted to obtain users preferences. Two hundred valid responses were analyzed using the simple ranking method of the requirements prioritization approach for ordinal data analysis. The findings revealed that females required comprehensive product details, ease of interface use, convenience in transactions, and overall hygiene at all stages. Privacy violation was reported as the most significant risk perceived by females. Male OFD users asked for safe food packaging and a good delivery experience but perceived the product performance failure as a severe risk. The inability to access food quality online was the top reason to avoid OFD use. The findings will help OFD operators and food-tech start-ups improve their operations by addressing specific issues. The article is unique as it followed an approach different from just establishing linear relations by analyzing ordinal data using the requirements prioritization technique.

A Systematic Literature Review of AI-Based Software Requirements Prioritization Techniques

A Systematic Literature Review of AI-Based Software Requirements Prioritization Techniques

Security Requirements Prioritization Techniques: A Survey and Classification Framework

Security requirements Engineering (SRE) is an activity conducted during the early stage of the SDLC. SRE involves eliciting, analyzing, and documenting security requirements. Thorough SRE can help software engineers incorporate countermeasures against malicious attacks into the software’s source code itself. Even though all security requirements are considered relevant, implementing all security mechanisms that protect against every possible threat is not feasible. Security requirements must compete not only with time and budget, but also with the constraints they inflect on a software’s availability, features, and functionalities. Thus, the process of security requirements prioritization becomes an integral task in the discipline of risk-analysis and trade-off-analysis. A sound prioritization technique provides guidance for software engineers to make educated decisions on which security requirements are of topmost importance. Even though previous research has proposed various security requirement prioritization techniques, none of the existing research efforts have provided a detailed survey and comparative analysis of existing techniques. This paper uses a literature survey approach to first define security requirements engineering. Next, we identify the state-of-the-art techniques that can be adopted to impose a well-established prioritization criterion for security requirements. Our survey identified, summarized, and compared seven (7) security requirements prioritization approaches proposed in the literature.

Current Stance on Requirement Prioritization Techniques: Challenges, Opportunities, and Future Directions

Requirement Engineering is an important aspect of Software Engineering, while Requirement prioritization is a crucial phase of Requirement Engineering, specifically in agile development. In today's world, software systems are nothing but the backbone for business organizations. However, for business operations, requirements are changing rapidly, and it seems to be impossible to accomplish the requirements at once. It may be possible with the help of requirement Prioritization as it decreases the risk for failure. It helps implement the most required and prioritized feature given by stakeholders. The entire purpose of this research is to investigate and rate the complete process of Requirement Engineering, specifically the current requirement prioritization techniques, by conducting an extensive literature review. Furthermore, to identify the opportunities, gaps, and challenges for future

Model planiranja logističke podrške u uslovima ograničenih resursa

Introduction/purpose: The paper presents a model of logistics support planning in the conditions of limited logistic resources based on the prioritization of customer requirements and resource allocation. Decisionmakers play a crucial role in the efficient and equitable allocation of resources as they prioritize among different user requirements. Methods: Requirement prioritization techniques that use nominal scale, ordinal scale, and ratio scale, and five methods for converting ranks into weighting coefficients have been applied to determine the degree of significance of user requirements. The Requirements triage method has been used for establishing relative priorities, while the heuristic algorithm determining the Kemeny median was used to consolidate individually ranked requests into a group rank. In order to balance opposing demands of users, consensus measures of group decision making were used. For obtaining an optimal planned solution of logistic support, the methods and techniques of resource allocation were applied. Results: A model for adaptive planning of logistics support in the conditions of limited resource capacities of the logistics system has been developed. Conclusion: The proposed model can be effectively applied in other areas of resource allocation.

E-AHP: An Enhanced Analytical Hierarchy Process Algorithm for Priotrizing Large Software Requirements Numbers

One of the main activities of software requirements analysis is requirements prioritization. The wrong requirements prioritization is risky as it leads to many software failures. The current requirements prioritization techniques can’t deal with large requirement numbers efficiently, which is considered one of their main issues. Many researchers have agreed that the analytical hierarchy process (AHP) is one of the best prioritization techniques as it produces highly accurate results. AHP has two main problems: scalability and inconsistency. These problems have motivated us to propose an improved version of AHP for software requirements prioritization, namely Enhanced AHP (E-AHP). A performance evaluation has been done for the conventional AHP, E-AHP, and one of the recent algorithms that also try to solve the AHP scalability problems, namely removing eigenvalues and introducing the dynamic consistency checking algorithm into AHP (ReDCCahp) algorithms The evaluation shows which algorithm takes the least time, uses the least memory, produces the most consistent and accurate results, and has the highest scalability. The three algorithms have been evaluated by running their codes using different numbers of requirements ranging from 10 to 500. The results show that E-AHP is more scalable, takes the least time, uses the least memory, and produces the most consistent and accurate results compared to the other two algorithms. That becomes remarkable when the number of requirements increases. Therefore, E-AHP is suitable to be applied in large software projects, as it can deal efficiently with the large software requirements numbers.

Guideline for the Selection of Requirement Prioritization Techniques in Agile Software Development: An Empirical Research

Prioritization is an essential process in any software development. Moreover in Agile, Requirement Prioritization (RP) needs more formal process because it is difficult to maintain priority after requirement change. Changes in the priority list are a continuous process in Agile Software Development (ASD) hence, the ignorance of critical requirements during prioritization will result several problems like unsatisfied client and poor quality of product. Moreover, there is little empirical knowledge on the state of the practice and contemporary problems exist in choosing best prioritization technique after the requirement change in Agile. To achieve this objective a guideline for the selection of RP technique is needed. Hence, the empirical research is used as a methodology for the evaluation of the requirement prioritization techniques practiced in Agile. The aim of this study is to determine RP techniques used in software industry and identify aspect or evaluation criteria to choose the best RP technique according to the environment. This study conducts an empirical study of requirement prioritization after requirement change in Agile, based on the responses from 137 Agile software practitioner representing around 31 organizations in Pakistan. The results reveal the main decision makers in the process of RP, prioritization technique after requirement change in Agile with the evaluation criteria and aspects to perform requirement prioritization. These findings will serve as a foundation to provide a guideline for selecting suitable requirement prioritization techniques in Agile which can help software practitioners to choose appropriate prioritization techniques during the process of requirement change in Agile.

An Empirical Evaluation of Requirements Prioritization Techniques

In today’s time and budget intensive software development market, quick delivery is the basicmotive of teams. Software development teams strive to gain customer satisfaction by allpossible means. Requirements prioritization is the most challenging customer input dependenttask in the software development life cycle that decides the fate of a project. Selection of awell-suited requirements prioritization technique may result in customer satisfaction and ontime delivery time. Literature reports on many requirements prioritization techniques inpractice. However, each has its own features that can outperform the rest for a certain case.Therefore, this research is conducted to empirically evaluate the existing techniques in termsof certain quality measures (i.e., accuracy, efficiency, and scalability). The selected techniquesare evaluated for the small, medium and large scale of requirements sets. For that, we selectedfive existing techniques that are multi-criteria-decision-making techniques and have userinvolvement (i.e., Analytical Hieratical Process (AHP), Analytical Network Process (ANP),FuzzyAHP, FuzzyANP and Interactive Genetic Algorithm (IGA)). The experimental resultsshowed that among the five selected techniques, FuzzyAHP is the most efficient and accuratetechnique for the large dataset of requirements.

Role of Requirement Prioritization Technique to Improve the Quality of Highly-Configurable Systems

Highly-configurable systems are such systems which are not developed for single scenario. However, perhaps they have variable functionality and they are developed for hybrid scenarios. Producing a good highly-configurable system within time and with customer satisfaction is not easy. Handling requirements effectively in such a way that it take least time to market, is one of the most difficult tasks in highly-configurable system. In this paper, a quantitative requirement prioritization technique for highly-configurable systems is proposed. This technique involves all stakeholders and can be used primarily for large scale software projects. The proposed technique is evaluated by taking a case study of the highly-configurable point of sale for automotive industry. The result shows that the proposed technique provides promising results and can be enhanced with more future work.

Requirements Prioritization using Risk Assessment for Analyzing Requirements

Requirements elicited from requirements elicitation session with stakeholders are usually comes in bulk and it is impossible to execute them simultaneously. In addition, the requirements elicited are unfiltered and usually low quality including ambiguous, incomplete and unclear. The low quality of requirements are then refined in the next activity which is requirements analysis in requirements engineering. This paper aims to integrate requirements prioritization techniques focused on the factor of risk in requirements analysis since the early stage of requirements engineering. It is seems to have a little evidence on that requirements prioritization focus on the factor of risk in requirements based on our conducted literature review. This paper begins with elaboration on requirements prioritization, further to the aspects of requirements prioritization, criteria for best suited technique, a literature review on requirements prioritization techniques. We then proposed a framework for requirements analysis with the integration of requirements prioritization. A case study is elaborated for a better vision on the process of the proposed approach. Finally, this study is believed to produce a better quality of requirements from the requirements analysis process.

Investigation of Requirements Interdependencies in Existing Techniques of Requirements Prioritization

Requirements prioritization (RP) is considered as a key role in producing a successful system by selecting the most important requirements to be released. Requirements interdependencies (RI) is one of the crucial aspects that need to be addressed in RP, since most of the requirements in reality are not independent and have dependencies between each other. Thus, ignoring RI in RP process may lead to produce inaccurate prioritization result which directly impacts the system’s success. In spite of this, little is known about the impact of RI, and obviously further research is urgently required to measure the RI in the RP techniques. Hence, this study aims to investigate and analyze the existence and the execution steps of handling RI in the existing RP techniques to improve the performance of techniques in generating accurate result and assist the researchers and practitioners to select the appropriate technique that can handle RI in prioritization process. The findings indicate that, out of 65 techniques, there are only 4 techniques that handle the RI. The result reveals that these four techniques still suffer from issues of manual process and heavily rely on the experts’ participation. Proposing a new technique is recommended to overcome the identified limitations.

Investigation of Stakeholder Analysis in Requirement Prioritization Techniques

Requirement Prioritization is considered as an essential process that leads to the production of a successful system by presenting the prime requirements that need to be developed. Stakeholder Analysis (SA) plays a vital role in the requirement prioritization process where it aims to select and identify the impact value of each stakeholder, depending on their significance along with the overall impact of requirements posed by them that may have on the project’s success. Thus, the aim of this paper is to investigate the stakeholder analysis in existing requirement prioritization techniques, in order to enhance the performance of existing RP techniques in producing accurate result. All existing RP techniques are critically analyzed to determine the existence of SA in their processes, presenting the execution steps that are used to performed SA process in their prioritization process. The findings of this study show that out of 66 techniques, there are only 5 techniques (evolve, mathematical programming, VIRP, RUPA and PHandler) that conducted the SA analysis in their prioritization processes. However, the result presents that these five techniques still face issues of time consuming, manual and requiring the involvement of the experts in conducting SA process.

An Appraisal of Software Requirement Prioritization Techniques


 
 
 
 In recent times, there is a paradigm shift from the use of paper based systems to the use of software systems in all spheres of life. However, the development of high quality, cost effective and useable software systems is a major challenge. One of the major obstacles confronting the successful implementation of software systems is the inability to implement all stakeholders' requirements in software development projects. This constraint is usually due to limited human resources, budget and time. Thus, most software systems have failed. It, therefore, becomes pertinent to prioritize software requirements. Requirement prioritization involves the selection of requirements that are considered more important from an accumulated list of stakeholders' requirements. There are two techniques that are used for categorizing software requirements. These techniques include the requirement prioritization methods and the negotiation methods. Requirement prioritization methods are based on different scales which include nominal scale, ordinal scale and ratio scale. The accuracy of these methods, however, is a challenge especially when prioritizing large number of requirements.
 Aims: Hence, this paper reviews different techniques for prioritizing requirements by highlighting their strengths and weaknesses. Techniques such as binary search tree, AHP, hierarchy AHP, priority group/Numerical Analysis, bubble sort, MoSoW, simple ranking and Planning Game were analyzed and compared in this study.
 Methodology: The study is based on previous literature on requirement prioritization.
 Results: The study showed that numerical assignment and simple ranking methods require less time in the prioritization process and they also have low scalability and reliability. The study also showed that the analytic hierarchy process requires more time for requirement prioritization; it is reliable but it is not scalable. The study also revealed that it is difficult to prioritize requirements with the existing prioritization techniques when multiple stakeholders are involved.
 Conclusion: The study suggests that future researches should be based on the design of requirement prioritization techniques that will have the ability to accommodate large stakeholders and requirements.
 
 
 
 

Requirements Prioritization Techniques Comparison

Requirements prioritization is considered as one of the most important approaches in the requirement engineering process. Requirements prioritization is used to define the ordering or schedule for executing requirement based on their priority or importance with respect to stakeholders’ viewpoints. Many prioritization techniques for requirement have been proposed by researchers, and there is no single technique can be used for all projects types. In this paper we give an overview of the requirement process and requirement prioritization concept. We also present the most popular techniques used to prioritize the software project requirements and a compression between these techniques. On the other hand, we spot the light on the importance of involving the non-functional requirements prioritization because of the great effects of non-functional on project success and quality; some approaches that used in prioritize non-functional requirements are discussed in this paper, in addition a general model is proposed based on reviewing the prioritization techniques in order to suggests a best suited technique for specific projects according to decision makers parameters.