Configuring crowdsourcing for requirements elicitation

Abstract

Abstract-Crowdsourcing is an emerging paradigm which utilises the power of the crowd in contributing information and solving problems. Crowdsourcing can support requirements elicitation, especially for systems used by a wide range of users and working in a dynamic context where requirements evolve regularly. For such systems, traditional elicitation methods are typically costly and limited in catering for the high diversity, scale and volatility of requirements. In this paper, we advocate the use of crowdsourcing for requirements elicitation and investigate ways to configure crowdsourcing to improve the quality of elicited requirements. To confirm and enhance our argument, we follow an empirical approach starting with two focus groups involving 14 participants, users and developers, followed by an online expert survey involving 34 participants from the Requirements Engineering community. We discuss our findings and present a set of challenges of applying crowdsourcing to aid requirements engineering with a focus on the elicitation stage.

REfine: A gamified platform for participatory requirements engineering

“…These approaches, however, do not focus on the provision of (long-term) incentives. Hosseini et al [22], [23] identify the quality attributes that affect the effectiveness of crowdsourcing in requirements elicitation, such as largeness, diversity, competence, motivation, etc.…”

The Use of Microtasks in Crowdsourcing Software Development

“…For this, we select two incipient aspects of the literature: i) "how the CS configuration affects the microtasks?". In this way, we investigate how the size of the crowd impacts the microtasks and the coordination process [5], [6]. And it was analyzed the "what is the complexity of CS projects?…”

“…In this way, the literature has been constantly updated with publications to understand the benefits, challenges, and configuration of CS software development [3], [5], [6]. Because of this scenery, L'Erario et al [7] presented the results of CS teaching and learning among undergraduate students.…”

“…Because microtasks concentrate small portions of work, CS projects tend to have a lot of microtasks, and thus may present difficulties for the development and coordination of work [6]. In addition, there is difficulty in identifying what effectively is a microtasks and what its influence on software projects [5]. The lack of focused studies on the subject of microtask poses several challenges for the application of CS.…”

CRAFT: A Crowd-Annotated Feedback Technique

“…This means that requirements are directly elicited from the masses who currently use the system-as-is, so that these can be incorporated into software evolution processes for the masses who will use the systemto-be. We have already investigated crowdsourcing and its potential in the domain of requirements engineering [8], [9]. However, although some studies have been conducted on crowdsourcing user annotation [10], little work exists to date on crowd-based requirements annotation.…”