End-user driven feedback prioritization

End-user feedback is becoming more important for the evolution of software systems. There exist various communication channels for end-users (app stores, social networks) which allow them to express their experiences and requirements regarding a software application. End-users communicate a large amount of feedback via these channels which leads to open issues regarding the use of end-user feedback for software development, maintenance and evolution. This includes investigating how to identify relevant feedback scattered across different feedback channels and how to determine the priority of the feedback issues communicated. In this research preview paper, we discuss ideas for enduser driven feedback prioritization.Peer ReviewedPostprint (published version

Collaborating with the Crowd for Software Requirements Engineering: A Literature Review

Requirements engineering (RE) represents a decisive success factor in software development. The novel approach of crowd-based RE seeks to overcome shortcomings of traditional RE practices such as the resource intensiveness and selection bias of stakeholder workshops or interviews. Two streams of research on crowd-based RE can be observed in literature: data-driven approaches that extract requirements from user feedback or analytics data and collaborative approaches in which requirements are collectively developed by a crowd of software users. As yet, research surveying the state of crowd-based RE does not put particular emphasis on collaborative approaches, despite collaborative crowdsourcing being particularly suited for joint ideation and complex problem-solving tasks. Addressing this gap, we conduct a structured literature review to identify the RE activities supported by collaborative crowd-based approaches. Our research provides a systematic overview of the domain of collaborative crowd-based RE and guides researchers and practitioners in increasing user involvement in RE

Bridging the Gap Between Stakeholder and Software Products: A Review of Software Requirement Engineering Techniques

Effective software requirement engineering plays a crucial role in bridging the gap between stakeholders and software products. The success of any software project heavily relies on accurately capturing, analyzing, and documenting stakeholders' needs and expectations. This article provides a comprehensive review of various software requirement engineering techniques that facilitate the alignment of stakeholder requirements with software product development. Software requirements are extracted from a variety of stakeholders, but the decision of "what to develop" is a difficult one. Stakeholders' lack of clarity about what they want makes requirement elicitation a difficult and vital task. It explores the significance of understanding stakeholders' perspectives, discusses popular requirement engineering approaches, and highlights their strengths and limitations. The article concludes by emphasizing the importance of selecting appropriate requirement engineering techniques based on the project's context and offers recommendations for future research in this domain

GARUSO: a gamification approach for involving stakeholders outside organizational reach in requirements engineering

Stakeholder participation is a key success factor of Requirements Engineering (RE). Typically, the techniques used for identifying and involving stakeholders in RE assume that stakeholders can be identified among the members of the organizations involved when a software system is ordered, developed or maintained—and that these stakeholders can be told or even mandated to contribute. However, these assumptions no longer hold for many of today’s software systems where significant stakeholders (in particular, end-users and people affected by a system) are outside organizational reach: They are neither known nor can they easily be identified in the involved organizations nor can they be told to participate in RE activities. We have developed the GARUSO approach to address this problem. It uses a strategy for identifying stakeholders outside organizational reach and a social media platform that applies gamification for motivating these stakeholders to participate in RE activities. In this article, we describe the GARUSO approach and report on its empirical evaluation. We found that the identification strategy attracted a crowd of stakeholders outside organizational reach to the GARUSO platform and motivated them to participate voluntarily in collaborative RE activities. From our findings, we derived a first set of design principles on how to involve stakeholders outside organizational reach in RE. Our work expands the body of knowledge on crowd RE regarding stakeholders outside organizational reach

Requirements Prioritization Techniques for Global Software Engineering

Increase in globalization of the industry of software requires an exploration of requirements engineering (RE) in software development institutes at multiple locations. Requirements engineering task is very complicated when it is performed at single site, but it becomes too much complex when stakeholder groups define well-designed requirements under language, time zone and cultural limits. Requirements prioritization (RP) is considered as an imperative part of software requirements engineering in which requirements are ranked to develop best-quality software. In this research, a comparative study of the requirements prioritization techniques was done to overcome the challenges initiated by the corporal distribution of stakeholders within the organization at multiple locations. The objective of this study was to make a comparison between five techniques for prioritizing software requirements and to discuss the results for global software engineering. The selected techniques were Analytic Hierarchy Process (AHP), Cumulative Voting (CV), Value Oriented Prioritization (VOP), Binary Search Tree (BST), and Numerical Assignment Technique (NAT). At the end of the research a framework for Global Software Engineering (GSE) was proposed to prioritize the requirements for stakeholders at distributed locations

The Crowd in Requirements Engineering: The Landscape and Challenges

Crowd-based requirements engineering (CrowdRE) could significantly change RE. Performing RE activities such as elicitation with the crowd of stakeholders turns RE into a participatory effort, leads to more accurate requirements, and ultimately boosts software quality. Although any stakeholder in the crowd can contribute, CrowdRE emphasizes one stakeholder group whose role is often trivialized: users. CrowdRE empowers the management of requirements, such as their prioritization and segmentation, in a dynamic, evolved style through collecting and harnessing a continuous flow of user feedback and monitoring data on the usage context. To analyze the large amount of data obtained from the crowd, automated approaches are key. This article presents current research topics in CrowdRE; discusses the benefits, challenges, and lessons learned from projects and experiments; and assesses how to apply the methods and tools in industrial contexts. This article is part of a special issue on Crowdsourcing for Software Engineering

Requirements volatility in multicultural situational contexts

Requirements volatility refers to additions, deletions, and modifications of requirements during the system development life cycle. Different approaches in software development, including Agile and DevOps, have addressed requirements volatility by increasing user participation throughout the whole development process. In this paper, we analyse requirements volatility from a situational context angle with the aim to increase understanding of the role of culture and cultural diversity in a multicultural requirements elicitation process. Research on the situational context in Requirements Engineering (RE) is rather limited, despite the recognized importance of RE and requirements elicitation for improving the quality of the final system and software product. This paper builds on an extensive literature review demonstrating the importance of raising awareness and understanding of the role of culture and cultural diversity for requirements volatility, as one of the most significant situational factors in the requirements elicitation process, with the aim to improve the whole systems development process as well as the resulting products and services. The paper concludes with the presentation of the Requirements Cultural Volatility Framework which aims to reveal potential conflicts that may occur in requirements elicitation on a multiplicity of cultural dimensions, The framework proposes actions to be taken in order to address the conflicts and point out expected benefits on each dimension

Canary: Extracting Requirements-Related Information from Online Discussions

Online discussions about software applications generate a large amount of requirements-related information. This information can potentially be usefully applied in requirements engineering; however currently, there are few systematic approaches for extracting such information. To address this gap, we propose Canary, an approach for extracting and querying requirements-related information in online discussions. The highlight of our approach is a high-level query language that combines aspects of both requirements and discussion in online forums. We give the semantics of the query language in terms of relational databases and SQL. We demonstrate the usefulness of the language using examples on real data extracted from online discussions. Our approach relies on human annotations of online discussions. We highlight the subtleties involved in interpreting the content in online discussions and the assumptions and choices we made to effectively address them. We demonstrate the feasibility of generating high-quality annotations by obtaining them from lay Amazon Mechanical Turk users