Analyzing the Rework Time and Severity of Code Debt: A Case Study Using Technical Debt Catalogs

敏捷环境中管理技术债务的初步模型

A Preliminary Model for Managing Technical Debt in an Agile Environment

提出一个集成管理敏捷环境中非自愿技术债务的初步模型，通过动态策略平衡新开发与修复，并考虑边际价值递减，经敏感性分析和蒙特卡洛模拟验证。

Identifying and Managing Technical Debt in Database Normalization Using Machine Learning and Trade-off Analysis

Technical debt is a metaphor that describes the long term effects of shortcuts taken in software development activities to achieve near term goals. In this study, we explore a new context of technical debt that relates to database normalization design decisions. We posit that ill normalized databases can have long term ramifications on data quality, performance degradation and maintainability costs over time, just like debts accumulate interest. Conversely, conventional database approaches would suggest normalizing weakly normalized tables, this can be a costly process in terms of effort and e…

敏捷软件开发中的非技术债务

Non Technical Debt in Agile Software Development

本研究基于NODLA项目的调查、访谈与统计分析，识别大规模敏捷开发中四类非技术债务的驱动因素与影响，并提出减少债务、恢复敏捷性的循证策略。

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

Existing software tools enable characterizing and measuring the amount of technical debt at selective granularity levels. In this paper we aim to study the evolution and characteristics of technical debt in open-source software. We carry out a longitudinal study that covers the entire development history of several complex applications. We study how technical debt is introduced in software, as well as identify how developers handle its accumulation over the long term. We carried out our evaluation using three complex, open-source Java applications. All 110 released versions, covering more than…

A Longitudinal Study of Identifying and Paying Down Architectural Debt

Architectural debt is a form of technical debt that derives from the gap between the architectural design of the system as it "should be" compared to "as it is". We measured architecture debt in two ways: 1) in terms of system-wide coupling measures, and 2) in terms of the number and severity of architectural flaws. In recent work it was shown that the amount of architectural debt has a huge impact on software maintainability and evolution. Consequently, detecting and reducing the debt is expected to make software more amenable to change. This paper reports on a longitudinal study of a healthc…

Prevalence, Common Causes and Effects of Technical Debt: Results from a Family of Surveys with the IT Industry

The technical debt (TD) metaphor describes actions made during various stages of software development that lead to a more costly future regarding system maintenance and evolution. According to recent studies, on average 25% of development effort is spent, i.e. wasted, on TD caused issues in software development organizations. However, further research is needed to investigate the relations between various software development activities and TD. The objective of this study is twofold. First, to get empirical insight on the understanding and the use of the TD concept in the IT industry. Second, …