Identify Impacts of Evolving Third Party Components on Long-Living Software Systems

Klatt, Benjamin; Durdik, Zoya; Koziolek, Heiko; Krogmann, Klaus; Stammel, Johannes; Weiß, Roland

doi:10.1109/csmr.2012.59

Cited by 5 publications

(5 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Klatt et al [12] suggested an approach to identify the impact of evolving third-party components on long-living software systems. They use a white-box impact analysis which requires access to the third-party source code and combined it with data from bug trackers and quality analyses on the third-party code.…”

Section: Third-party Reusementioning

confidence: 99%

See 1 more Smart Citation

Facts and Fallacies of Reuse in Practice

Bauer

2013

2013 17th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

Abstract-Despite the positive effects of reuse claimed in a significant amount of research, anecdotal evidence indicates that industry is not yet experiencing the expected benefit. This dissertation proposal aims to investigate these indicators and therefore addresses reuse from an industrial point of view. As a first step, it empirically assesses the general state of reuse in practice. This is achieved via a large-scale online questionnaire distributed to multiple companies. Complementing the questionnaire, extensive interviews are being scheduled with developers and project managers of the respective companies. The goal is to interview approximately 10 employees per company. Three companies have already committed to the interview phase and contact with seven further companies is currently being established. In a second step, the findings of the study will be used to extract the context and type of reuse, as well as success factors and hindrances. This information forms the basis for an analytical assessment model for internal code reuse, which is developed in a third step. It will capture a range of different aspects of reuse in practice and will be combined with a process to evaluate the adequacy of reuse. The planned result is a larger assessment framework for evaluating the reuse (management) process within a project as well as a multiproject context. As a result, guidelines for code organization should be developed and tested for their effects in improving reuse in one or more of the industrial partners projects.

show abstract

Section: Third-party Reusementioning

confidence: 99%

“…Also organisational factors have been considered [8]. Recently, the focus has shifted to identifying maintenance consequences and potential risks introduced by library reuse [9]- [12]. Consequently, the quality assessment of reuse aspects is emerging as research direction [13].…”

Section: Introductionmentioning

confidence: 99%

Facts and Fallacies of Reuse in Practice

Bauer

2013

2013 17th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

show abstract

“…The percentage of API utilization is computed as fraction between the number of distinct API methods called and the total number of API methods in the library. The complete tool support is available as a ConQAT extension 5 http://www.conqat.org/ and can be downloaded as a self-contained bundle including ConQAT 6 .…”

Section: Tool Supportmentioning

confidence: 99%

“…Klatt et al [6] suggested an approach to identify the impact of evolving third-party components on long-living software systems. They use a white-box impact analysis which requires access to the third-party source code and combined it with data from bug trackers and quality analyses on the third-party code.…”

Section: A Analysis Of Third-party Library Usagementioning

confidence: 99%

A structured approach to assess third-party library usage

Bauer

Heinemann

Deissenboeck³

2012

2012 28th IEEE International Conference on Software Maintenance (ICSM)

View full text Add to dashboard Cite

Abstract-Modern software systems build on a significant number of external libraries to deliver feature-rich and highquality software in a cost-efficient and timely manner. As a consequence, these systems contain a considerable amount of third-party code. External libraries thus have a significant impact on maintenance activities in the project. However, most approaches that assess the maintainability of software systems largely neglect this important factor. Hence, risks may remain unidentified, threatening the ability to effectively evolve the system in the future. We propose a structured approach to assess the third-party library usage in software projects and identify potential problems. Industrial experience strongly influences our approach, which we designed in a lightweight way to enable easy adoption in practice. We present an industrial case study showing the applicability of the approach to a real-world software system.

show abstract

“…However, anecdotal evidence from industrial research projects indicates that these current research efforts have not yet significantly impacted the software development industry. Secondly, systems built on external libraries face novel challenges in maintenance, entailed by their dependencies and the, usually, ad-hoc way libraries are integrated [4,23,15]. However, we as research community have little knowledge on how reuse is currently effected in practice.…”

Section: Introductionmentioning

confidence: 99%

An exploratory study on reuse at google

Bauer¹,

Eckhardt²,

Hauptmann³

et al. 2014

Proceedings of the 1st International Workshop on Software Engineering Research and Industrial Practices

View full text Add to dashboard Cite

Software reuse is a challenging and multifaceted topic. Significant research effort has been spent to address technical and organizational aspects. However, adoption of proposed practices and novel approaches often proceeds slowly. Additionally, little is known on how reuse is currently effected in practice and which solutions have proven useful. This paper aims to shed light on the matter by studying the current practice of reuse at Google. We conduct an exploratory study with a total of 49 participants of which 39 answered our online questionnaire and 10 participated in our 1h interviews. We assess reuse practices, success factors and challenges and collect ideas for improvement.We distill our findings to provide practitioners with examples of scalable reuse practices and detail on prerequisites required to implement/tailor a similar reuse approach. Furthermore, we point out open issues to support researchers and practitioners alike to align their efforts for developing solutions.

show abstract

Identify Impacts of Evolving Third Party Components on Long-Living Software Systems

Cited by 5 publications

References 8 publications

Facts and Fallacies of Reuse in Practice

Facts and Fallacies of Reuse in Practice

A structured approach to assess third-party library usage

An exploratory study on reuse at google

Contact Info

Product

Resources

About