Guided Derivation of Conceptual Models from User Stories: A Controlled Experiment

Abstract

Context and Motivation]User stories are a popular notation for representing requirements, especially in agile development. Although they represent a cornerstone for developing systems, limited research exists on how user stories are refined into conceptual design. [Question/Problem] We study the process of deriving conceptual models from user stories, which is at the basis of information systems development. We focus our attention on the derivation of a holistic view of structural and interaction aspects, represented via class diagrams and use case diagrams, respectively. In this paper, we examine whether providing guidelines has an effect on the ability of humans to derive complete and valid conceptual models. [Principal Ideas/Results] We design example-based guidelines for the derivation of class and use case diagrams from user stories. Then, we conduct a two-factor, two-treatment controlled experiment with 77 undergraduate students serving as subjects. The results indicate that the guidelines improve the completeness and validity of the conceptual models in cases of medium complexity, although the subjects were neutral on the usefulness of the guidelines. [Contribution] The guidelines may assist analysts in the refinement of user stories. Our initial evidence, besides showing how the guidelines can help junior analysts derive high-quality conceptual models, opens the doors for further studies on the refinement of user stories, and to the investigation of alternative guidelines.

Automated translation from domain knowledge to software model: EXCEL2UML in the tunneling domain

“…A formalization method based on examples is presented in (Bragilovski et al, 2022). The authors propose examplebased guidelines for the derivation of formal requirements out of user stories.…”

Generating multiple conceptual models from behavior-driven development scenarios

“…First, apart from Wautelet et al [22], studies focus on generating just one kind of conceptual model (e.g., use case model [18], [23], [24]; class diagram [25], [26]; goal model [27], [28]; OWL model [29]) whereas in software development different conceptual models are used to cover different perspectives (e.g., data, process, function, interaction) of the software system in development. Second, models are generated from user stories for a particular use (e.g., generating test cases [18], reasoning over requirements [30], obtaining a domain model [29]) or the intended use is implicit (e.g., [31]). There is a need to explore more deeply the different ways that models generated from user stories could be useful in Agile software development.…”