Commodification of Industrial Software: A Case for Open Source

Linden, Frank van der; Lundell, Björn; Marttiin, Pentti

doi:10.1109/ms.2009.88

Cited by 72 publications

(75 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The increased openness that OI implies poses significant challenges to software organizations in terms of securing their competitive advantage (Munir et al 2016) and understanding what to contribute, when and how to maintain differentiation towards competitors that may also be involved in the OSS community (Henkel 2006;van der Linden et al 2009;Jansen et al 2012). Related to that is the challenge of what requirements should be selected, when these should be released and how an internal roadmap should be synchronized with the OSS project's roadmap (Wnuk et al 2012;Linåker et al 2016).…”

Section: Related Workmentioning

confidence: 99%

“…Organizations have a tendency to open proprietary products when they lose their value, and spinning off is a one way of re-capturing the value by creating a community around it (van der Linden et al 2009). This implication paves the way for future studies using proprietary solutions as units of analysis.…”

Section: Openness Of Tools Software Vs Proprietary Softwarementioning

confidence: 99%

See 1 more Smart Citation

Open innovation using open source tools: a case study at Sony Mobile

et al. 2017

View full text Add to dashboard Cite

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. This shift enabled Sony Mobile to utilize the Jenkins and Gerrit communities to make their internal development process better for its software developers and testers.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Openness Of Tools Software Vs Proprietary Softwarementioning

confidence: 99%

Open innovation using open source tools: a case study at Sony Mobile

et al. 2017

View full text Add to dashboard Cite

show abstract

“…We would in particular recommend investigating two issues: (1) topics related to integration of OSS components and (2) topics concerning participation in organization-community or inter-organizational OSS collaborations. We find these issues important because integration of OSS components concerns most software-intensive organizations [98] and because participation in collaborative software development is increasing [7,185].…”

Section: Topics For Future Researchmentioning

confidence: 99%

Adoption of open source software in software-intensive organizations – A systematic literature review

Hauge¹,

Ayala²,

Conradi³

2010

Information and Software Technology

193

113

View full text Add to dashboard Cite

Context: Open source software (OSS) is changing the way organizations develop, acquire, use, and commercialize software. Objective: This paper seeks to identify how organizations adopt OSS, classify the literature according to these ways of adopting OSS, and with a focus on software development evaluate the research on adoption of OSS in organizations. Method: Based on the systematic literature review method we reviewed publications from 24 journals and seven conference and workshop proceedings, published between 1998 and 2008. From a population of 24289 papers, we identified 112 papers which provide empirical evidence on how organizations actually adopt OSS. Results: We show that adopting OSS involves more than simply using OSS products. We moreover provide a classification framework consisting of six distinctly different ways in which organizations adopt OSS. This framework is used to illustrate some of the opportunities and challenges organizations meet when approaching OSS, to show that OSS can be adopted successfully in different ways, and to organize and review existing research. We find that this research does not sufficiently describe the context of the organizations studied. It is furthermore fragmented and fails to benefit fully from related research fields. Finally, we present directions for future research.

show abstract

“…Project-specific communities formed around Lucent's SIP transaction manager [16,17], SAP's mobile retail prototype [42], Philips' medical imaging components [63,59,61], and projects at HP [30] and Microsoft [31]. Within an IS program, multiple project-specific communities can exist.…”

Section: B) Values Of Open Collaboration: Is Implements the Three Valmentioning

confidence: 99%

Inner Source Definition, Benefits, and Challenges

Capraro

Riehle

2016

ACM Comput. Surv.

View full text Add to dashboard Cite

Inner Source (IS) is the use of open source software development practices and the establishment of an open source-like culture within organizations. The organization may still develop proprietary software but internally opens up its development. A steady stream of scientific literature and practitioner reports indicates the interest in this research area. However, the research area lacks a systematic assessment of known research work: No model exists that defines IS thoroughly. Various case studies provide insights into IS programs in the context of specific organizations but only few publications apply a broader perspective. To resolve this, we performed an extensive literature survey and analyzed 43 IS related publications plus additional background literature. Using qualitative data analysis methods, we developed a model of the elements that constitute IS. We present a classification framework for IS programs and projects and apply it to lay out a map of known IS endeavors. Further, we present qualitative models summarizing the benefits and challenges of IS adoption. The survey provides the first broad review of IS literature and systematic arrangement of IS research results.

show abstract

Commodification of Industrial Software: A Case for Open Source

Cited by 72 publications

References 5 publications

Open innovation using open source tools: a case study at Sony Mobile

Open innovation using open source tools: a case study at Sony Mobile

Adoption of open source software in software-intensive organizations – A systematic literature review

Inner Source Definition, Benefits, and Challenges

Contact Info

Product

Resources

About