On the generation of requirements specifications from software engineering models: A systematic literature review

Nicolás, Joaquín; Toval, Ambrosio

doi:10.1016/j.infsof.2009.04.001

Cited by 94 publications

(55 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Thus, the CIM models only model the software requirements of the enterprise without considering other enterprise views; i.e., they only model what they are going to transform. There are two sub-categories: one related to the reutilisation of models generated with i* language (Nicolás & Toval, 2009), and the other based on the processing of natural language specifications to obtain PIM models.…”

Section: Cim2pim Work Focused On Software Requirements Modellingmentioning

confidence: 99%

Reusing enterprise models to build platform independent computer models

Pazos

Chalmeta

2016

Inf Syst E-Bus Manage

View full text Add to dashboard Cite

Section: Cim2pim Work Focused On Software Requirements Modellingmentioning

confidence: 99%

Reusing enterprise models to build platform independent computer models

Pazos

Chalmeta

2016

Inf Syst E-Bus Manage

View full text Add to dashboard Cite

“…In a similar way, Schatz et al [23] and Davis [24] propose to combine textbased and model-based requirements. Nicolás and Toval even explicitly discuss the value of generation in this context [25]. They argue that generation reduces the effort and, at the same time, increases the quality and traceability of the requirements.…”

Section: The Value Of Requirements Generationmentioning

confidence: 99%

A semi-automated approach for generating natural language requirements documents based on business process models

Aysolmaz

Leopold

Reijers

et al. 2018

Information and Software Technology

View full text Add to dashboard Cite

Context: The analysis of requirements for business-related software systems is often supported by using business process models. However, the final requirements are typically still specified in natural language.This means that the knowledge captured in process models must be consistently transferred to the specified requirements. Possible inconsistencies between process models and requirements represent a serious threat for the successful development of the software system and may require the repetition of process analysis activities.Objective: The objective of this paper is to address the problem of inconsistency between process models and natural language requirements in the context of software development. Method:We define a semi-automated approach that consists of a process model-based procedure for capturing execution-related data in requirements models and an algorithm that takes these models as input for generating natural language requirements. We evaluated our approach in the context of a multiple case study with three organizations and a total of 13 software development projects.Results: We found that our approach can successfully generate well-readable requirements, which do not only positively contribute to consistency, but also to the completeness and maintainability of requirements.The practical use of our approach to identify a suitable subcontractor on the market in 11 of the 13 projects further highlights the practical value of our approach. Conclusion:Our approach provides a structured way to obtain high-quality requirements documents from process models and to maintain textual and visual representations of requirements in a consistent way.

show abstract

“…Deriving requirements and structures for requirements documents from graphical models is an established approach [16]. Especially UML/SysML diagrams have received attention.…”

Section: Related Workmentioning

confidence: 99%

What is a Good Textual Representation of Activity Diagrams in Requirements Documents?

Beckmann¹,

Vogelsang²

2017

2017 IEEE 25th International Requirements Engineering Conference Workshops (REW)

View full text Add to dashboard Cite

Abstract-The use of graphical models has become a widely adopted approach to specify requirements of complex systems. Still, in practice, graphical models are often accompanied by textual descriptions to provide more detail, because of legal considerations, and to enable stakeholders with different backgrounds to understand a requirements document. One of our industry partners (Daimler AG) uses activity diagrams to specify vehicle functions in combination with a textual representation thereof in their requirements documents. Since graphical and textual representations serve different purposes, it is not obvious how textual representations of activity diagrams should be structured. In this paper, we present different textual representations of activity diagrams for use in requirements documents. The representation currently in use is presented as well as four alternatives. For each representation, we discuss advantages and disadvantages. To evaluate the representations, we asked five stakeholders of one system to create a preference ranking of the representations. The resulting ranking showed that the currently used representation is not considered to be the best possible option. The stakeholders' favorite textual representation emphasizes structural similarity with the activity diagram, which however does not resemble the diagram's structure exactly.

show abstract

On the generation of requirements specifications from software engineering models: A systematic literature review

Cited by 94 publications

References 35 publications

Reusing enterprise models to build platform independent computer models

Reusing enterprise models to build platform independent computer models

A semi-automated approach for generating natural language requirements documents based on business process models

What is a Good Textual Representation of Activity Diagrams in Requirements Documents?

Contact Info

Product

Resources

About