论文标题
使用开源工具开放创新:Sony Mobile的案例研究
Open innovation using open source tools: a case study at Sony Mobile
论文作者
论文摘要
尽管在软件工程(SE)中对开放创新(OI)的兴趣日益增加,但对触发软件组织采用它以及这如何影响SE实践的知识知之甚少。可以以多种方式实现OI,包括开源软件(OSS)参与。 OI的结果不仅限于产品创新,还包括流程创新,例如改进的SE实践和方法。这项研究从OI的角度探讨了软件组织(Sony Mobile)在OSS社区中的参与,以及与OI相关的SE SE实践(需求工程和测试)的参与。它还突出了OI产生的创新成果。一项探索性嵌入式案例研究调查了索尼移动使用和如何为詹金斯和杰里特做出贡献;其连续集成工具链中的两个中央OSS工具。对从源代码存储库进行的更改日志数据进行了定量分析,以识别顶级贡献者,并通过五次半结构访谈的结果进行三角剖分,以探索提交的性质。案例研究的结果包括五个主要主题:i)朝着工具社区开放的过程与组织中的一般采用OSS及时相关。 ii)资产不被视为竞争优势或收入来源向OSS社区开放,并且逐渐地,组织更加开放。 iii)针对社区的要求工程过程是非正式的,并且是基于参与的。 iv)对系统和自动化测试的需求仍处于起步阶段,但需要确定需求。 v)创新成果包括免费功能和维护,据信可以提高开发的速度和质量。采用OI是从Windows转移到Linux的范式转移的结果。
Despite growing interest of Open Innovation (OI) in Software Engineering (SE), little is known about what triggers software organizations to adopt it and how this affects SE practices. OI can be realized in numerous of ways, including Open Source Software (OSS) involvement. Outcomes from OI are not restricted to product innovation but also include process innovation, e.g. improved SE practices and methods. This study explores the involvement of a software organization (Sony Mobile) in OSS communities from an OI perspective and what SE practices (requirements engineering and testing) have been adapted in relation to OI. It also highlights the innovative outcomes resulting from OI. An exploratory embedded case study investigates how Sony Mobile use and contribute to Jenkins and Gerrit; the two central OSS tools in their continuous integration tool chain. Quantitative analysis was performed on change log data from source code repositories in order to identify the top contributors and triangulated with the results from five semi-structured interviews to explore the nature of the commits. The findings of the case study include five major themes: i) The process of opening up towards the tool communities correlates in time with a general adoption of OSS in the organization. ii) Assets not seen as competitive advantage nor a source of revenue are made open to OSS communities, and gradually, the organization turns more open. iii) The requirements engineering process towards the community is informal and based on engagement. iv) The need for systematic and automated testing is still in its infancy, but the needs are identified. v) The innovation outcomes included free features and maintenance, and were believed to increase speed and quality in development. Adopting OI was a result of a paradigm shift of moving from Windows to Linux.