Auflistung nach Autor:in "Riehle, Dirk"
1 - 9 von 9
Treffer pro Seite
Sortieroptionen
- Konferenzbeitrag3rd Workshop on Continuous Software Engineering (CSE)(Software Engineering und Software Management 2018, 2018) Lichter, Horst; Krusche, Stephan; Riehle, Dirk; Steffens, Andreas
- KonferenzbeitragCSE 2016: workshop on continuous software engineering(Software Engineering 2016, 2016) Lichter, Horst; Brügge, Bernd; Riehle, Dirk
- KonferenzbeitragCSE 2017 - 2nd Workshop on Continuous Software Engineering(Software Engineering 2017, 2017) Lichter, Horst; Krusche, Stephan; Riehle, Dirk
- KonferenzbeitragDeveloper belief vs. reality: the case of the commit size distribution(Software Engineering 2012, 2012) Riehle, Dirk; Kolassa, Carsten; Salim, Michel A.The design of software development tools follows from what the developers of such tools believe is true about software development. A key aspect of such beliefs is the size of code contributions (commits) to a software project. In this paper, we show that what tool developers think is true about the size of code contributions is different by more than an order of magnitude from reality. We present this reality, called the commit size distribution, for a large sample of open source and selected closed source projects. We suggest that these new empirical insights will help improve software development tools by aligning underlying design assumptions closer with reality.
- ZeitschriftenartikelGeschäftsrisiken und Governance von Open Source in Softwareprodukten(HMD Praxis der Wirtschaftsinformatik: Vol. 49, No. 1, 2012) Helmreich, Martin; Riehle, DirkenIn fast jedem Softwareprodukt, auch in großer Standardsoftware, sind heute Open-Source-Komponenten enthalten. Die Hersteller dieser Software müssen die Geschäftsrisiken, die mit der Integration von Open-Source-Software in kommerzielle Produkte verbunden sind, verstehen und vernünftig managen. Dieser Beitrag zeigt ein Modell verschiedener rechtlicher, technischer und sozialer Risiken auf, die durch unkontrollierten Einsatz von Open-Source-Software entstehen, und erläutert ausgewählte Erfolgsmethoden der Open Source Governance, die von führenden Firmen angewandt werden. Das Modell ist das Analyseergebnis von fünf mit großen deutschen Softwareherstellern geführten Interviews sowie weiterer Literaturrecherche.
- KonferenzbeitragImproving traceability of requirements through qualitative data analysis(Software-engineering and management 2015, 2015) Kaufmann, Andreas; Riehle, Dirk
- 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.
- KonferenzbeitragThe QDAcity-RE Method for Structural Domain Modeling Using Qualitative Data Analysis(Software Engineering und Software Management 2018, 2018) Kaufmann, Andreas; Riehle, DirkThe creation of domain models from qualitative input relies heavily on experience. An uncodified ad-hoc modeling process is still common and leads to poor documentation of the analysis. In this article we present a new method for domain analysis based on qualitative data analysis (QDA). The method helps identify inconsistencies, ensures a high degree of completeness, and inherently provides traceability from analysis results back to stakeholder input. These traces do not have to be documented after the fact. We evaluate our approach using four exploratory studies.