论文信息 - Technical Debt: From Metaphor to Theory and Practice

Technical Debt: From Metaphor to Theory and Practice

The metaphor of technical debt in software development was introduced two decades ago to explain to nontechnical stakeholders the need for what we call now "refactoring." As the term is being used to describe a wide range of phenomena, this paper proposes an organization of the technical debt landscape, and introduces the papers on technical debt contained in the issue.

[1] Jane Cleland-Huang,et al. The incremental funding method: data-driven software development , 2004, IEEE Software.

[2] Alan MacCormack,et al. Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code , 2006, Manag. Sci..

[3] Chris Sterling,et al. Managing Software Debt: Building for Inevitable Change , 2010 .

[4] Robert L. Nord,et al. In Search of a Metric for Managing Architectural Technical Debt , 2012, 2012 Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture.

[5] Robert L. Nord,et al. Enabling Agility Through Architecture , 2010 .

[6] Carolyn B. Seaman,et al. A Balancing Act: What Software Practitioners Have to Say about Technical Debt , 2012, IEEE Softw..

[7] Robert L. Nord,et al. Technical debt in software development: from metaphor to theory report on the third international workshop on managing technical debt , 2012, SOEN.

[8] Ward Cunningham,et al. The WyCash portfolio management system , 1992, OOPSLA '92.