User Story Writing in Crowd Requirements Engineering: The Case of a Web Application for Sports Tournament Planning
Abel Menkveld, Sjaak Brinkkemper, Fabiano Dalpiaz
Abstract
Abel Menkveld, Sjaak Brinkkemper, Fabiano Dalpiaz
Abstract
Although users feel more engaged when they are involved in the elicitation, negotiation and prioritization of requirements for a product or service they are using, the quality of crowdsourced requirements remains an issue. Simple notations like user stories have been highly adopted by practitioners in agile development to capture requirements for a software product, but their utilization in crowdsourced requirements engineering is still scarce. Through a case study of a web application for sports tournament planning, we investigate how a dedicated platform for user story writing in crowd requirements engineering is valued by its users and we show that the delivered requirements are not inferior to those written by professionals.
OpenAlex reports 17 citations for this work. Citation counts describe recorded attention and do not establish research quality.
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.
Although users feel more engaged when they are involved in the elicitation, negotiation and prioritization of requirements for a product or service they are using, the quality of crowdsourced requirements remains an issue. Simple notations like user stories have been highly adopted by practitioners in agile development to capture requirements for a software product, but their utilization in crowdsourced requirements engineering is still scarce. Through a case study of a web application for sports tournament planning, we investigate how a dedicated platform for user story writing in crowd requirements engineering is valued by its users and we show that the delivered requirements are not inferior to those written by professionals.
Key concepts: Requirements elicitation, User story, Requirement, Requirements engineering, Computer science, User requirements document, Agile software development, Requirements analysis