To pay or not to pay technical debt

IEEE Software

Volumn 28, Issue 6, 2011, Pages 29-31

  Buschmann, Frank ^a  

^a SIEMENS AG   (Germany)

Author keywords

architecture; software; software engineering; technical debt

Indexed keywords

BUSINESS ASPECTS; TECHNICAL DEBT;

SOFTWARE ENGINEERING;

EID: 80054896104     PISSN: 07407459     EISSN: None     Source Type: Journal    
DOI: 10.1109/MS.2011.150     Document Type: Article

References (9)

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, http://bradapp. blogspot.com/2009/06/technical-debtdefinition-and- resources.html.
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.com/Page.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.