Handling Numerous Stakeholders Requirements A Research Agenda and\n Preliminary Outcomes
Saurabh Malgaonkar, Sherlock A. Licorish, Bastin Tony Roy Savarimuthu
Abstract
Open-access reader
Saurabh Malgaonkar, Sherlock A. Licorish, Bastin Tony Roy Savarimuthu
Abstract
Open-access reader
This research aims to design and develop a new requirements prioritization\napproach for analyzing and prioritizing stakeholders requirements which are\nmentioned in the feedback for software products. This paper presents a PhD\nresearch agenda and preliminary outcomes from the early analysis. A roadmap to\nthe proposed research methodology that is to be followed to achieve the\ntargeted outcomes is also outlined. Outcomes to date show that the requirements\nprioritization problem has been researched extensively, however, gaps still\nremain when considering techniques that handle a large number of crowdsourced\nrequirements. Furthermore, requirements prioritization as a problem affects\nmany domains beyond software engineering. Hence, knowledge from other fields\ncould be useful for informing requirements prioritization practice in the\nsoftware engineering space.\n
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
This research aims to design and develop a new requirements prioritization\napproach for analyzing and prioritizing stakeholders requirements which are\nmentioned in the feedback for software products. This paper presents a PhD\nresearch agenda and preliminary outcomes from the early analysis. A roadmap to\nthe proposed research methodology that is to be followed to achieve the\ntargeted outcomes is also outlined. Outcomes to date show that the requirements\nprioritization problem has been researched extensively, however, gaps still\nremain when considering techniques that handle a large number of crowdsourced\nrequirements. Furthermore, requirements prioritization as a problem affects\nmany domains beyond software engineering. Hence, knowledge from other fields\ncould be useful for informing requirements prioritization practice in the\nsoftware engineering space.\n
Key concepts: Requirement prioritization, Prioritization, Requirements engineering, Requirements analysis, Software requirements, Computer science, Requirements elicitation, Requirements management