Figure 3 - uploaded by Arjen Spaans
Content may be subject to copyright.
Source publication
![Figure 3.2: ABRE-QM metamodel as defined by Femmer [18, p. 42]](profile/Arjen-Spaans/publication/331011737/figure/fig2/AS:726459303882752@1550212803699/ABRE-QM-metamodel-as-defined-by-Femmer-18-p-42_Q320.jpg)
The requirements within agile software development methodologies are often documented
in the user story format. The quality of these user stories is regarded as crucial
for the success of agile software development projects. So far, we have seen limited
research regarding user story quality. Also, the limited research is reflected by the small
numb...
Contexts in source publication
Context 1
... a Role , I want Means , so that Rationale " Figure 3.1 shows the template with the other components of a user story. The user story, therefore, describes who wants the functionality, what the stakeholders want regarding the functionality of the system and why the stakeholders want the functionally [50, p. 1]. ...
Context 2
... user story, therefore, describes who wants the functionality, what the stakeholders want regarding the functionality of the system and why the stakeholders want the functionally [50, p. 1]. In the following paragraphs we outline the association between the who, the what and the way and our user story metamodel as shown in figure 3.1: ...
Context 3
... ABRE-QM is an instance of the several elements [18, p. 42]. Figure 3.2 provides an overview of the elements and the relationships among the elements within the AB- QM metamodel. ...
Context 4
... instantiate each of the elements within the context of this thesis. Figure 3.3 provides an overview regarding the ABUS-QM within the user story and Scrum context. ...
Context 5
... 3.3 provides an overview regarding the ABUS-QM within the user story and Scrum context. We will explain each element within the model of figure 3.3, limiting its scope if necessary: ...
Context 6
... we can map all of the mentioned generic activities to the product owner or the development team and for simplicity reasons, we only consider the two roles mentioned previously. Figure 3.3 illustrates the two Scrum-roles. ...
Similar publications
![Fig 3: Scrum Process [3]](profile/Timothy-Malche/publication/335810597/figure/fig1/AS:802858161160195@1568427710617/Scrum-Process-3_Q320.jpg)
![Fig 4: Feature Driven Development Process [3]](profile/Timothy-Malche/publication/335810597/figure/fig2/AS:802858161172480@1568427710652/Feature-Driven-Development-Process-3_Q320.jpg)
![Fig 5: DSDM Process Diagram [3]](profile/Timothy-Malche/publication/335810597/figure/fig3/AS:802858161164290@1568427710676/DSDM-Process-Diagram-3_Q320.jpg)
![Fig 6: ASD Life Cycle [3]](profile/Timothy-Malche/publication/335810597/figure/fig4/AS:802858161164291@1568427710710/ASD-Life-Cycle-3_Q320.jpg)
![Fig 12: Agile Unified Process Phases [30] III. COMPARISON BETWEEN AGILE...](profile/Timothy-Malche/publication/335810597/figure/fig5/AS:802858161172481@1568427710744/Agile-Unified-Process-Phases-30-III-COMPARISON-BETWEEN-AGILE-METHODOLOGIES-There-are_Q320.jpg)
Protocol for a Systematic Mapping of the Literature, which aims to identify and classify the estimations techniques used in software development agile methodologies based on the results found, and to compare their estimation accuracies against those obtained in traditional software development methodologies.
Hybrid methodologies can be applied in the software industry, particularly, in business sectors to cope with dilemmas in large-scale software projects. Rapid change and increasing software criticality drive organizations to balance between agility and discipline in software development projects. In order to utilize the benefits of both approaches i...
The field of software engineering is growing rapidly due to
increased change of customers’ requirements and progress in
technologies. Agile software development (ASD) have
substituted the conventional Software development
methodologies to enhance the software productivity through
short increments and increased user satisfaction. The purpose
of this...
Application of agile software development methodologies in large-scale organizations is becoming increasingly common. However, working with multiple teams and on multiple products at the same time yields higher coordination and communication efforts compared to single-team settings for which agile methodologies have been designed originally. With t...
Citations
... However, users of our technique may assess the quality of their stories before applying it. For example, user stories might be checked using more advanced quality assessments as proposed in other research, e.g., [29,41]. ...
Textual user stories capture interactions of users with the system as high-level requirements. However, user stories are typically rather short and backlogs can include many stories. This makes it hard to (a) maintain user stories and backlogs, (b) fully understand the scope of a software project without a detailed analysis of the backlog, and (c) analyse how user stories impact design decisions during sprint planning and implementation. This paper proposes a technique to automatically transform textual user stories into visual use case scenarios in the form of robustness diagrams (a semi-formal scenario-based visualisation of workflows). In addition to creating diagrams for individual stories, the technique allows combining diagrams of multiple stories into one diagram to visualise workflows within sets of stories (e.g., a backlog). Moreover, the technique supports "viewpoint-based" diagrams, i.e., diagrams that show relationships between actors, domain entities and user interfaces starting from a diagram element (e.g., an actor) selected by the analyst. The technique utilises natural language processing and rule-based transformations. We evaluated the technique with more than 1,400 user stories from 22 backlogs and show that (a) the technique generates syntactically valid robustness diagrams, and (b) the quality of automatically generated robustness diagrams compares to the quality of diagrams created by human experts, but depends on the quality of the textual user stories.
