What you need is what you get!: The vision of view-based requirements specifications

Gross, Anne; Doerr, Joerg

doi:10.1109/re.2012.6345801

Cited by 22 publications

(10 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…From the different opinions on the contained information, we conclude that a mechanism is needed to tailor the models according to each individual's needs. This suggestion has been stated before [13] and is in line with established solutions on using textual requirements [26].…”

Section: Suggestionssupporting

confidence: 71%

“…Nevertheless, despite showing several advantages there are drawbacks such as end users' unfamiliarity with graphical notations and limits on the displayable details in visualizations. Moreover in requirements engineering, research has identified the need for different representations of requirements [13]. A possibility to tackle these issues is to use accompanying text for graphical models.…”

Section: Related Workmentioning

confidence: 99%

“…This conflict cannot be resolved by using a single graphical representation of a function for all stakeholders (cf. [13]). …”

Section: Findings From Our Studymentioning

confidence: 99%

See 2 more Smart Citations

Coexisting Graphical and Structured Textual Representations of Requirements: Insights and Suggestions

Beckmann

Reuter

Vogelsang

2018

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Abstract. [Context & motivation] Many requirements documents contain graphical and textual representations of requirements side-byside. These representations may be complementary but oftentimes they are strongly related or even express the same content. [Question/problem] Since both representation may be used on their own, we want to find out why and how a combination of them is used in practice. In consequence, we want to know what advantages such an approach provides and whether challenges arise from the coexistence. [Principal ideas/results] To get more insights into how graphical and textual representations are used in requirements documents, we conducted eight interviews with stakeholders at Daimler. These stakeholders work on a system that is specified by tabular textual descriptions and UML activity diagrams. The results indicate that the different representations are associated with different activities.[Contribution] Our study provides insights into a possible implementation of a specification approach using mixed representations of requirements. We use these insights to make suggestions on how to apply the approach in a way that profits from its advantages and mitigates potential weaknesses. While we draw our conclusions from a single use case, some aspects might be applicable in general.

show abstract

Section: Suggestionssupporting

confidence: 71%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Coexisting Graphical and Structured Textual Representations of Requirements: Insights and Suggestions

Beckmann

Reuter

Vogelsang

2018

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

show abstract

“…Some exemplary activities are estimating the costs, planning the implementation of the system, developing the system, or testing the system. Consequently, high quality in RE is the degree to which engineers working with the requirements (i.e., the information) can efficiently and effectively use the requirements to execute their requirements-based activities [7]. RE artifact quality should be defined and assessed with respect to the achievement of these goals.…”

Section: Goals Of Requirements Engineeringmentioning

confidence: 99%

Requirements Quality Is Quality in Use

Femmer¹,

Vogelsang

2019

IEEE Softw.

View full text Add to dashboard Cite

The quality of requirements engineering artifacts is widely considered a success factor for software projects. Currently, the definition of high-quality or good RE artifacts is often provided through normative references, such as quality standards, textbooks, or generic guidelines. We see various problems of such normative references: (1) It is hard to ensure that the contained rules are complete, (2) the contained rules are not context-dependent, and (3) the standards lack precise reasoning why certain criteria are considered bad quality. To change this understanding, we postulate that creating an RE artifact is rarely an end in itself, but just a means to understand and reach the project's goals. Following this line of thought, the purpose of an RE artifact is to support the stakeholders in whatever activities they are performing in the project. This purpose must define high-quality RE artifacts. To express this view, we contribute an activity-based RE quality meta model and show applications of this paradigm. Lastly, we describe the impacts of this view onto research and practice.

show abstract

“…Software requirements classification is a time‐consuming task that represents the first stage in the requirements analysis. Recent proposals (see [5–8 ]) rely on Natural Language Processing (NLP) and Information Extraction techniques to define features to apply machine‐learning techniques [9 ]. These proposals aim at providing meaningful support to stakeholders in decision making and further analytical processes.…”

Section: Introductionmentioning

confidence: 99%

Classifying design‐level requirements using machine learning for a recommender of interaction design patterns

Silva-Rodríguez

Nava-Muñoz

Castro³

et al. 2020

IET softw.

View full text Add to dashboard Cite

Software Engineering is a discipline that encompasses processes associated with the development of interactive systems. The perceived quality of an interactive system is heavily influenced by the user interface design, which may result in many challenges. One such challenge is design‐level requirements analysis. The success of the software system is mostly dependent on how well users’ requirements have been understood and translated into appropriate functionalities. During the interactive system design process, it is common to find recurring problems in human–computer interactions, for which reusing solutions is highly feasible. Interaction design patterns seek to support designers in decision making during the design of interactive systems. Due to the design task tends to be subjective and prone to errors. This work aims at presenting and evaluating an interaction design patterns recommendation model based on design‐level requirements classification, through the application of supervised machine learning algorithms. To compare the performance of four classification algorithms, a study was carried out, in which the linear support vector machine was the most suitable to this problem. The results of this work can be used for implementing frameworks that can better support designers’ decision making when designing user interfaces.

show abstract

What you need is what you get!: The vision of view-based requirements specifications

Cited by 22 publications

References 17 publications

Coexisting Graphical and Structured Textual Representations of Requirements: Insights and Suggestions

Coexisting Graphical and Structured Textual Representations of Requirements: Insights and Suggestions

Requirements Quality Is Quality in Use

Classifying design‐level requirements using machine learning for a recommender of interaction design patterns

Contact Info

Product

Resources

About