In quest for requirements engineering oracles: dependent variables and measurements for (good) RE

Context: For many years, researchers and practitioners have been proposing various methods and approaches to Requirements Engineering (RE). Those contributions remain, however, too often on the level of apodictic discussions without having proper knowledge about the practical problems they propagate to address, or how to measure the success of the contributions when applying them in practical contexts. While the scientific impact of research might not be threatened, the practical impact of the contributions is. Aim: We aim at better understanding practically relevant variables in RE, how those variables relate to each other, and to what extent we can measure those variables. This allows for the establishment of generalisable improvement goals, and the measurement of success of solution proposals. Method: We establish a first empirical basis of dependent variables in RE and means for their measurement. We classify the variables according to their dimension (e.g. RE, company, SW project), their measurability, and their actionability. Results: We reveal 93 variables with 167 dependencies of which a large subset is measurable directly in RE while further variables remain unmeasurable or have too complex dependencies for reliable measurements. We critically reflect on the results and show direct implications for research in the field of RE. Conclusion: We discuss a variety of conclusions we can draw from our results. For example, we show a set of first improvement goals directly usable for evidence-based RE research such as "increase flexibility in the RE process", we discuss suitable study types, and, finally, we can underpin the importance of replication studies to obtain generalisability.

[1]  Daniela E. Damian,et al.  An Empirical Study of the Complex Relationships between Requirements Engineering Processes and Other Processes that Lead to Payoffs in Productivity, Quality, and Risk Management , 2006, IEEE Transactions on Software Engineering.

[2]  Roel Wieringa,et al.  Technical Action Research as a Validation Method in Information Systems Design Science , 2012, DESRIST.

[3]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[4]  Stefan Wagner,et al.  Naming the pain in requirements engineering: design of a global family of surveys and first results from Germany , 2013, EASE '13.

[5]  David Chenho Kung,et al.  Status report: requirements engineering , 1993, IEEE Software.

[6]  Roel Wieringa,et al.  Naming the pain in requirements engineering , 2016, Empirical Software Engineering.

[7]  Marco Kuhrmann,et al.  Who Cares About Software Process Modelling? A First Investigation About the Perceived Value of Process Engineering and Process Consumption , 2013, PROFES.

[8]  Heikki Kälviäinen,et al.  A State-of-the-Practice Survey on Requirements Engineering in Small- and Medium-Sized Enterprises , 2000 .

[9]  Birgit Penzenstadler,et al.  A case study on the application of an artefact-based requirements engineering approach , 2011, EASE.

[10]  Natalia Juristo Juzgado,et al.  Using differences among replications of software engineering experiments to gain knowledge , 2009, 2009 3rd International Symposium on Empirical Software Engineering and Measurement.

[11]  Khaled El Emam,et al.  A field study of requirements engineering practices in information systems development , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[12]  Philippe Kruchten,et al.  Using grounded theory to study the experience of software development , 2011, Empirical Software Engineering.

[13]  J. Fleiss Statistical methods for rates and proportions , 1974 .

[14]  Stefan Wagner,et al.  Field study on requirements engineering: Investigation of artefacts, project parameters, and execution strategies , 2012, Inf. Softw. Technol..

[15]  Roel Wieringa,et al.  Preliminary Survey on Empirical Research Practices in Requirements Engineering , 2012 .

[16]  Laurie A. Williams,et al.  Validating software metrics: A spectrum of philosophies , 2012, TSEM.

[17]  Austen Rainer,et al.  Requirements problems in twelve software companies: an empirical analysis , 2002, IEE Proc. Softw..

[18]  Tony Gorschek,et al.  Requirements engineering: In search of the dependent variables , 2008, Inf. Softw. Technol..

[19]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[20]  Manfred Broy,et al.  A meta model for artefact-orientation: fundamentals and lessons learned in requirements engineering , 2010, MODELS'10.

[21]  Austen Rainer,et al.  Software Process Improvement Problems in Twelve Software Companies: An Empirical Analysis , 2003, Empirical Software Engineering.

[22]  Chris Verhoef,et al.  The rise and fall of the Chaos report figures , 2010, IEEE Software.

[23]  Jacob Cohen A Coefficient of Agreement for Nominal Scales , 1960 .