SAFFRON: A Semi-Automated Framework for Software Requirements Prioritization

Abstract

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.

A Data Mining Technique to Improve Configuration Prioritization Framework for Component-Based Systems: An Empirical Study

“…Prioritizing requirements by focusing on stakeholders' feedback results in a noteworthy increase in development cost because of the time elapsed in several human interactions. In another work, a semi-automated framework has been presented to predict the ratings to reduce human interactions [7]. A prioritization method known as case-based ranking integrates the project's stakeholders' needs with requirements ordering approximations, calculated through automated techniques [42].…”

Requirement prioritization framework using case‐based reasoning: A mining‐based approach

“…Because faulty specification and selection increase the complexity, human interaction demands, inconsistency, and ambiguity in configurable CBSs after modification, this affects all CBSD operations, particularly component prioritizing activities. The attributes which impact and help to resolve these issues highlighted in existing literature are described below (Asif et al, 2017;Ayala et al, 2018;Graics et al, 2020;Heikkilä et al, 2017;Imam Ya'u & Nura Yusuf, 2018;Khan et al, 2016;Kyaw Zaw & Vasupongayya, 2019;Noei et al, 2019).…”