RePizer: a framework for prioritization of software requirements

A systematic literature review on requirement prioritization techniques and their empirical evaluation

“…• [63] proposed an AHP-based prioritization approach, RePizer, that provides a holistic view of the entire project to ensure the judicious of the software development process. The overview of the softwere development process by RePizer is based on the RePizer in terms of expected accuracy and ease of use, it is also considered the guidelines of planning game (PG).…”

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

“…Historical information is essential for prioritization strategies for prioritizing and selecting requirements and test cases. Khan et al (2016) identified that the requirement prioritization process improved the use of historical data; a framework strategy was then provided for storing and retrieving historical information requirements for ambiguities removal. Arrieta et al (2016) outlined a CBS for the accurate selection and execution of test cases by validating the requirements of the software, identifying a maximum error, and validating all configurations using a weighted average method of requirements.…”

“…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).…”

WhaleRank: an optimisation based ranking approach for software requirements prioritisation

“…Comparison of the IPA approach with the HAM-based approach in terms of three parameters, namely time-consumption, accuracy, and ease of use proved that IPA outperformed other approaches, but there was no hierarchical relationship between the functional and the non-functional requirements. Khan et al (2016) proposed RePizer, a framework for prioritisation of software requirements. It assisted the engineer's inaccurate decision-making through the retrieval of the historical data.…”

“…The main challenge is the domain knowledge for prioritising the requirements, which raises the need for the human interference in the decision-making process (Babar et al, 2015), this, in turn, poses the need for the automatic selection (Khan et al, 2016) of performing the prioritising technique.…”