Issue No.06 - Nov.-Dec. (2011 vol.28)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2011.150
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