An Impact Study of Business Process Models for Requirements Elicitation in XP

Requirements elicitation techniques: a systematic literature review based on the maturity of the techniques

“…Additionally, use cases are an effective technique if they are used as a secondary technique. According to the authors in [161, 175–177], the workshops were considered effective because these help stakeholders to negotiate and collaborate in an effective way. Duggan and Thachenkary [157] affirmed that JAD is an effective technique for eliciting quality requirements. JAD is often used with rapid AD, an iterative and incremental approach for improving the quality and speed of a system design by supporting it with structured methods and computer aided software engineering (CASE) tools. Researches by the authors in [82, 84–86, 164] state that the focus group technique is effective because it promotes the discussion among stakeholder with the aim of formalising the requirements. Niknafs and Berry [93] and Konaté et al [94] consider that brainstorming is an effective technique for eliciting needs by producing, voting, organising, and reviewing in a collaborative way all the ideas. Ordóñez et al [152] show the effectiveness of the business process models compared with user stories in software agile development. The results indicate a higher effectiveness for models as a primary technique because these enable analysts to clearly specify the stakeholders’ needs and business objectives. Isabirye and Flowerday [164] propose to use the user stories as a primary technique because the user stories take advantage of the usual mode of communication among stakeholders in order to obtain a complete understanding of the problem and its context (e.g.…”

“…Ordóñez et al [152] show the effectiveness of the business process models compared with user stories in software agile development. The results indicate a higher effectiveness for models as a primary technique because these enable analysts to clearly specify the stakeholders’ needs and business objectives.…”

“…• Niknafs and Berry [93] and Konaté et al [94] consider that brainstorming is an effective technique for eliciting needs by producing, voting, organising, and reviewing in a collaborative way all the ideas. • Ordóñez et al [152] show the effectiveness of the business process models compared with user stories in software agile development. The results indicate a higher effectiveness for models as a primary technique because these enable analysts to clearly specify the stakeholders' needs and business objectives.…”

Ambiguity in user stories: A systematic literature review

“…Despite empirical support for these benefits (e.g., [18,19,25,26]), several studies showed that user stories are prone to ambiguity [24,[26][27][28]. Based on these studies, we describe ambiguity as problems regarding the articulation of requirements as user stories, which cause doubtful, imprecise, and multiple interpretations of these requirements.…”

“…While the emphasis on informal communication using verbal language (as opposed to, for instance, formal or semi-formal requirements models) certainly provides advantages with respect to user involvement [24,27], it can also lead to ambiguity in what exactly is expressed by the user story, as illustrated by our example. Causes of such ambiguity could be differences in domain knowledge, differences in terminology used to articulate that knowledge, or just being careless or sloppy when formulating user stories.…”