Desmond Greer

TL;DR: The Naming the Pain in Requirements Engineering (NaPiRE) initiative as discussed by the authors is a family of surveys on the status quo and problems in practical requirements engineering (RE) in 10 countries in various domains.

TL;DR: In this article, the authors present an empirical and externally valid foundation for a theory of requirements engineering practice, which helps software engineers establish effective and efficient requirements engineering processes in a problem-driven manner.

TL;DR: The Naming the Pain in Requirements Engineering (NaPiRE) initiative as mentioned in this paper is a family of surveys on the status quo and problems in practical requirements engineering (RE) in 10 countries in various domains.

TL;DR: This survey is beneficial as an introduction for any researchers aiming to work in the area of Search-Based Software Engineering with respect to software maintenance to gain an understanding of the current landscape of the research and the insights gathered.

TL;DR: In this article, an empirically-based theory of requirements engineering (RE) has been developed and validated in 10 countries world-wide, with participants from 228 organizations, and the results reveal that there are no strong differences between organisations in different countries and regions, that interviews, facilitated meetings and prototyping are the most used elicitation techniques, that requirements are often documented textually, traces between requirements and code or design documents is common, requirements specifications themselves are rarely changed and that improvement endeavours are mostly intrinsically motivated.