Long-Term Evaluation of Technical Debt in Open-Source Software

@article{Molnar2020LongTermEO,
  title={Long-Term Evaluation of Technical Debt in Open-Source Software},
  author={Arthur-Jozsef Molnar and Simona Motogna},
  journal={Proceedings of the 14th ACM / IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)},
  year={2020}
}
  • Arthur-Jozsef Molnar, S. Motogna
  • Published 27 July 2020
  • Computer Science
  • Proceedings of the 14th ACM / IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)
Background: A consistent body of research and practice have identified that technical debt provides valuable and actionable insight into the design and implementation deficiencies of complex software systems. Existing software tools enable characterizing and measuring the amount of technical debt at selective granularity levels; by providing a computational model, they enable stakeholders to measure and ultimately control this phenomenon. Aims: In this paper we aim to study the evolution and… Expand
Towards better data discovery and collection with flow-based programming
TLDR
The potential of flow-based programming (FBP) for simplifying data discovery and collection in software systems and an insight into the current trend that prioritizes model development over data quality management is provided. Expand

References

SHOWING 1-10 OF 45 REFERENCES
Investigating Architectural Technical Debt accumulation and refactoring over time: A multiple-case study
TLDR
A taxonomy of the factors and their influence in the accumulation of Architectural Technical Debt is compiled, and two qualitative models of how the debt is accumulated and refactored over time in the studied companies are provided. Expand
Longitudinal Evaluation of Open-Source Software Maintainability
TLDR
This study covers the entire 18 year development history and all released versions for three complex, open-source applications, and determines the maintainability for each version using the proposed models, compare obtained results and use manual source code examination to put them into context. Expand
Technical Debt Cripples Software Developer Productivity: A Longitudinal Study on Developers’ Daily Software Development Work
TLDR
The analysis of the reported wasted time revealed that developers waste, on average, 23% of their development time due to TD and that they are frequently forced to introduce new TD due to already existing TD. Expand
An Empirical Study of Technical Debt in Open-Source Software Systems
Technical debt (TD) is a term coined by agile software pioneer Ward Cunningham to account for the added software-system effort or cost resulting from taking early software project shortcuts. The debtExpand
An empirical model of technical debt and interest
TLDR
The technical debt metaphor is revisited, and an approach to quantify debts and interest and how the results provide useful insights on important questions related to IT investment such as the return on investment (ROI) in software quality improvement. Expand
The Correspondence Between Software Quality Models and Technical Debt Estimation Approaches
TLDR
A case study across 10 releases of 10 open source systems in order to evaluate three proposed methods of technical debt principal estimation found that only one estimation technique had a strong correlation to the quality attributes reusability and understand ability. Expand
A Longitudinal Study of Identifying and Paying Down Architecture Debt
TLDR
Quantitative evidence is presented, augmented by qualitative evidence gathered from in-depth interviews with BrightSquid's architects, about the costs and benefits of paying down architecture debt in practice to make software less costly and more amenable to change. Expand
An enterprise perspective on technical debt
TLDR
It is found that in many cases, the decision to acquire technical debt is not made by technical architects, but rather by non-technical stakeholders who cause the project to acquire new technical debt or discover existing technical debt that wasn't previously visible. Expand
An Empirical Study on Technical Debt in a Finnish SME
TLDR
From this study, it is learned that learning, careful estimations, and continuous improvement could be good strategies to mitigate Technical Debt. Expand
Longitudinal Evaluation of Software Quality Metrics in Open-Source Applications
TLDR
This paper proposes a longitudinal evaluation of the metric values and their relations in the context of three complex, open-source applications, covering the entire 18 year development history of the targeted applications. Expand
...
1
2
3
4
5
...