Decision theoretic requirements prioritization A two-step approach for sliding towards value realization

Kukreja, Nupul

doi:10.1109/icse.2013.6606746

Cited by 16 publications

(6 citation statements)

References 4 publications

(5 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Hence, different authors have highlighted the benefits of requirement prioritization at various times. For instance, Kukreja [23] reported that requirement prioritization facilitates users' involvement in the software development process. Hence, all stakeholders involved in the system development agree on the requirements that a particular software release should contain.…”

Section: Benefits and Challenges Of Prioritizing Software Requirementsmentioning

confidence: 99%

An Appraisal of Software Requirement Prioritization Techniques

Iroju¹,

Ikono

Gambo

2018

AJRCoS

View full text Add to dashboard Cite

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.

show abstract

Section: Benefits and Challenges Of Prioritizing Software Requirementsmentioning

confidence: 99%

An Appraisal of Software Requirement Prioritization Techniques

Iroju¹,

Ikono

Gambo

2018

AJRCoS

View full text Add to dashboard Cite

show abstract

“…All requirements have equal priority if they fall within the same group. These approaches rank requirements based on their absolute importance as Priority Groups Technique [40], MoSCoW [46].Perhaps the biggest challenge facing developers in this category is capturing the true value of each requirement, but they are often unable to achieve it. Despite the fact that most stakeholders have sufficient experience and knowledge.…”

Section: VIImentioning

confidence: 99%

Considering Stakeholders’ Feedback in Requirements Prioritization using Social Network Analysis

Hamad¹,

El‐Sayed²,

Abdelmoez³

et al. 2016

IJCSE

View full text Add to dashboard Cite

Requirements prioritization plays a significant role to ensure successful planning of software releases. It helps software stakeholders to discover the most desirable requirements. In this paper, we propose requirements prioritization approach using social network analysis based on stakeholders' feedback. The social network models the relationships among stakeholders, their feedback and the system requirements. A string-matching algorithm is used to automate the discovery process of the relationship between stakeholders' feedbacks and requirements specifications based on text similarity. Then, the network is analysed to identify the priority of requirements depending on relevant groups of stakeholders and their feedbacks. As an attempt to validate the results, focus group is conducted to discover the relationship between the stakeholders' feedbacks and the requirements by manually matching each feedback with its related system requirement. Then, social network is built based on the results of the focus group and the system requirements are prioritized based on the network. The results of the two approaches are compared. The experimental results proved that there is a difference between the approach that uses string-matching and the focus group approach. The string-matching approach does not seem to be very appropriate in capturing the real relationship between the stakeholders' feedbacks and the requirements.

show abstract

“…The defect severity is set using the following values: trivial (1), minor (2), major (3), and critical (4). If a defect is not related to the CVFs and there is no 'add 1' in the formula, then the customer severity would be 0 regardless of defect severity.…”

Section: Evaluation Methodsmentioning

confidence: 99%

Value-Driven V-Model: From Requirements Analysis to Acceptance Testing

Han¹,

Lee²,

Choi

et al. 2016

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYThe goal of software testing should go beyond simply finding defects. Ultimately, testing should be focused on increasing customer satisfaction. Defects that are detected in areas of the software that the customers are especially interested in can cause more customer dissatisfaction. If these defects accumulate, they can cause the software to be shunned in the marketplace. Therefore, it is important to focus on reducing defects in areas that customers consider valuable. This article proposes a valuedriven V-model (V 2 model) that deals with customer values and reflects them in the test design for increasing customer satisfaction and raising test efficiency. key words: V-model, test design, value-based software engineering, customer value, customer satisfaction

show abstract

Decision theoretic requirements prioritization A two-step approach for sliding towards value realization

Cited by 16 publications

References 4 publications

An Appraisal of Software Requirement Prioritization Techniques

An Appraisal of Software Requirement Prioritization Techniques

Considering Stakeholders’ Feedback in Requirements Prioritization using Social Network Analysis

Value-Driven V-Model: From Requirements Analysis to Acceptance Testing

Contact Info

Product

Resources

About