A method for using business process models in the elicitation of user stories

Marina Trkman (2016) A method for using business process models in the elicitation of user stories. PhD thesis.

Preview

PDF Download (20Mb)

Abstract

Agile software development projects often manage user requirements with models that are called user stories. Approaches for eliciting user stories from customer’s existing documentation are missing. Furthermore, proper understanding of user story’s context requires an understanding of execution-order and integration dependencies among user stories, which are also missing. In this thesis we propose so-called BuPUS method which 1) facilitates elicitation of user stories from existing business process models, and 2) supports better understanding of execution-order and integration dependencies among user stories from customer’s existing documentation. The method associates user stories with corresponding BPMN’s activity elements, or with corresponding text-written use case model’s events. We defined three levels of association granularity: a user story can be more abstract, approximately equal to, or more detailed than its associated business process model’s event/activity element. In our experiments we evaluated these three levels. We run two experiments. We applied comprehension, problem-solving and recall tasks to evaluate the hypotheses which refer to understanding of the dependencies. On the other hand, we measured user story elicitation’s effectiveness with counting correctly defined user stories. The statistical results provide support for eight out of eleven of the hypotheses. The results of our first experiment show, that understanding of the execution-order and integration dependencies among user stories, when associated business process models are available, is significantly greater. In our second experiment, we compared text-written use case model and BPMN model. There appears to be greater understanding of the execution-order dependencies when using BPMN models, while there were no significant differences in understanding integration dependencies. Similarly, for the elicitation of user stories there are no significant differences when using either of the mentioned models.

Actions (login required)