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

Hauge, Øyvind; Ayala, Claudia; Conradi, Reidar

doi:10.1016/j.infsof.2010.05.008

Cited by 193 publications

(142 citation statements)

References 181 publications

Supporting

Mentioning

113

Contrasting

Unclassified

Order By: Relevance

“…The rapid growth in scale and complexity of software systems, together with the availability of third party software components, such as Commercial Off-The-Shelf (COTS) or Open Source Software (OSS) components, increase the adoption of component-based software development (CBSD) in software industry [1]. This adoption demands specialized software development processes that aim at supporting Off-The-Shelf (OTS, including both COTS and OSS) component acquisition, especially Requirements Engineering (RE) processes.…”

Section: Introductionmentioning

confidence: 99%

Collaborative Resolution of Requirements Mismatches When Adopting Open Source Components

Ánh

Cruzes

Conradi

et al. 2012

Requirements Engineering: Foundation for Software Quality

Self Cite

View full text Add to dashboard Cite

Abstract. [Context and motivation]There is considerable flexibility in requirements specifications (both functional and non-functional), as well as in the features of available OSS components. This allows a collaborative matching and negotiation process between stakeholders such as: customers, software contractors and OSS communities, regarding desired requirements versus available and thus reusable OSS components.[Problem] However, inconclusive research exists on such cooperative processes. Not much empirical data exists supporting the conduction of such research based on observation of industrial OSS adoption projects. This paper investigates how functional and non-functional requirement mismatches are handled in practice.[Results] We found two common approaches to handle functional mismatches. The main resolution approach is to get the components changed by the development team, OSS community or commercial vendor. The other resolution approach is to influence requirements, often by postponing requirements. Overall, non-functional requirements are satisfactorily achieved by using OSS components. Last but not least, we found that the customer involvement could enhance functional mismatch resolution while OSS community involvement could improve nonfunctional mismatch resolution.[Contribution] Our data suggests that the selecting components should be done iteratively with close collaboration with stakeholders. Improvement in requirement mismatch resolution to requirements could be achieved by careful consideration of mismatches size, requirements flexibility and components quality.

show abstract

Section: Introductionmentioning

confidence: 99%

Collaborative Resolution of Requirements Mismatches When Adopting Open Source Components

Ánh

Cruzes

Conradi

et al. 2012

Requirements Engineering: Foundation for Software Quality

Self Cite

View full text Add to dashboard Cite

show abstract

“…Recent systematic reviews reveal that integration is one of the most popular strategies of adopting OSS [2], [4].…”

Section: Background and Related Workmentioning

confidence: 99%

“…Even though there is a considerable body of research on the challenges of integrating OSS components in the development of software products [2], [4], the majority of these works refer to success stories derived from single case studies or experience reports that provide very limited information about the real industrial landscape of companies integrating OSS components. Moreover, the role that OSS communities play on supporting integrators to solve their integration problems has not been further explored.…”

Section: Background and Related Workmentioning

confidence: 99%

See 1 more Smart Citation

OSS Integration Issues and Community Support: An Integrator Perspective

Ayala

Cruzes

Nguyen

et al. 2012

IFIP Advances in Information and Communication Technology

Self Cite

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

“…Open Source Software (OOS) wide spread adoption, including in the industry, has raised increased concerns related with software quality and certification [3]. In this context, the CROSS research project 4 aims at developing software analysis techniques that can be combined to assess open source software projects.…”

Section: Introductionmentioning

confidence: 99%

Open Source Software Documentation Mining for Quality Assessment

Carvalho

Simões

Almeida

2013

Advances in Intelligent Systems and Computing

View full text Add to dashboard Cite

Abstract. Besides source code, the fundamental source of information about Open Source Software lies in documentation, and other non source code files, like README, INSTALL, or HowTo files, commonly available in the software ecosystem. These documents, written in natural language, provide valuable information during the software development stage, but also in future maintenance and evolution tasks. DMOSS 3 is a toolkit designed to systematically assess the quality of non source code text found in software packages. The toolkit handles a package as an attribute tree, and performs several tree traverse algorithms through a set of plugins, specialized in retrieving specific metrics from text, gathering information about the software. These metrics are later used to infer knowledge about the software, and composed together to build reports that assess the quality of specific features of the software. This paper discusses the motivations for this work, continues with a description of the toolkit implementation and design goals. Follows an example of its usage to process a software package, and the produced report. Finally some final remarks and trends for future work are presented.

show abstract

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

Cited by 193 publications

References 181 publications

Collaborative Resolution of Requirements Mismatches When Adopting Open Source Components

Collaborative Resolution of Requirements Mismatches When Adopting Open Source Components

OSS Integration Issues and Community Support: An Integrator Perspective

Open Source Software Documentation Mining for Quality Assessment

Contact Info

Product

Resources

About