Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
skip to main content
article

To Pay or Not to Pay Technical Debt

Published: 01 November 2011 Publication History

Abstract

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.

Cited By

View all
  • (2024)Security and privacy software creators' perspectives on unintended consequencesProceedings of the 33rd USENIX Conference on Security Symposium10.5555/3698900.3699083(3259-3276)Online publication date: 14-Aug-2024
  • (2024)An empirical study on the effectiveness of large language models for SATD identification and classificationEmpirical Software Engineering10.1007/s10664-024-10548-329:6Online publication date: 1-Oct-2024
  • (2021)How Far Have We Progressed in Identifying Self-admitted Technical Debts? A Comprehensive Empirical StudyACM Transactions on Software Engineering and Methodology10.1145/344724730:4(1-56)Online publication date: 23-Jul-2021
  • Show More Cited By

Recommendations

Comments

Information & Contributors

Information

Published In

cover image IEEE Software
IEEE Software  Volume 28, Issue 6
November 2011
99 pages

Publisher

IEEE Computer Society Press

Washington, DC, United States

Publication History

Published: 01 November 2011

Author Tags

  1. architecture
  2. software
  3. software engineering
  4. technical debt

Qualifiers

  • Article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 17 Jan 2025

Other Metrics

Citations

Cited By

View all
  • (2024)Security and privacy software creators' perspectives on unintended consequencesProceedings of the 33rd USENIX Conference on Security Symposium10.5555/3698900.3699083(3259-3276)Online publication date: 14-Aug-2024
  • (2024)An empirical study on the effectiveness of large language models for SATD identification and classificationEmpirical Software Engineering10.1007/s10664-024-10548-329:6Online publication date: 1-Oct-2024
  • (2021)How Far Have We Progressed in Identifying Self-admitted Technical Debts? A Comprehensive Empirical StudyACM Transactions on Software Engineering and Methodology10.1145/344724730:4(1-56)Online publication date: 23-Jul-2021
  • (2020)DATESSOProceedings of the IEEE/ACM 15th International Symposium on Software Engineering for Adaptive and Self-Managing Systems10.1145/3387939.3391604(96-107)Online publication date: 29-Jun-2020
  • (2017)Understanding Technical Debt at the Code Level from the Perspective of Software DevelopersProceedings of the XXXI Brazilian Symposium on Software Engineering10.1145/3131151.3131164(64-73)Online publication date: 20-Sep-2017
  • (2017)Identification and analysis of the elements required to manage technical debt by means of a systematic mapping studyJournal of Systems and Software10.1016/j.jss.2016.10.018124:C(22-38)Online publication date: 1-Feb-2017
  • (2015)Escalation in Information Technology ProjectsInternational Journal of Information Technology Project Management10.5555/2820217.28202186:4(1-19)Online publication date: 1-Oct-2015
  • (2015)Software Quality AssuranceundefinedOnline publication date: 2-Nov-2015
  • (2014)Formula translation in Blitz++, NumPy and modern FortranScientific Programming10.1155/2014/87014622:3(201-222)Online publication date: 1-Jul-2014
  • (2014)Robustness Indicators for Cloud-Based Systems TopologiesProceedings of the 2014 IEEE/ACM 7th International Conference on Utility and Cloud Computing10.1109/UCC.2014.40(307-316)Online publication date: 8-Dec-2014
  • Show More Cited By

View Options

View options

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media