The Community for Technology Leaders
RSS Icon
Issue No.06 - Nov.-Dec. (2011 vol.28)
pp: 29-31
Technical debt is a widely used metaphor to illustrate and discuss the consequences of design and coding decisions over time. The architect's position on technical debt, however, should be driven more by business aspects and less by technical concerns. Only then can architects assess when to incur technical debt and whether or not to retire it, when to retire it, and how.
technical debt, software, software engineering, architecture
Frank Buschmann, "To Pay or Not to Pay Technical Debt", IEEE Software, vol.28, no. 6, pp. 29-31, Nov.-Dec. 2011, doi:10.1109/MS.2011.150
1. W. Cunningham, "The WyCash Portfolio Management System," Addendum to Proc. Object-Oriented Programming Systems, Languages, and Applications (OOPSLA 92), ACM Press, 1992, pp. 29–30, doi:10.1145/157709.157715.
2. J. Kerievsky, Refactoring to Patterns, Addison-Wesley, 2004.
3. B. Appleton, "Technical Debt—Definition and Resources," blog, 24 Jun. 2009, .
4. F. Buschmann, "Learning from Failure, Part 1: Scoping and Requirements Woes," IEEE Software, vol. 26, no. 6, 2009, pp. 68–69.
5. F. Buschmann, "Learning from Failure, Part 2: Featuritis, Performitis, and Other Diseases," IEEE Software, vol. 27, no. 1, 2010, pp. 10–11.
6. F. Buschmann, "Learning from Failure, Part 3: On Hammers and Nails, and Falling in Love with Technology and Design," IEEE Software, vol. 27, no. 2, 2010, pp. 49–51.
7. S. McConnell, Managing Technical Debt, white paper, Construx Software, 2008, www.construx.comPage.aspx?cid=2801.
8. F. Buschmann, "The Pragmatic Architect—Gardening Your Architecture: Part 1," IEEE Software, vol. 28, no. 4, pp. 92–94.
9. F. Buschmann, "The Pragmatic Architect − Gardening Your Architecture, Part 2, IEEE Software, vol. 28, no. 5, pp. 21–23.
448 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool