Requirements Engineering (RE) has undergone several transitions over the years, from
traditional methods to agile approaches emphasising increased automation. In many …

Context: Processing Software Requirement Specifications (SRS) manually takes a much
longer time for requirement analysts in software engineering. Researchers have been …

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 …

Functional and non-functional requirements are equally important in software engineering.
Both of them are mixed together within the same software requirement document. Usually …

Model-driven requirements engineering is gaining enormous popularity in recent years.
Unified Modeling Language (UML) is widely used in the software industry for specifying …

A sequence diagram is one of UML models that are usually used within the analysis phase
in software system development. Since generating such sequence diagrams is performed …

The process of transformation from informal requirements stated in natural language into a
formal specification such as Unified Modeling Language (UML) is an important challenge …

Every process within software development refers to a specific set of input and output
artifacts. Each artifact models specific design information of a system, yet they complement …

User stories are informal, non-technical descriptions of features from a user's perspective
that guide collaboration and iterative development in Agile projects. However, ambiguities in …

A goal model, which is one of the common requirements models, has advantages of
formalizing and visualizing results of requirements analysis. The model regards a …