How can open source software development help requirements management gain the potential of open innovation: an exploratory study

ABSTRACT

A key component in successfully managing software products is to properly, and in a timely manner, identify and secure competitive advantage by innovation via feature differentiation. Although open source software (OSS) is not a new idea, several product development companies that operate in a market-driven context have started to use open source solutions as core software components in their products. Adopting open source core components implies a lower degree of control over software development and increased business risk associated with integrating differentiating contributions into the core release stream. Whether and how to adjust the current requirements management practices after the adoption of OSS components to fully benefit from the concept of open innovation has not yet been empirically explored. We outline experiences and challenges related to leveraging open innovation via engaging in OSS identified during 19 interviews with practitioners occupying different roles in the requirements management process at a large company followed by four validation interviews with other practitioners. We then propose a research agenda for requirements and decision management in the open innovation context and suggest which challenges in requirements engineering open innovation affects.

References

1. Aurum, A., Wohlin C. 2007. A Value-Based Approach in Requirements Engineering: Explaining Some of the Fundamental Concepts. In Proceedings of the REFSQ 2007 Conference (Montpellier, France, June 20-23, 2007). 109--115. Springer, Heidelberg (2007) 109--115. DOI = 10.1007/978-3-540-73031-6_8.
2. Herbsleb, J. D. 2007. Global Software Engineering: The Future of Socio-technical Coordination. In: Proccedings of the FOSE'07 Future of Software Engineering (Minneapolis, MN, United states, May 23, 2007 - May 25, 2007). IEEE Computer Society, Washington, DC, USA, 188--198. DOI = 10.1109/FOSE.2007.11.
3. Biffl, S., Aurum, A., Boehm, B., Erdogmus, H., Grunbacher, P. (eds.). 2005. Value-Based Software Engineering. Springer, Heidelberg, ISBN 3-540-25993-7.
4. Sommerville, I., Sawyer P. 1997. Requirements Engineering: A Good Practice Guide. John Wiley & Sons Ltd., Chichester.
5. Chesbrough, H. 2003. Open Innovation The new Imperative for Creating and Profiting from Technology, Harvard Business School Press, USA.
6. Vanhaverbeke, W., Van de Vrande, V., Chesbrough, H. 2008. Understanding the Advantages of Open Innovation Practices in Corporate Venturing in Terms of Real Options. Creativity and Innovation Management. 251 (Mar. 2008), 251--258. DOI: 10.1109/IEEM.2008.4738011.
7. Lichtenthaler, U. 2008. Open Innovation in Practice: An Anlaysis of Strategic Approaches to Technology Transactions. Trans on Eng Management 55 (May 2008), 148--156. DOI: 10.1109/TEM.2007.912932.
8. Kauppinen, M., Savolainen, J., Mannisto, T. 2007. Requirements Engineering as a Driver for Innovations. In Proceedings of the 15th IEEE International Requirements Engineering Conference (New Delhi, India, 15-19 October 2007). IEEE Press, New York, 15--20. DOI: doi: 10.1109/RE.2007.47.
9. Grube, P., Schmid, K. 2008. Selecting Creativity Techniques for Innovative Requirements Engineering. In Proceedings of the Third International Workshop on Multimedia and Enjoyable Requirements Engineering - Beyond Mere Descriptions and with More Fun and Games MERE '08 (Barcelona, Spain 3 September), IEEE Press New York, 32--36. DOI: 10.1109/MERE.2008.6.
10. Myers, M. D., Avison D. 2002. Qualitative Research in Information Systems. Sage Publications, USA.
11. Pohl, C., Böckle, G., Linden, F. J. van der. 2005. Software Product Line Engineering: Foundations, Principles and Techniques. Springer-Verlag, New York USA.
12. M.Q. Patton. 2002. Qualitative Research and Evaluation Methods. Sage Publications, USA.
13. Agile manifesto http://agilemanifesto.org/, accessed January 2012.
14. Karlsson, J., Ryan, K. 1997. A cost-value approach for prioritizing requirements. IEEE Softw. 14 (Sept. 1997), 67--74. DOI: 10.1109/52.605933.
15. Regnell, B., Brinkkemper, S. 2005. Market-Driven Requirements Engineering for Software Products. In: Aurum, A., Wohlin, C. (Eds.), Managing and Engineering Software Requirements, 287--308. Springer-Verlag, Heidelberg.
16. Chesbrough, H., Adrienne Kardon C. 2006. Beyond high tech: early adopters of open innovation in other industries. R&D Management. 36 (June 2006), 229--236. DOI: 10.1111/j.1467-9310.2006.00428.x.
17. Hood, C., Wiedemann., S., Fichtinger, S., Pautz, U. 2008. Requirements Management: The Interface Between Requirements Development and All Other Systems Engineering Processes. Springer, Berlin.
18. Svahnberg, M., Gorschek, T., Feldt, R., Torkar, R., Bin Saleem, S., Usman M. 2010. A systematic review on strategic release planning models. Inf. Softw. Technol. 52 (Mar 2010), 237--248. DOI: 10.1016/j.infsof.2009.11.006.
19. Laurent, P., Cleland-Huang, J. 2009. Lessons learned from open source projects for facilitating online requirements processes. In Proceedings of the 15th International Working Conference Requirements Engineering: Foundation for Software Quality (Essen, Germany, 25 - 28 march 2009). Springer Verlag, Berling, 240--55. DOI: 10.1007/978-3-642-02050-6_21.
20. Glynn, E., Fitzgerald, B., Exton C. 2005. Commercial adoption of open source software: An empirical study. In Proceedings of the International Symposium on Empirical Software Engineering, (17-18 November, Noosa Heads, Australia , 2005), IEEE Press, New York , 225--234. DOI: 10.1109/ISESE.2005.1541831.
21. Maxwell, J. A. 1992. Understanding and validity in qualitative research. Harvard Educational Review, 62(Fall 1992), 279--300.

Index Terms

• Software and its engineering

  • Software creation and management

    • Software development process management

      • Software development methods