一句话：指出技术债管理缺乏系统化流程，主张将其与软件质量管理流程整合。
技术债被定义为在软件系统的设计、开发与部署过程中因走捷径而产生的维护义务，已有研究表明它会显著影响软件系统的可靠性与长期演化。学术界已不再仅把技术债当作隐喻，并开始积累关于其经济影响的有力实证证据，但工业界从业者仍感到管理技术债是一场艰难的平衡。尽管人们对软件产品开发中技术债管理重要性的认识不断提高，可用于在软件生产中实施技术债管理的系统化流程却仍不普及。本文（摘要层面）着眼于这一问题，强调需要把技术债管理流程与软件质量管理流程结合起来，以弥补流程缺失带来的实践困难。
Technical debt, defined as the maintenance obligations arising from shortcuts taken during the design, development, and deployment of software systems, has been shown to significantly impact the reliability and long-term evolution of software systems [1], [2]. Although academic research has moved beyond using technical debt only as a metaphor, and has begun compiling strong empirical evidence on the economic implications of technical debt, industry practitioners continue to find managing technical debt a challenging balancing act [3]. Despite the increasing awareness of the importance of managing technical debt in software product development, systematic processes for implementing technical debt management in software production have not been readily available.
DOI 原文 ·
@inproceedings{paperbot4507,
title = {Integrating technical debt management and software quality management processes},
author = {Narayan Ramasubbu and Chris Kemerer},
booktitle = {ICSE},
year = {2018},
doi = {10.1145/3180155.3182529}
}