Crowd-Based Requirements Engineering Research Articles

Joint Impact of Agents and Services in Enhancing Software Requirements Engineering

Requirements engineering (RE) is a significant aspect of system development stages in generating reliable software (SW). Despite RE’s decisive impact on project success, SW systems still fail since there is a perplexity in sorting out requirements correctly. Researchers have tried several paradigms to deal with the specified challenges, such as agent-oriented RE (AORE), model-based RE, and service-oriented RE (SORE). By investigating the limitations of the independent use of these paradigms, this research sets an objective that proposes a framework which integrates the two paradigms (agent and service) on top of social media to enhance the SW RE processes. Thus, the research addresses challenges in gathering adequate requirements, detecting alignment between business requirements and SW products, prioritizing requirements, and recommending innovative ideas. The research has mainly adopted an empirical research methodology for SW engineering. Accordingly, two distinct expert groups have been formed based on their previous experience in AORE and SORE, respectively. The experts have been selected from enterprises and academic institutions, and they participated in our case study. After performing the necessary assessment based on specified criteria, those experts in the first group have reported that CASCRE (Collaboration of Agents and Services for Crowd-based Requirements Engineering) with a score of 93.7% is found to be better than that of AORE with a score of 88.7%. Moreover, experts in the second group have declared that CASCRE, with a score of 92.3%, is better than SORE, with a score of 83.7%. In both cases, improvements have been observed, which reveals that the synergy of the CASCRE features has a better impact on the RE process than utilizing individual approaches. Moreover, in order to demonstrate the applicability of CASCRE, feedback has been gathered from a focused crowd of local pharmaceuticals using a mini-prototype. Accordingly, 250 requirements related comments have been gathered from the discussion forum, and 1400 keywords were generated. Then, after performing a sentiment analysis using NLP algorithms, the result was demonstrated to experts. Therefore, 93% of gurus strongly agreed on the applicability of CASCRE in real projects.

Crowd-based requirements elicitation via pull feedback: method and case studies

Crowd-based Requirements Engineering (CrowdRE) promotes the active involvement of a large number of stakeholders in RE activities. A prominent strand of CrowdRE research concerns the creation and use of online platforms for a crowd of stakeholders to formulate ideas, which serve as an additional input for requirements elicitation. Most of the reported case studies are of small size, and they analyze the size of the crowd, rather than the quality of the collected ideas. By means of an iterative design that includes three case studies conducted at two organizations, we present the CREUS method for crowd-based elicitation via user stories. Besides reporting the details of these case studies and quantitative results on the number of participants, ideas, votes, etc., a key contribution of this paper is a qualitative analysis of the elicited ideas. To analyze the quality of the user stories, we apply criteria from the Quality User Story framework, we calculate automated text readability metrics, and we check for the presence of vague words. We also study whether the user stories can be linked to software qualities, and the specificity of the ideas. Based on the results, we distill six key findings regarding CREUS and, more generally, for CrowdRE via pull feedback.

Research Efforts and Challenges in Crowd-based Requirements Engineering: A Review

Eliciting software system development requirements is a challenging task as the information is from various resources. The most constructive resource is the stakeholders of the system to be developed. It is critical yet time-consuming to capture essential requirements to realize a reliable and workable software system. The crowd-based Requirements Engineering (crowd-based RE) approach adapts the crowdsourcing technique to access an extensive range of stakeholders and save time, especially for the generic type system with no clear stakeholder. This paper presents current research efforts and challenges in crowd-based RE. A systematic literature review method is adopted to explore literature based on two specific research questions. The first question aimed at identifying research efforts on crowd-based RE, and the second question focused on the main challenges discovered in pursuing crowd-based RE. The findings from the literature review show that many efforts have been made to explore and further improve crowd-based RE. This paper provides a foundation to pursue research in improving crowdsourcing techniques for the benefit of requirements engineering.

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.