원문정보
초록
영어
Technical debt management requires means to identify, track, and resolve technical debt in the various software project artifacts. There are several approaches for identifying technical debt from the software implementation, but they all have their shortcomings in maintaining this information. Readily available information is a cornerstone of successful technical debt management integration. As such, this paper presents a two-partite case study that explores the role of dependency propagation in the accumulation of technical debt for software implementations. The first part, targeting a refactorization project in the ViLLE education platform, identifies a clear relation between the propagation and the accumulation in addition to making notions about special propagation characteristics. The second part considers bug reports for the Eclipse IDE, and, thus, provides further verification in observing a similar relationship at a lower implementation abstraction level for this independent data set. We conclude that formalization of this relation should lead to solutions for the technical debt information maintenance problem. As such, we use the case study herein to further improve the propagation model applied in our DebtFlag technical debt management tool.
목차
1. Introduction
2. Technical Debt
2.1 Technical Debt in Software Implementations
2.2 Related Work on Technical Debt Propagation
3. First Case - Class Level Mechanics
3.1 Research Problem
3.2 Target System
3.3 Data Collection and Analysis
4. Results
4.1 Technical Debt Propagation Trees
4.2 Analysis of the Technical Debt Propagation Trees
5. Conclusions and Validity
6. Second Case - Class Member Level Mechanics
6.1 Execution
7. Resulting Technical Debt Propagation Trees
8. Conclusions and Relation with the Former Part
9. Future Work
Acknowledgements
References