2014
DOI: 10.1016/j.is.2014.05.006
|View full text |Cite
|
Sign up to set email alerts
|

What stakeholders will or will not say: A theoretical and empirical study of topic importance in Requirements Engineering elicitation interviews

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0
4

Year Published

2015
2015
2020
2020

Publication Types

Select...
6
4

Relationship

1
9

Authors

Journals

citations
Cited by 28 publications
(14 citation statements)
references
References 46 publications
0
10
0
4
Order By: Relevance
“…This finding is inline with the results of Fernández et al [40], which hold that RE professionals' weak qualification and lack of experience are among the causes for incomplete and/or hidden requirements. Also, it highlights the importance of Burnay et al's [41] urges to prepare elicitation interview questions so that implicit requirements may be better captured. While some authors argue that such requirements are best identified using ethnographic methods [42][43] [44], our results reveal that observation is rather time-consuming and ineffective at gathering complete requirements.…”
Section: Discussionmentioning
confidence: 99%
“…This finding is inline with the results of Fernández et al [40], which hold that RE professionals' weak qualification and lack of experience are among the causes for incomplete and/or hidden requirements. Also, it highlights the importance of Burnay et al's [41] urges to prepare elicitation interview questions so that implicit requirements may be better captured. While some authors argue that such requirements are best identified using ethnographic methods [42][43] [44], our results reveal that observation is rather time-consuming and ineffective at gathering complete requirements.…”
Section: Discussionmentioning
confidence: 99%
“…In order to build a web-based information system for snow avalanche observations, we first identified the user needs via a requirement analysis based on different methods as interviews (e.g., Burnay et al, 2014), scenario examples and observation of the working process in real conditions. These methods helped us to define system specifications that meet the expectations of the users.…”
Section: User Needs and System Requirementsmentioning
confidence: 99%
“…Although the sentences shared by stakeholders during elicitation were not proper requirements, we consider the previous criteria can still be considered as ways to evaluate quality of information. The quantity of documentation REC was studied using some dimensions of context defined in [23]. Our objective here was simply to provide examples of topics that might be discussed during interviews, and see how subjects were behaving toward the latter.…”
Section: Exploratory Study -Empirical Designmentioning
confidence: 99%