When first approaching an unfamiliar domain or requirements document, it is often useful to get a quick grasp of what the essential concepts and entities in the domain are. This process is called abstraction identification, where the word abstraction refers to an entity or concept that has a particular significance in the domain. Abstraction identification has been proposed and evaluated as a useful technique in requirements engineering (RE). In this paper, we propose a new technique for automated abstraction identification called relevance-based abstraction identification (RAI), and evaluate its performance-in multiple configurations and through two refinements-compared to other tools and techniques proposed in the literature, where we fin...
In this position paper, we discuss the role of abstraction in designing for appropriation. We examin...
By means of abstraction a notion A is derived from a notion S. The re-sulting notion A often is call...
Requirements can cause substantial problems in large software projects if not handled correctly and ...
When first approaching an unfamiliar domain or requirements document, it is often useful to get a qu...
The identification of abstractions, i.e. terms that have a particular significance in a given domain...
Abstract. Abstraction identification is named as a key problem in requirements analysis. Typically, ...
Software requirements are often formulated on different levels and hence they are difficult to compa...
Abstract Software requirements are often formulated on different levels and hence they are difficult...
Requirements documents often describe the system on different abstraction levels. This results in th...
Most requirements engineering (RE) research and practice embodies a philosophy that we will call abs...
In the context of Information Systems development supported by software applications, the coherence ...
One of the most powerful tools designers have at their disposal is abstraction. By abstracting from ...
We have been investigating the implications of using abstractions based on intent rather than the ag...
This paper advocates that extracting formal specification semantically consistent to the original le...
This paper takes a cognitive view of data modeling to address the usability of semantic modeling tec...
In this position paper, we discuss the role of abstraction in designing for appropriation. We examin...
By means of abstraction a notion A is derived from a notion S. The re-sulting notion A often is call...
Requirements can cause substantial problems in large software projects if not handled correctly and ...
When first approaching an unfamiliar domain or requirements document, it is often useful to get a qu...
The identification of abstractions, i.e. terms that have a particular significance in a given domain...
Abstract. Abstraction identification is named as a key problem in requirements analysis. Typically, ...
Software requirements are often formulated on different levels and hence they are difficult to compa...
Abstract Software requirements are often formulated on different levels and hence they are difficult...
Requirements documents often describe the system on different abstraction levels. This results in th...
Most requirements engineering (RE) research and practice embodies a philosophy that we will call abs...
In the context of Information Systems development supported by software applications, the coherence ...
One of the most powerful tools designers have at their disposal is abstraction. By abstracting from ...
We have been investigating the implications of using abstractions based on intent rather than the ag...
This paper advocates that extracting formal specification semantically consistent to the original le...
This paper takes a cognitive view of data modeling to address the usability of semantic modeling tec...
In this position paper, we discuss the role of abstraction in designing for appropriation. We examin...
By means of abstraction a notion A is derived from a notion S. The re-sulting notion A often is call...
Requirements can cause substantial problems in large software projects if not handled correctly and ...