Challenges and strategies in the use of Open Source Software by Independent Software Vendors

Ven, Kris; Mannaert, Herwig

doi:10.1016/j.infsof.2007.09.001

Cited by 52 publications

(53 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, influence on feature selection and road-mapping may be gained through a more active participation, as many OSS communities are based on meritocracy principles (Jensen and Scacchi 2007). Also, some benefits may first be fully utilized after contributing back certain parts to the OSS community (Ven and Mannaert 2008). For example, by correcting bugs, actively participating in discussions and contributing new features, a software organization might reduce maintenance cost compared to proprietary software development (Stuermer et al 2009).…”

Section: Explains the Term Open Innovation (Oi) As "A Paradigm That Amentioning

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: Explains the Term Open Innovation (Oi) As "A Paradigm That Amentioning

confidence: 99%

“…We cannot afford to re-work everything". Due to these reasons, the Tools department is keen on not keeping stuff for themselves, but contributing everything (Ven and Mannaert 2008;Wnuk et al 2012). An issue in Jenkins is that there exist numerous combinations and settings of plug-ins.…”

Section: When Developers Upload a Change Which Can Have Several Revmentioning

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

“…These factors have been also mentioned by Ven and Mannaert [10]. In addition, most integrators that did not contribute to the communities also mentioned that they try to use the component as is (i.e., without modifications).…”

Section: Discussion Of Main Findingsmentioning

confidence: 90%

“…Several barriers to contribute back to the community have been also investigated as for instance by Ven and Mannaert [10] that found that deciding not to contribute can also be risky as one may be forced to maintain a parallel copy of the product.…”

Section: Background and Related Workmentioning

confidence: 99%

OSS Integration Issues and Community Support: An Integrator Perspective

Ayala

Cruzes

Nguyen

et al. 2012

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Abstract. The reuse and integration of Open Source Software (OSS) components provided by OSS communities is becoming an economical and strategic need for today's organizations. The integration of OSS components provides many benefits, but also risks and challenges. One of the most important risks is the lack of effective and timely OSS community support for dealing with possible integration problems. For gaining an understanding of the common problems that organizations face when integrating OSS components, and the role played by OSS communities, we performed an exploratory study on 25 OSS integration projects from different European organizations. The results show that the main way of reducing integration problems was the use of OSS components from well-established communities; therefore very few integration problems were identified. In most of the cases these problems were successfully solved with the support from the OSS community and/or colleagues. In addition, contrary to the common belief that understanding code from someone else is a hard and undesirable task, some integrators consider OSS code even more understandable than their own code.

show abstract

“…Once OSS components are integrated, they must be maintained as part of an application. If custom changes were made during the integration phase, these may have to be separately maintained if the changes are not incorporated back into the source base that is maintained by the OSS community [21]. An OSS integrator can choose to actively participate in the development or roadmap planning of the OSS product [17,21].…”

Section: Component-based Development With Open Source Softwarementioning

confidence: 99%

The Importance of Architectural Knowledge in Integrating Open Source Software

Stol

Babar

Avgeriou

2011

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Abstract. Open Source Software (OSS) is increasingly used in ComponentBased Software Development (CBSD) of large software systems. An important issue in CBSD is selection of suitable components. Various OSS selection methods have been proposed, but most of them do not consider the software architecture aspects of OSS products. The Software Architecture (SA) research community refers to a product's architectural information, such as design decisions and underlying rationale, and used architecture patterns, as Architecture Knowledge (AK). In order to investigate the importance of AK of OSS components in integration, we conducted an exploratory empirical study. Based on in-depth interviews with 12 IT professionals, this paper presents insights into the following questions: 1) what AK of OSS is needed? 2) Why is AK of OSS needed? 3) Is AK of OSS generally available? And 4) what is the relative importance of AK? Based on these new insights, we provide a research agenda to further the research field of software architecture in OSS.

show abstract

Challenges and strategies in the use of Open Source Software by Independent Software Vendors

Cited by 52 publications

References 19 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

OSS Integration Issues and Community Support: An Integrator Perspective

The Importance of Architectural Knowledge in Integrating Open Source Software

Contact Info

Product

Resources

About