Value-Based Requirements Prioritization: Usage Experiences

Kukreja, Nupul; Payyavula, Sheetal Swaroop; Boehm, Barry; Padmanabhuni, Srinivas

doi:10.1016/j.procs.2013.01.084

Cited by 38 publications

(22 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…TOPSIS was deployed in the organization across various projects and proved valuable for providing a value-centric basis for prioritization [7]. Based on the positive feedback and usage experiences I decided to integrate TOPSIS into Winbook and used it for performing a two-step hierarchical prioritization of requirements as described below.…”

Section: Background and Related Workmentioning

confidence: 99%

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

Kukreja¹

2013

2013 35th International Conference on Software Engineering (ICSE)

Self Cite

View full text Add to dashboard Cite

Budget and schedule constraints limit the number of requirements that can be worked on for a software system and is thus necessary to select the most valuable requirements for implementation. However, selecting from a large number of requirements is a decision problem that requires negotiating with multiple stakeholders and satisficing their value propositions. In this paper I present a two-step value-based requirements prioritization approach based on TOPSIS, a decision analysis framework that tightly integrates decision theory with the process of requirements prioritization. In this two-step approach the software system is initially decomposed into high-level Minimal Marketable Features (MMFs) which the business stakeholders prioritize against business goals. Each individual MMF is further decomposed into low-level requirements/features that are primarily prioritized by the technical stakeholders. The priorities of the low-level requirements are influenced by the MMFs they belong to. This approach has been integrated intoWinbook, a social-networking influenced collaborative requirements management framework and deployed for use by 10 real-client project teams for the Software Engineering project course at the University of Southern California in Fall 2012. This model allowed the clients and project teams to effectively gauge the importance of each MMF and low-level requirement and perform various sensitivity analyses and take value-informed decisions when selecting requirements for implementation.

show abstract

Section: Background and Related Workmentioning

confidence: 99%

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

Kukreja¹

2013

2013 35th International Conference on Software Engineering (ICSE)

Self Cite

View full text Add to dashboard Cite

show abstract

“…These complexities increase the need for human interaction that becomes infeasible when stakeholder size is too large. One major challenge that arises from the scalability issues is the rank reversal problem [6].…”

Section: Introductionmentioning

confidence: 99%

“…It is particularly challenging for large scale projects with large number of stakeholders since such projects would have more volatile requirements that are subject to change. It is essential to take such changes into consideration when prioritizing requirements [6]- [8].…”

Section: Introductionmentioning

confidence: 99%

SAFFRON: A Semi-Automated Framework for Software Requirements Prioritization

Asif¹,

Masud²,

Easmin³

et al. 2017

ijacsa

View full text Add to dashboard Cite

Abstract-Due to dynamic nature of current software development methods, changes in requirements are embraced and given proper consideration. However, this triggers the rank reversal problem which involves re-prioritizing requirements based on stakeholders' feedback. It incurs significant cost because of time elapsed in large number of human interactions. To solve this issue, a Semi-Automated Framework for soFtware Requirements priOritizatioN (SAFFRON) is presented in this paper. For a particular requirement, SAFFRON predicts appropriate stakeholders' ratings to reduce human interactions. Initially, item-item collaborative filtering is utilized to estimate similarity between new and previously elicited requirements. Using this similarity, stakeholders who are most likely to rate requirements are determined. Afterwards, collaborative filtering based on latent factor model is used to predict ratings of those stakeholders. The proposed approach is implemented and tested on RALIC dataset. The results illustrate consistent correlation, similar to state of the art approaches, with the ground truth. In addition, SAFFRON requires 13.5-27% less human interaction for reprioritizing requirements.

show abstract

“…Many researchers have focused on requirements engineering in order to elicit and prioritize customer values in a systematic fashion [3]- [7]. However, as the software development process reaches the testing phase, customer values that were considered in earlier phases are often not dealt with or prioritized properly.…”

Section: Introductionmentioning

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

Value-Based Requirements Prioritization: Usage Experiences

Cited by 38 publications

References 4 publications

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

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

SAFFRON: A Semi-Automated Framework for Software Requirements Prioritization

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

Contact Info

Product

Resources

About