Auflistung nach Autor:in "Capraro, Maximilian"
1 - 2 von 2
Treffer pro Seite
Sortieroptionen
- KonferenzbeitragInner Source Definition, Benefits, and Challenges(Software Engineering and Software Management 2019, 2019) Capraro, Maximilian; Riehle, DirkInner source (IS) is the use of open source software development practices within an organization. The organization still develops proprietary software but internally opens up its development. 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 a specific context but only few publications apply a broader perspective. To resolve this, we performed an extensive literature survey and analyzed 43 IS related publications. Using qualitative data analysis methods, we developed a model of elements that constitute IS. We present a classification framework for IS and apply it to lay out a map of known IS endeavors. Further, we present qualitative models summarizing the benefits and challenges of IS. This article is an extended abstract of [CR17].
- KonferenzbeitragInner Source in Platform-based Product Engineering(Software Engineering und Software Management 2018, 2018) Riehle, Dirk; Capraro, Maximilian; Kips, Detlef; Horn, LarsDie vorzustellende Veröffentlichung wurde in IEEE Transactions on Software Engineering vol. 42, no. 12 (December 2016), 1162-1177, veröffentlicht. Der Titel lautet Inner Source in Platform-Based Product Engineering. Es folgt der Artikel-Abstract: Inner source is an approach to collaboration across intra-organizational boundaries for the creation of shared reusable assets. Prior project reports on inner source suggest improved code reuse and better knowledge sharing. Using a multiple-case case study research approach, we analyze the problems that three major software development organizations were facing in their product line engineering efforts. We find that a root cause, the separation of product units as profit centers from a platform organization as a cost center, leads to delayed deliveries, increased defect rates, and redundant software components. All three organizations assume that inner source can help solve these problems. The article analyzes the expectations that these companies were having towards inner source and the problems they were experiencing in its adoption. Finally, the article presents our conclusions on how these organizations should adapt their existing engineering efforts.