Naming the pain in requirements engineering: Contemporary problems, causes, and effects in practice

Tutkimustuotos: Lehtiartikkelivertaisarvioitu


  • D. Méndez Fernández
  • S. Wagner
  • M. Kalinowski
  • M. Felderer
  • P. Mafra
  • A. Vetrò
  • T. Conte
  • M. T. Christiansson
  • D. Greer
  • M. Nayabi
  • M. Oivo
  • B. Penzenstadler
  • D. Pfahl
  • R. Prikladnicki
  • G. Ruhe
  • A. Schekelmann
  • S. Sen
  • R. Spinola
  • A. Tuzcu
  • J. L. de la Vara
  • R. Wieringa


  • Technische Universität München
  • University of Stuttgart
  • Universidade Federal Fluminense
  • University of Innsbruck
  • Polytechnic University of Turin
  • Universidade Federal do Amazonas
  • Karlstad University
  • Queen's University Belfast
  • University of Calgary
  • University of Oulu
  • California State University Long Beach
  • University of Tartu
  • Pontifícia Universidade Católica do Rio Grande do Sul
  • Niederrhein University of Applied Sciences
  • Universidade Federal da Bahia
  • GmbH
  • Universidad Carlos III de Madrid
  • University of Twente
  • University of Helsinki
  • Simula Research Laboratory
  • Salvador University


Requirements Engineering (RE) has received much attention in research and practice due to its importance to software project success. Its interdisciplinary nature, the dependency to the customer, and its inherent uncertainty still render the discipline difficult to investigate. This results in a lack of empirical data. These are necessary, however, to demonstrate which practically relevant RE problems exist and to what extent they matter. Motivated by this situation, we initiated the Naming the Pain in Requirements Engineering (NaPiRE) initiative which constitutes a globally distributed, bi-yearly replicated family of surveys on the status quo and problems in practical RE. In this article, we report on the qualitative analysis of data obtained from 228 companies working in 10 countries in various domains and we reveal which contemporary problems practitioners encounter. To this end, we analyse 21 problems derived from the literature with respect to their relevance and criticality in dependency to their context, and we complement this picture with a cause-effect analysis showing the causes and effects surrounding the most critical problems. Our results give us a better understanding of which problems exist and how they manifest themselves in practical environments. Thus, we provide a first step to ground contributions to RE on empirical observations which, until now, were dominated by conventional wisdom only.


JulkaisuEmpirical Software Engineering
TilaJulkaistu - lokakuuta 2017
OKM-julkaisutyyppiA1 Julkaistu artikkeli, soviteltu

ID: 9198647