Software Engineering: User Stories to Use Case Scenarios Review

This paper reviews a software engineering methodology focused on transitioning from user stories to use case scenarios using a generative approach. The study evaluates the use of user stories to create case studies for a generative process, specifically proposing a generative approach for developing robustness diagrams. It highlights the increasing use of NLP techniques in software engineering and reviews previous work related to requirement engineering methodologies, including business process framework generation and comparative models for user stories. The review identifies user stories as an effective technique for software development but notes potential issues with incorrect documentation. The author designed and implemented a robustness diagram to better understand user stories, discussing the key aspects of robustness and user stories and determining the relationships between produced entities. The conclusion emphasizes the role of the developed robustness diagram in improving software development performance.

F R O M U S E R S T O R I E S T O U S E C A S E
S C E N A R I O S
T O WA R D S A G E N E R AT I V E A P P R O A C H
Software engineering
methodology

Introduction
The title of the paper is “From User Stories
to Use Case Scenarios Towards a Generative
Approach”.
This paper is based on software engineering
methodology (Gilson, & Irwin, 2018).
The goal of this study is to evaluate user
stories to utilize case studies towards the
generative process.
The researcher proposed a generative
approach for creating robustness diagrams.

Motivation and related work
It is analysed that the use of NLP techniques
are increasing rapidly that help engineer for
performing their activities.
The previous paper conducted a literature
review to understand the mining approaches
for software design.
Most of the recent investigations evaluated
the work related to the requirement and
focused on the engineering methodologies.

Motivation and related work
Friedrich, Mendling, & Puhlmann, (2011)
developed and proposed the generation of
business process framework.
This framework provided a way to the
companies for improving the accuracy of
their business.
After evaluating their work it is identified
that they were suffered from some textual
description (Stavru, 2014).

Motivation and related work
Dybå, & Dingsøyr, (2008) proposed a
comparative model for user stories which is
also based on the NLP process.
In which the authors critically reviewed the
conceptual framework.
From this paper, it is identified that agile
methodology and user stories both are very
common approaches used by companies.
Moreover, user stories are effective
techniques for developing reliable software.

Techniques for agile requirement analysis
In this section, the author examined the
various kinds of techniques used in the agile
requirements.
User stories are a very appropriate technique
in the development of software related
projects.
But, a significant enhancement overhead can
be occurred in the user stories because of
incorrect documentation.

Techniques for agile requirement analysis
It is identified that user stories can be
expressed around 80 synthetic variants in the
organizations.
In order to understand the concept of user
stories, the author developed a flow chart.
Moreover, a robustness chart is also
proposed in order to express simplified
collaboration figure.

Generate Robustness figure
In this section, the author designed and
implemented a robustness diagram for better
understanding of user stories.
There are various sections included in this
part, for example, an overview of the
approach, implementation, and examples.
Therefore, the proposed system by the
authors helped for understanding the concept
of user stories.

Discussion
In this section, the author discussed and
reviewed the key aspects of robustness and
user stories.
The author believed that the developed
robustness process provided a platform for
verifying the concept of user stories.
The authors also able for determining the
relation between the produced entities.

Discussion
The developed approach used an effective
analysis process based on user stories.
The researcher achieved the aim and purpose
of this investigation and described the key
aspects of user stories.
Moreover, the robustness diagram also
helped the author for expressing and
verifying the behavioural case in terms of
controls, user stories and boundaries.

Conclusion
This paper is based on the user stories and
the authors critically review the concept of
user stories.
It is concluded that the developed robustness
diagram helped the industries for improving
the performance of software development.
Moreover, the authors also described the
results and opinions of other papers in order
to understand the key factors of user stories.

References
Gilson, F., & Irwin, C. (2018). From User Stories to Use Case
Scenarios towards a Generative Approach. In 2018 25th
Australasian Software Engineering Conference (ASWEC),
12(2), 61-65.
Friedrich, F., Mendling, J., & Puhlmann, F. (2011). Process
model generation from natural language text.
In International Conference on Advanced Information
Systems Engineering, 8(2), 482-496.
Dybå, T., & Dingsøyr, T. (2008). Empirical studies of agile
software development: A systematic review. Information and
software technology, 50(9-10), 833-859.
Stavru, S. (2014). A critical examination of recent industrial
surveys on agile method usage. Journal of Systems and
Software, 94(2), 87-97.