Open Source Collaboration for Fostering Off-The-Shelf Components Selection

Ayala, Claudia; Søensen, Carl-Fredrik; Conradi, Reidar; Franch, Xavier; Li, Jingyue

doi:10.1007/978-0-387-72486-7_2

Cited by 15 publications

(16 citation statements)

References 17 publications

(28 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…4 (119) exceeds the number of OSS projects that have SA documentation (108), because one OSS project may employ several formats (e.g., both Html and picture) to document SA. Design information contained in OSS projects, e.g., architectural information, is often not detailed enough, and usually unstructured, presented in many different forms (e.g., web pages, forums, files, mailing lists) [9]. As presented in Section III.C, in this survey, we focus on the architectural information archived within the OSS repositories in documents, e.g., files and web pages.…”

Section: B) Project Types and Sadmentioning

confidence: 99%

See 1 more Smart Citation

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

Ding

Liang

Tang

et al. 2014

2014 19th International Conference on Engineering of Complex Computer Systems

View full text Add to dashboard Cite

Abstract-Software architecture (SA) documentation provides a blueprint of a software-intensive system for the communication between stakeholders about the high-level design of the system. In open source software (OSS) development, a lack of SA documentation may hinder the use and further development of OSS, but how much "architecture" documentation is enough and appropriate is largely dependent on the contextual factors of development. In order to understand the state of the practice of SA documentation in OSS projects, we conducted a documentation-based survey to explore how SA is documented in OSS projects. Out of 2,000 OSS projects from four major OSS sources, we found that 108 projects have some SA documentation, which shows that the SA documentation is scarce in OSS development. We analyzed these 108 projects to understand what SA information has been documented and how they have been described. We have found that frequentlydocumented architectural information is model, system, and mission; natural language is the most frequently-used architectural language for specifying architectural information in OSS SA documents. The results also show that the likelihood that an OSS project will document SA is increased when more developers are involved in the project, and industry and research OSS projects are more likely to create SA documents than freelance projects.

show abstract

Section: B) Project Types and Sadmentioning

confidence: 99%

“…Consequently, the documentation of OSS projects is less emphasized in at least some OSS projects [8]. The information contained in those documents is presented in various forms such as Office files, web pages, and images [9].…”

Section: Introductionmentioning

confidence: 99%

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

Ding

Liang

Tang

et al. 2014

2014 19th International Conference on Engineering of Complex Computer Systems

View full text Add to dashboard Cite

show abstract

“…Searches in search engines usually yield huge, unwieldy sets of results. A centralized experience portal for sharing OTS componentrelated knowledge between organizations, probably using a global OTS Wiki [15] could be a solution. The results of our industrial surveys have revealed gaps between theory and practice regarding the use of OTS components.…”

Section: Fact 10mentioning

confidence: 99%

Development with Off-the-Shelf Components: 10 Facts

Conradi

Bunse

et al. 2009

IEEE Softw.

Self Cite

View full text Add to dashboard Cite

The paper summarizes the results of several industrial surveys on issues related to the development of systems using Commercial-Off-The-Shelf and Open Source Software components. The results demonstrate the following. (1) There is a discrepancy between academic theory and industrial practices regarding the use of components. One reason is that researchers have empirically evaluated only a few theoretical methods; hence, industrial practitioners currently have no reason to adopt them. Another reason might be that researchers have specified the contexts of application of only a small number of theories in sufficient detail to avoid misleading users. (2) Academic researchers often hold false assumptions about industry. For example, research on requirement negotiations often assumes that a client will be interested in, and be capable of, discussing the technical details of a project. However, in practice this is usually not true. In addition, the quality of a component in the final system is often attributed solely to component quality before integration, ignoring quality improvements by integrators during component integration.

show abstract

“…In addition, the results regarding RQ2 show that knowledge sharing between companies is rare. To facilitate knowledge sharing internally, one possible strategy is to have an internal component 'knowledge keeper' (Li et al 2006 between organizations, probably using a global OSS Wiki (Ayala et al 2007), could be a solution.…”

Section: Recommendation 4: Facilitate the Sharing Of Internal And Extmentioning

confidence: 99%

An empirical study on software development with open source components in the chinese software industry

Chen

et al. 2008

Softw Process Imprv Pract

Self Cite

View full text Add to dashboard Cite

Chinese software companies are increasingly using open source software (OSS) components in software development. Development with OSS components faces challenges with respect to component selection, component integration, licensing compliance, and system maintenance. Although these issues have been investigated in the industry in other countries, few similar studies have been performed in China. It is therefore difficult for Chinese software companies to be aware of their special issues and to make the necessary improvements. This article describes a questionnaire-based survey of software development with OSS components in Chinese software companies. Data from 47 completed development projects in 43 companies were collected. The results show that the main motivation behind using OSS components was their modifiability and low license cost. Using a web search engine was the most common method of locating OSS components. Local acquaintance and compliance requirements were the major decisive factors in choosing a suitable component. To avoid legal exposure, the common strategy was to use components without licensing constraints. The major cost of OSS-based projects was the cost to learn and understand OSS components. Almost 84% of the components needed bug fixing or other changes to the code. However, close participation with the OSS community was rare.

show abstract

Open Source Collaboration for Fostering Off-The-Shelf Components Selection

Cited by 15 publications

References 17 publications

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

Development with Off-the-Shelf Components: 10 Facts

An empirical study on software development with open source components in the chinese software industry

Contact Info

Product

Resources

About