Technology transfer decision support in requirements engineering research: a systematic review of REj

One of the main goals of an applied research field such as requirements engineering is the transfer of research results to industrial use. To promote industrial adoption of technologies developed in academia, researchers need to provide tangible evidence of the advantages of using them. This can be done through industry validation, enabling researchers to test and validate technologies in a real setting with real users and applications. The evidence obtained, together with detailed information on how the validation was conducted, offers rich decision support material for industrial practitioners seeking to adopt new technologies. This paper presents a comprehensive systematic literature review of all papers published in the Requirements Engineering journal containing any type of technology evaluation. The aim is to gauge the support for technology transfer, i.e., to what degree industrial practitioners can use the reporting of technology evaluations in the journal as decision support for adopting the technologies in industrial practice. Findings show that very few evaluations offer full technology transfer support, i.e., have a realistic scale, application or subjects. The major improvement potential concerning support for technology transfer is found to be the subjects used in the evaluations. Attaining company support, including support for using practitioners as subjects, is vital for technology transfer and for researchers seeking to validate technologies.

[1]  Roel Wieringa,et al.  Requirements engineering paper classification and evaluation criteria: a proposal and a discussion , 2005, Requirements Engineering.

[2]  Shari Lawrence Pfleeger,et al.  Preliminary Guidelines for Empirical Research in Software Engineering , 2002, IEEE Trans. Software Eng..

[3]  Claes Wohlin,et al.  Engineering and Managing Software Requirements , 2005 .

[4]  Roel Wieringa,et al.  The methodological soundness of requirements engineering papers: a conceptual framework and two case studies , 2006, Requirements Engineering.

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

[6]  Shari Lawrence Pfleeger,et al.  Understanding and improving technology transfer in software engineering , 1999, J. Syst. Softw..

[7]  Robert D. Macredie,et al.  The Importance of Context in Information System Design: An Assessment of Participatory Design , 1999, Requirements Engineering.

[8]  Colin J. Neill,et al.  Requirements Engineering: The State of the Practice , 2003, IEEE Softw..

[9]  Debbie Richards.  Merging individual conceptual models of requirements , 2003, Requirements Engineering.

[10]  Claes Wohlin,et al.  A Framework for Technology Introduction in Software Organizations 1 , 1996 .

[11]  Päivi Parviainen,et al.  A Survey of Existing Requirements Engineering Technologies and their Coverage , 2007, Int. J. Softw. Eng. Knowl. Eng..

[12]  Tony Gorschek,et al.  A Model for Technology Transfer in Practice , 2006, IEEE Software.

[13]  Marvin V. Zelkowitz,et al.  Culture Conflicts in Software Engineering Technology Transfer , 1998 .

[14]  E. Guba,et al.  Fourth Generation Evaluation , 1989 .

[15]  Barbara Paech,et al.  MOQARE: misuse-oriented quality requirements engineering , 2008, Requirements Engineering.

[16]  H. Dieter Rombach,et al.  Experimentation as a vehicle for software technology transfer-A family of software reading techniques , 1997, Inf. Softw. Technol..

[17]  Neil Maiden,et al.  What Has Requirements Research Ever Done for Us? , 2005, IEEE Softw..

[18]  Joaquín Nicolás,et al.  Requirements Reuse for Improving Information Systems Security: A Practitioner’s Approach , 2002, Requirements Engineering.

[19]  Donald R. Chand,et al.  Diffusing software-engineering methods , 1989, IEEE Software.

[20]  Sara Jones,et al.  Generating requirements from systems models using patterns: a case study , 2005, Requirements Engineering.

[21]  Magne Jørgensen,et al.  Forecasting of software development work effort: Evidence on expert judgement and formal models , 2007 .

[22]  Paul Lukowicz,et al.  Experimental evaluation in computer science: A quantitative study , 1995, J. Syst. Softw..

[23]  Björn Regnell,et al.  Requirements engineering challenges in market-driven software development - An interview study with practitioners , 2007, Inf. Softw. Technol..

[24]  Michael Breen.  Experience of using a lightweight formal specification method for a commercial embedded system product line , 2004, Requirements Engineering.

[25]  Søren Lauesen,et al.  Preventing Requirement Defects: An Experiment in Process Improvement , 2001, Requirements Engineering.

[26]  Robert L. Glass,et al.  The software-research crisis , 1994, IEEE Software.

[27]  Martin Höst,et al.  An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.

[28]  Winifred Menezes,et al.  Marketing Technology to Software Practitioners , 2000, IEEE Softw..

[29]  J. Knottnerus,et al.  Real world research. , 2010, Journal of clinical epidemiology.

[30]  Hossein Saiedian,et al.  Scenario-based requirements analysis techniques for real-time software systems: a comparative evaluation , 2004, Requirements Engineering.

[31]  Gustavo Rossi,et al.  Enhancing a requirements baseline with scenarios , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[32]  Venkataraman Ramesh,et al.  Research in software engineering: an analysis of the literature , 2002, Inf. Softw. Technol..

[33]  Marvin V. Zelkowitz,et al.  Experimental validation in software engineering , 1997, Inf. Softw. Technol..

[34]  Yvonna S. Lincoln,et al.  Fourth generation evaluation Sage. , 1993 .

[35]  David Lorge Parnas,et al.  Stop the numbers game , 2007, CACM.

[36]  Pearl Brereton,et al.  Performing systematic literature reviews in software engineering , 2006, ICSE.

[37]  Tony Gorschek,et al.  Industry evaluation of the Requirements Abstraction Model , 2007, Requirements Engineering.

[38]  Claes Wohlin,et al.  Experimentation in Software Engineering , 2000, The Kluwer International Series in Software Engineering.

[39]  E. Rogers,et al.  Diffusion of innovations , 1964, Encyclopedia of Sport Management.

[40]  Julio Cesar Sampaio do Prado Leite,et al.  Scenario inspections , 2003, Requirements Engineering.

[41]  Barbara Paech,et al.  Rationale-Based Use Case Specification , 2002, Requirements Engineering.

[42]  Radmila Juric,et al.  Engineering Requirements Through Use Cases in Complex Business Environment , 1999, Requirements Engineering.

[43]  William E. Riddle,et al.  Software technology maturation , 1985, ICSE '85.

[44]  Natalia Juristo Juzgado,et al.  Effectiveness of Requirements Elicitation Techniques: Empirical Results Derived from a Systematic Review , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[45]  Julio Cesar Sampaio do Prado Leite,et al.  A Scenario Construction Process , 2000, Requirements Engineering.

[46]  Behrouz Homayoun Far,et al.  A case study validation of a knowledge-based approach for the selection of requirements engineering techniques , 2008, Requirements Engineering.

[47]  Marvin V. Zelkowitz,et al.  Software engineering technology infusion within NASA , 1996 .

[48]  Guenther Ruhe,et al.  Impact Analysis of Missing Values on the Prediction Accuracy of Analogy-based Software Effort Estimation Method AQUA , 2007, ESEM 2007.

[49]  Julio Cesar Sampaio do Prado Leite,et al.  A Framework for Integrating Non-Functional Requirements into Conceptual Models , 2001, Requirements Engineering.

[50]  Tore Dybå,et al.  Conducting realistic experiments in software engineering , 2002, Proceedings International Symposium on Empirical Software Engineering.

[51]  Pearl Brereton,et al.  Systematic literature reviews in software engineering - A systematic literature review , 2009, Inf. Softw. Technol..

[52]  Jim Duggan,et al.  A Tool to Support Collaborative Software Requirements Management , 2001, Requirements Engineering.

[53]  Keng Siau,et al.  Are use case and class diagrams complementary in requirements analysis? An experimental study on use case and class diagrams in UML , 2004, Requirements Engineering.

[54]  Janis A. Bubenko,et al.  Requirements Engineering and Technology Transfer: Obstacles, Incentives and Improvement Agenda , 2002, Requirements Engineering.

[55]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.

[56]  Tore Dybå,et al.  Applying Systematic Reviews to Diverse Study Types: An Experience Report , 2007, First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007).

[57]  Colin Potts,et al.  Software-engineering research revisited , 1993, IEEE Software.