The Crowd in Requirements Engineering: The Landscape and Challenges
Authors: Groen, E.C. et al.
Journal: IEEE Software
Volume: 34
Issue: 2
Pages: 44-52
ISSN: 0740-7459
DOI: 10.1109/MS.2017.33
Abstract: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.
https://eprints.bournemouth.ac.uk/28519/
Source: Scopus
The Crowd in Requirements Engineering The Landscape and Challenges
Authors: Groen, E.C. et al.
Journal: IEEE SOFTWARE
Volume: 34
Issue: 2
Pages: 44-52
eISSN: 1937-4194
ISSN: 0740-7459
DOI: 10.1109/MS.2017.33
https://eprints.bournemouth.ac.uk/28519/
Source: Web of Science (Lite)
The Crowd in Requirements Engineering: The Landscape and Challenges
Authors: Groen, E. et al.
Journal: IEEE Software
Volume: 34
Issue: 2
Pages: 44-52
Publisher: Institute of Electrical and Electronics Engineers (IEEE)
ISSN: 0740-7459
DOI: 10.1109/MS.2017.33
Abstract: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.
https://eprints.bournemouth.ac.uk/28519/
Source: Manual
The Crowd in Requirements Engineering: The Landscape and Challenges
Authors: Groen, E. et al.
Journal: IEEE Software
Volume: 34
Issue: 2
Pages: 44-52
ISSN: 0740-7459
Abstract: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.
https://eprints.bournemouth.ac.uk/28519/
Source: BURO EPrints