Towards a Generation of Class Diagram from User Stories in Agile Methods

User Stories and Natural Language Processing: A Systematic Literature Review

“…Some studies were authored/co-authored by the same person, indicating the existence of an active research group in this field. [33] Identify ambiguous user stories [34] Define and measure quality factors from user stories [4], [35] Obtain a security defect reporting form from user stories [36] Indicate duplication between user stories [37] Generate model/artifact Generate a test case from user stories [38]- [43] Generate a class diagram from user stories [44], [45] Generate a sequence diagram from user stories [46] Generate a use case diagram from user stories [47]- [49] Generate a use case scenario from user stories [50] Generate a multi-agent system from user stories [51] Generate a source code from user stories [40] Generate a BPMN diagram from user stories [40] Identify the key abstractions To understand the semantic connection in user stories [52]- [54] Identify topics and summarizing user stories [55], [56] Construct a goal model from a set of user stories. [57] Define ontology for user stories [58] Extract the conceptual model of user stories [59], [60] To find the linguistic structure of user stories [61] Prioritizing and estimation of user story complexity [62], [63] Extracting user stories from text [64]- [66] Trace links between model/NL requirements Tracking the development status of user stories from software artifacts [67] Identify the type of dependency of user stories [68] Traceability user stories and software artifact [69]…”

“…The user story can be either input or output of the generated artifact. Fourteen studies reported methods for generating software model/artifacts from user stories, that is, generating a test case from user stories [35][36][37][38][39]64], generating class diagrams from user stories [40,41], generating sequence diagrams from user stories [46], generating a use case diagram from user stories [43][44][45], generating a use case scenario from user stories [50], generating a multi-agent system from user stories [51], generating a source code from user stories [40], and generating BPMN diagrams from user stories [40]. The software artifact generation aims to cut time and cost in software development and avoid inconsistencies, incompleteness, and incorrect requirements and artifact/software models.…”

“…This technique was used to generate use case diagrams [48], sequence diagrams [46], and use case scenarios [50] from user stories. The same approach was taken by [44], [45] to generate class diagrams. In generating use case diagrams, [47] categorized the aspects of what in user stories into three categories, namely task, capability, and goal, to produce more detailed use case diagrams involving <include> and <extend> as dependency relationships.…”

From User Stories to UML Diagrams Driven by Ontological and Production Model

“…In our previous approach [19], our objective was to define the extraction rules of the object-oriented design elements, such as actors, classes, attributes, operations of classes, and associations. These components were essential to generate a class diagram, presented in an XMI file and also in a PNG image.…”

“…To extract the design elements which constitute the class diagram, from a set of user stories, we followed the steps described in the algorithm presented below: Based on rules previously defined in [19], we have defined a production rules written in prolog language to extract actors, classes, and associations which connect classes (lines 8-10). The facts are provided from NLP tool that provide the nouns, the verbs and typed dependencies (lines 3-7).…”