Challenges and best practices in industry-academia collaborations in software engineering: A systematic literature review

Context: The global software industry and the software engineering (SE) academia are two large communities. However, unfortunately, the level of joint industry-academia collaborations in SE is still relatively very low, compared to the amount of activity in each of the two communities. It seems that the two 'camps' show only limited interest/motivation to collaborate with one other. Many researchers and practitioners have written about the challenges, success patterns (what to do, i.e., how to collaborate) and anti-patterns (what not do do) for industry-academia collaborations.Objective: To identify (a) the challenges to avoid risks to the collaboration by being aware of the challenges, (b) the best practices to provide an inventory of practices (patterns) allowing for an informed choice of practices to use when planning and conducting collaborative projects.Method: A systematic review has been conducted. Synthesis has been done using grounded-theory based coding procedures.Results: Through thematic analysis we identified 10 challenge themes and 17 best practice themes. A key outcome was the inventory of best practices, the most common ones recommended in different contexts were to hold regular workshops and seminars with industry, assure continuous learning from industry and academic sides, ensure management engagement, the need for a champion, basing research on real-world problems, showing explicit benefits to the industry partner, be agile during the collaboration, and the co-location of the researcher on the industry side.Conclusion: Given the importance of industry-academia collaboration to conduct research of high practical relevance we provide a synthesis of challenges and best practices, which can be used by researchers and practitioners to make informed decisions on how to structure their collaborations.

[1]  Michael A. Jackson,et al.  Problem Frames - Analysing and Structuring Software Development Problems , 2000 .

[2]  G. G. Stokes "J." , 1890, The New Yale Book of Quotations.

[3]  Oscar Dieste,et al.  Software industry experiments: A systematic literature review , 2013, 2013 1st International Workshop on Conducting Empirical Studies in Industry (CESI).

[4]  Vahid Garousi,et al.  Software test-code engineering: A systematic mapping , 2015, Inf. Softw. Technol..

[5]  Richard E. Fairley,et al.  Guide to the Software Engineering Body of Knowledge (SWEBOK(R)): Version 3.0 , 2014 .

[6]  Claes Wohlin Empirical software engineering research with industry: Top 10 challenges , 2013, 2013 1st International Workshop on Conducting Empirical Studies in Industry (CESI).

[7]  Lars-Ola Damm,et al.  Early and Cost-Effective Software Fault Detection: Measurement and Implementation in an Industrial Setting , 2007 .

[8]  Sigrid Eldh Some researcher considerations when conducting empirical studies in industry , 2013, 2013 1st International Workshop on Conducting Empirical Studies in Industry (CESI).

[9]  J. Osborne Best Practices in Quantitative Methods , 2009 .

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

[11]  Thomas Arts,et al.  Agile Collaborative Research: Action Principles for Industry-Academia Collaboration , 2011, IEEE Software.

[12]  Manoj Manuja,et al.  Industry academia collaboration model: The design challenges , 2011, 2011 24th IEEE-CS Conference on Software Engineering Education and Training (CSEE&T).

[13]  H. Dieter Rombach,et al.  Research Collaborations between Academia and Industry , 2007, Future of Software Engineering (FOSE '07).

[14]  Lionel Briand,et al.  Embracing the Engineering Side of Software Engineering , 2012, IEEE Softw..

[15]  Vahid Garousi A bibliometric analysis of the Turkish software engineering research community , 2015, Scientometrics.

[16]  David E. Avison,et al.  Action research , 1999, CACM.

[17]  Per Runeson It Takes Two to Tango -- An Experience Report on Industry -- Academia Collaboration , 2012, 2012 IEEE Fifth International Conference on Software Testing, Verification and Validation.

[18]  Claes Wohlin,et al.  Faults-slip-through - a concept for measuring the efficiency of the test process , 2006, Softw. Process. Improv. Pract..

[19]  Alexander L. Wolf,et al.  International Conference on Software Engineering, ISCE 2007, Workshop on the Future of Software Engineering, FOSE 2007, May 23-25, 2007, Minneapolis, MN, USA , 2007, FOSE@ICSE.

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

[21]  Muhammad Ali Babar,et al.  Identifying relevant studies in software engineering , 2011, Inf. Softw. Technol..

[22]  A. Salter,et al.  Academic Engagement and Commercialisation: A Review of the Literature on University-Industry Relations , 2012 .

[23]  Kai Petersen,et al.  Systematic Mapping Studies in Software Engineering , 2008, EASE.

[24]  Muhammad Ali Babar,et al.  Conducting empirical studies in industry: Balancing rigor and relevance , 2013, 2013 1st International Workshop on Conducting Empirical Studies in Industry (CESI).

[25]  Carlo Ghezzi,et al.  Determining the Impact of Software Engineering Research on Practice , 2008, Computer.

[26]  Robert L. Glass,et al.  Software Conflict 2.0: The Art and Science of Software Engineering , 2006 .

[27]  Claes Wohlin,et al.  Software Engineering Research under the Lamppost , 2013, ICSOFT.

[28]  Donald A. Sch The reflective practitioner: how professionals think in action , 1983 .

[29]  Ali Kanso,et al.  Foundations for long-term collaborative research , 2014, WISE@ASE.

[30]  Kelvin J. Ross,et al.  Industry Academia Collaboration: An Experience Report at a Small University , 2009, 2009 22nd Conference on Software Engineering Education and Training.

[31]  Lionel C. Briand Useful software engineering research - leading a double-agent life , 2011, ICSM.

[32]  Claes Wohlin,et al.  Guidelines for snowballing in systematic literature studies and a replication in software engineering , 2014, EASE '14.

[33]  Kai Petersen,et al.  Finding relevant research solutions for practical problems: the serp taxonomy architecture , 2014, WISE@ASE.

[34]  Daniela Cruzes,et al.  Synthesizing evidence in software engineering research , 2010, ESEM '10.

[35]  Vahid Garousi,et al.  When and what to automate in software testing? A multi-vocal literature review , 2016, Inf. Softw. Technol..

[36]  Kai Petersen,et al.  Action research as a model for industry-academia collaboration in the software engineering context , 2014, WISE@ASE.

[37]  S. J. Lamprecht,et al.  Models for technology research collaboration between industry and academia in South Africa , 2012, Proceedings of the 2012 4th IEEE Software Engineering Colloquium (SE).

[38]  B. Glaser Theoretical Sensitivity: Advances in the Methodology of Grounded Theory , 1978 .

[39]  Eduard Paul Enoiu,et al.  Enablers and impediments for collaborative research in software testing: an empirical exploration , 2014, WISE@ASE.

[40]  Forrest Shull,et al.  Impact of research on practice in the field of inspections, reviews and walkthroughs: learning from successful industrial uses , 2008, SOEN.

[41]  Alan M. Davis,et al.  Requirements Researchers: Do We Practice What We Preach? , 2002, Requirements Engineering.

[42]  Vahid Garousi,et al.  An Open-Source Tool for Automated Generation of Black-Box xUnit Test Code and Its Industrial Evaluation , 2010, TAIC PART.

[43]  Vahid Garousi,et al.  A systematic mapping study of web application testing , 2013, Inf. Softw. Technol..

[44]  Guilherme Horta Travassos,et al.  Action research use in software engineering: An initial survey , 2009, ESEM 2009.

[45]  Christian Steger,et al.  Embedding research in the industrial field: a case of a transition to a software product line , 2014, WISE@ASE.

[46]  Helena Martins Marques,et al.  Practical experiences in designing and conducting empirical studies in industry-academia collaboration , 2014, CESI 2014.

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

[48]  Daniela Cruzes,et al.  Research synthesis in software engineering: A tertiary study , 2011, Inf. Softw. Technol..

[49]  Vahid Garousi,et al.  A bibliometric/Geographic Assessment of 40 Years of Software Engineering Research (1969-2009) , 2013, Int. J. Softw. Eng. Knowl. Eng..

[50]  K. Malterud Qualitative research: standards, challenges, and guidelines , 2001, The Lancet.

[51]  Vahid Garousi,et al.  Cost, benefits and quality of software development documentation: A systematic mapping , 2015, J. Syst. Softw..

[52]  Lefteris Angelis,et al.  The Success Factors Powering Industry-Academia Collaboration , 2012, IEEE Software.

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

[54]  Paul Grünbacher,et al.  Success factors for empirical studies in industry-academia collaboration: A reflection , 2013, 2013 1st International Workshop on Conducting Empirical Studies in Industry (CESI).

[55]  D. Schoen,et al.  The Reflective Practitioner: How Professionals Think in Action , 1985 .

[56]  Citations , 2002 .

[57]  Lutz Prechelt,et al.  A Coding Scheme Development Methodology Using Grounded Theory for Qualitative Analysis of Pair Programming , 2007, PPIG.

[58]  Vahid Garousi,et al.  Graphical user interface (GUI) testing: Systematic mapping and repository , 2013, Inf. Softw. Technol..

[59]  Per Runeson,et al.  Get the cogs in synch: time horizon aspects of industry--academia collaboration , 2014, WISE@ASE.

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

[61]  Tony Gorschek,et al.  A method for evaluating rigor and industrial relevance of technology evaluations , 2011, Empirical Software Engineering.

[62]  A Bibliometric Assessment of Canadian Software Engineering Scholars and Institutions (1996-2006) , 2010, Comput. Inf. Sci..

[63]  Vahid Garousi,et al.  The need for multivocal literature reviews in software engineering: complementing systematic literature reviews with grey literature , 2016, EASE.

[64]  Pär J. Ågerfalk,et al.  Situational Method Engineering , 2014, Springer Berlin Heidelberg.

[65]  Kai Petersen,et al.  Guidelines for conducting systematic mapping studies in software engineering: An update , 2015, Inf. Softw. Technol..

[66]  Per Runeson,et al.  The 4+1 view model of industry--academia collaboration , 2014, WISE@ASE.

[67]  S. Ankrah,et al.  Universities-Industry Collaboration: A Systematic Review , 2015 .

[69]  Daniela Cruzes,et al.  Recommended Steps for Thematic Synthesis in Software Engineering , 2011, 2011 International Symposium on Empirical Software Engineering and Measurement.

[70]  Maria Teresa Baldassarre,et al.  Empirical studies for innovation dissemination: ten years of experience , 2013, EASE '13.

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

[72]  Claes Wohlin,et al.  Strategies for industrial relevance in software engineering education , 1999, J. Syst. Softw..

[73]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[74]  A. Strauss,et al.  Basics of qualitative research: Grounded theory procedures and techniques. , 1992 .

[75]  Marcelo Masera,et al.  Requirements engineering and industrial uptake , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[76]  Natalia Juristo Juzgado,et al.  Topic selection in industry experiments , 2014, CESI 2014.

[77]  Krassie Petrova,et al.  Bridging the Research-Practice Gap in Requirements Engineering through Effective Teaching and Peer Learning , 2009, 2009 Sixth International Conference on Information Technology: New Generations.

[78]  Vahid Garousi,et al.  Citations, research topics and active countries in software engineering: A bibliometrics study , 2016, Comput. Sci. Rev..