Lessons learned on applying design science for bridging the collaboration gap between industry and academia in empirical software engineering

Collaboration between industry practitioners and researchers has been reported as a challenge to conduct empirical studies in software engineering. Gaining practitioners interest in research activities is challenging in the software development industry characterized by tough competition and short time-to-market. Often, practitioners do not see the direct value in collaborating with researchers. Meanwhile, researchers are frequently frustrated because they have no access to the real-world data that would enable them to develop scientific knowledge. Design science has become a popular research framework in Information Systems. This paper describes our lessons learned on how design science can help to attract and motivate industry practitioners to take part in empirical research. We present our practical experiences with using design science in the context of empirical software engineering, and how the design science framework helped us to bridge the collaborative gap with our industry partners. In illustrating our experiences, we present two case studies conducted in collaboration with Ericsson and Elektrobit in which the design science framework was followed. Based on our experience, design science is a suitable research framework for empirical software engineering since much of the research in the field is constructive. The similarities between the design science practices and the day-to-day work of practitioners in industry make it easy for them to understand the research approach. Thus, it supports their willingness to participate in research activities.

[1]  Pasi Kuvaja,et al.  Combining Lean Thinking and Agile Methods for Software Development: A Case Study of a Finnish Provider of Wireless Embedded Systems Detailed , 2014, 2014 47th Hawaii International Conference on System Sciences.

[2]  Juan Garbajosa,et al.  Building lean thinking in a telecom software development organization: strengths and challenges , 2013, ICSSP 2013.

[3]  Shirley Gregor,et al.  The Anatomy of a Design Theory , 2007, J. Assoc. Inf. Syst..

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

[5]  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).

[6]  Irit Hadar,et al.  Conducting a long-term case study in a software firm: An experience report , 2013, 2013 1st International Workshop on Conducting Empirical Studies in Industry (CESI).

[7]  Alan R. Hevner,et al.  Focus Groups for Artifact Refinement and Evaluation in Design Research , 2010, Commun. Assoc. Inf. Syst..

[8]  Salvatore T. March,et al.  Design and natural science research on information technology , 1995, Decis. Support Syst..

[9]  Vijay K. Vaishnavi,et al.  Theory Development in Design Science Research: Anatomy of a Research Project , 2008 .

[10]  Samir Chatterjee,et al.  A Design Science Research Methodology for Information Systems Research , 2008 .

[11]  Pasi Kuvaja,et al.  Adapting the Lean Enterprise Self-Assessment Tool for the Software Development Domain , 2012, 2012 38th Euromicro Conference on Software Engineering and Advanced Applications.

[12]  Martin Bichler,et al.  Design science in information systems research , 2006, Wirtschaftsinf..

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

[14]  Pilar Rodríguez,et al.  Combining lean thinking and agile software development : how do software-intensive companies use them in practice? , 2013 .