Are Stakeholders the Only Source of Information for Requirements Engineers? Toward a Taxonomy of Elicitation Information Sources

被引:4
作者
Burnay, Corentin [1 ]
机构
[1] Univ Namur, Brussels Dept Business Adm, PReCISE Res Ctr, Fonds Rech Sci FNRS, Namur, Belgium
关键词
Requirements engineering; elicitation; information sources; taxonomy; empirical study; exploratory research;
D O I
10.1145/2965085
中图分类号
TP [自动化技术、计算机技术];
学科分类号
0812 ;
摘要
Requirements elicitation consists in collecting and documenting information about the requirements from a system-to-be and about the environment of that system. Elicitation forms a critical step in the design of any information system, subject to many challenges like information incompleteness, variability, or ambiguity. To deal with these challenges, requirements engineers heavily rely on stakeholders, who turn out to be one of the most significant provider of information during elicitation. Sometimes, this comes at the cost of less attention being paid by engineers to other sources of information accessible in a business. In this article, we try to deal with this issue by studying the different sources of information that can be used by engineers when designing a system. We propose TELIS (a Taxonomy of Elicitation Sources), which can be used during elicitation to review more systematically the sources of information about a system-to-be. TELIS was produced through a series of empirical studies and was partially validated through a real-world case study. Our objective in this article is to increase the awareness of engineers about the other information providers within a business. Ultimately, we believe our taxonomy may help in better dealing with classical elicitation challenges and increase the chances of successful information systems design.
引用
收藏
页数:29
相关论文
共 87 条
[1]  
Adepetu A, 2012, AAAI SPRING S WISD C, P2
[2]   Method for stakeholder identification in interorganizational environments [J].
Ballejos, Luciana C. ;
Montagna, Jorge M. .
REQUIREMENTS ENGINEERING, 2008, 13 (04) :281-297
[3]  
Bano M, 2013, IEEE INT WORKS EMPIR, P24, DOI 10.1109/EmpiRE.2013.6615212
[4]  
Berg B. L, 2004, QUALITATIVE RES METH, V5
[5]   APPRENTICING WITH THE CUSTOMER [J].
BEYER, HR ;
HOLTZBLATT, K .
COMMUNICATIONS OF THE ACM, 1995, 38 (05) :45-52
[6]  
Beyer Hugh., 1997, CONTEXTUAL DESIGN DE
[7]   Analyzing regulatory rules for privacy and security requirements [J].
Breaux, Travis D. ;
Anton, Annie I. .
IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, 2008, 34 (01) :5-20
[8]  
Breaux TD, 2006, RE'06: 14TH IEEE INTERNATIONAL REQUIREMENTS ENGINEERING CONFERENCE, PROCEEDINGS, P49
[9]   What stakeholders will or will not say: A theoretical and empirical study of topic importance in Requirements Engineering elicitation interviews [J].
Burnay, Corentin ;
Jureta, Ivan J. ;
Faulkner, Stephane .
INFORMATION SYSTEMS, 2014, 46 :61-81
[10]   Towards requirements-driven information systems engineering:: the Tropos project [J].
Castro, J ;
Kolp, M ;
Mylopoulos, J .
INFORMATION SYSTEMS, 2002, 27 (06) :365-389