TY - JOUR
T1 - Relevance-based abstraction identification
T2 - technique and evaluation
AU - Gacitua, Ricardo
AU - Sawyer, Peter
AU - Gervasi, Vincenzo
PY - 2011/9
Y1 - 2011/9
N2 - 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 find that RAI significantly outperforms previous techniques. We present an experiment measuring the effectiveness of RAI compared to human judgement, and discuss how RAI could be used to good effect in requirements engineering.
AB - 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 find that RAI significantly outperforms previous techniques. We present an experiment measuring the effectiveness of RAI compared to human judgement, and discuss how RAI could be used to good effect in requirements engineering.
KW - Abstractions
KW - Natural language
KW - Requirements elicitation
KW - Evaluation of tool
UR - https://link.springer.com/article/10.1007/s00766-011-0122-3
UR - http://www.scopus.com/inward/record.url?scp=84870583552&partnerID=8YFLogxK
U2 - 10.1007/s00766-011-0122-3
DO - 10.1007/s00766-011-0122-3
M3 - Article
SN - 0947-3602
VL - 16
SP - 251
EP - 265
JO - Requirements engineering
JF - Requirements engineering
IS - 3
ER -