What lies behind requirements? A quality assessment of statement grounds in requirements elicitation
- PDF / 1,558,898 Bytes
- 29 Pages / 439.642 x 666.49 pts Page_size
- 8 Downloads / 212 Views
What lies behind requirements? A quality assessment of statement grounds in requirements elicitation Corentin Burnay1 · Sarah Bouraga1 · Joseph Gillain1 · Ivan J. Jureta1,2
© Springer Science+Business Media, LLC, part of Springer Nature 2020
Abstract In requirements engineering (RE), an early yet critical activity consists in eliciting the requirements from various stakeholders, who usually have different assumptions, knowledge, and intentions. The goal during elicitation is to understand what stakeholders expect from a given software, expectations which then feed the analysis, prioritization, validation, and ultimately specification activities of the RE process. Elicitation is an interactive activity. It relies on verbal communication of statements of stakeholders about their requirements, their ideas, their assumptions, the constraints they know apply in the environment of the future software, and so forth. Statements, we claim, build either on a past experience of the stakeholder or are the result of reasoning from indirect experience, i.e., they have different grounds. In this paper, we introduce the concept of “Statement Ground” during RE, contrast it with the classical perspective on requirements elicitation, and position the concept in existing RE literature. We conduct an empirical assessment of the relative qualities of statements that have different grounds. Our work results in a better understanding of the statements produced by stakeholders during requirements elicitation, of their qualities, and of the interplay between those qualities and the concept of statement ground. It also results in the definition of a series of research questions which focus on the implications of our findings on the overall requirements engineering activity. Keywords Requirement engineering · Elicitation · Stakeholders communication · Statement · Ground · Experience · Hypothetical statement
1 Introduction 1.1 Statements in requirements elicitation Requirements elicitation, or simply elicitation, designates all activities conducted during requirements engineering (RE) in order to collect information from stakeholders about their Corentin Burnay
[email protected] 1
Department of Business Administration NADI Research Institute, PReCISE Research Center, University of Namur, Namur, Belgium
2
Fonds de la Recherche Scientifique - FNRS, University of Namur, Namur, Belgium
Software Quality Journal
requirements toward a software-to-be and about the environment in which that software is supposed to operate (Nuseibeh and Easterbrook 2000). It is an interactive process, relying on verbal or written statements made by stakeholders to requirements engineers, who are in charge of summarizing the information and ultimately of producing the specification of a software that complies with those expectations. Techniques to elicit requirements efficiently are numerous (Zowghi and Coulin 2005). They include approaches as varied as interviews, surveys, questionnaires, brainstorming sessions, group meetings, ethnography, and so on
Data Loading...
