Issue No.06 - Nov.-Dec. (2012 vol.29)
pp: 22-27
Erin Lim , Aquatic Informatics
Nitin Taksande , Novasom
Carolyn Seaman , University of Maryland, Baltimore County
An interview study involving 35 practitioners from a variety of domains aimed to characterize technical debt at the ground level to find out how software practitioners perceive it. The study also aimed to understand the context in which technical debt occurs, including its causes, symptoms, and effects. In addition, the study focused on how practitioners currently deal with technical debt. This analysis paints a picture of a large, complex balancing act of various short- and long-term concerns. The Web Extra gives the interview questions used by Erin Lim, Nitin Taksande, and Carolyn Seaman.
Interviews, Risk management, Investments, Software testing, Documentation, Software quality, software engineering, maintenance management, software maintenance, technical debt
Erin Lim, Nitin Taksande, Carolyn Seaman, "A Balancing Act: What Software Practitioners Have to Say about Technical Debt", IEEE Software, vol.29, no. 6, pp. 22-27, Nov.-Dec. 2012, doi:10.1109/MS.2012.130
1. W. Cunningham, "The WyCash Portfolio Management System," Addendum to Proc. Object-Oriented Programming Systems, Languages, and Applications, ACM, 1992, pp. 29–30.
2. T. Klinger et al., "An Enterprise Perspective on Technical Debt," Proc. Workshop Managing Technical Debt, ACM, 2011, pp. 35–38.
3. M. Fowler, "Technical Debt," blog, 26 Feb. 2003;
4. S. McConnell, "10x Software Development," blog, 1 Nov. 2007; archive/2007/11/01technical-debt-2.aspx.
5. N. Brown et al., "Managing Technical Debt in Software-Reliant Systems," Proc. Workshop Managing Technical Debt, ACM, 2010, pp. 47–52.
6. C. Seaman, "Qualitative Methods," Guide to Advanced Empirical Software Engineering, F. Shull et al., eds., Springer, 2008, pp. 35–62.
7. C. Seaman, and Y. Guo, "Measuring and Monitoring Technical Debt," Advances in Computers, vol. 82, 2011, pp. 25–46.
8. N. Zazworka et al., "Investigating the Impact of Design Debt on Software Quality," Proc. Workshop Managing Technical Debt, ACM, 2011, pp. 17–23.
9. J.-L. Letouzey, "The SQALE Method for Evaluating Technical Debt," Proc. 3rd Int'l Workshop Managing Technical Debt, IEEE CS, 2012, pp. 31–36.
10. S. Wong et al., "Detecting Software Modularity Violations," Proc. 33rd Int'l Conf. Software Eng. (ICSE 11), ACM, 2011, pp. 411–420.