Nothing Special   »   [go: up one dir, main page]

skip to main content
research-article

A threshold based approach to technical debt

Published: 03 April 2012 Publication History

Abstract

Nearly two decades ago, Ward Cunningham introduced us to the term "technical debt" as a means of describing the long term costs associated with a suboptimal software design and implementation. For most programs, especially those with a large legacy code baseline, achieving zero absolute debt is an unnecessary and unrealistic goal. It is important to recall that a primary reason for managing and eliminating debt is to drive down maintenance costs and to reduce defects. A sufficiently low, manageable level of debt can minimize the long-term impact, i.e., "low debt interest payments". In this article, we define an approach for establishing program specific thresholds to define manageable levels of technical debt.

References

[1]
Cunningham, W. 1992. The WyCash Portfolio Management System. OOPSLA '92 Experience Report.
[2]
Gat, I. 2010. Revolution in Software: Using Technical Debt Techniques to Govern the Software Development Process. Executive Report. Cutter Consortium.
[3]
Sonar, 2011. http://www.sonarsource.org/
[4]
CWE/SANS Top 25 Most Dangerous Software Errors, The MITRE Corporation, 2011. http://cwe.mitre.org/top25/
[5]
Highsmith, J. 2009. Agile Project Management 2nd ed. Addison Wesley.

Cited By

View all
  • (2024)A Systematic Mapping Study Exploring Quantification Approaches to Code, Design, and Architecture Technical DebtACM Transactions on Software Engineering and Methodology10.1145/367539333:7(1-44)Online publication date: 2-Jul-2024
  • (2024)Technical Debt Monitoring Decision Making with Skin in the GameACM Transactions on Software Engineering and Methodology10.1145/366480533:7(1-27)Online publication date: 26-Aug-2024
  • (2024)Local and Global Explainability for Technical Debt IdentificationIEEE Transactions on Software Engineering10.1109/TSE.2024.342242750:8(2110-2123)Online publication date: 1-Aug-2024
  • Show More Cited By

Index Terms

  1. A threshold based approach to technical debt

    Recommendations

    Comments

    Please enable JavaScript to view thecomments powered by Disqus.

    Information & Contributors

    Information

    Published In

    cover image ACM SIGSOFT Software Engineering Notes
    ACM SIGSOFT Software Engineering Notes  Volume 37, Issue 2
    March 2012
    92 pages
    ISSN:0163-5948
    DOI:10.1145/2108144
    Issue’s Table of Contents
    Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third-party components of this work must be honored. For all other uses, contact the Owner/Author.

    Publisher

    Association for Computing Machinery

    New York, NY, United States

    Publication History

    Published: 03 April 2012
    Published in SIGSOFT Volume 37, Issue 2

    Check for updates

    Author Tags

    1. cost estimation
    2. risk management
    3. software quality
    4. technical debt

    Qualifiers

    • Research-article

    Contributors

    Other Metrics

    Bibliometrics & Citations

    Bibliometrics

    Article Metrics

    • Downloads (Last 12 months)13
    • Downloads (Last 6 weeks)4
    Reflects downloads up to 16 Feb 2025

    Other Metrics

    Citations

    Cited By

    View all
    • (2024)A Systematic Mapping Study Exploring Quantification Approaches to Code, Design, and Architecture Technical DebtACM Transactions on Software Engineering and Methodology10.1145/367539333:7(1-44)Online publication date: 2-Jul-2024
    • (2024)Technical Debt Monitoring Decision Making with Skin in the GameACM Transactions on Software Engineering and Methodology10.1145/366480533:7(1-27)Online publication date: 26-Aug-2024
    • (2024)Local and Global Explainability for Technical Debt IdentificationIEEE Transactions on Software Engineering10.1109/TSE.2024.342242750:8(2110-2123)Online publication date: 1-Aug-2024
    • (2023)A metrics-based approach for selecting among various refactoring candidatesEmpirical Software Engineering10.1007/s10664-023-10412-w29:1Online publication date: 16-Dec-2023
    • (2022) SDK4ED : A platform for technical debt management Software: Practice and Experience10.1002/spe.309352:8(1879-1902)Online publication date: 4-May-2022
    • (2021)Experience With Managing Technical Debt in Scientific Software Development Using the EXA2PRO FrameworkIEEE Access10.1109/ACCESS.2021.30792719(72524-72534)Online publication date: 2021
    • (2020)Towards better technical debt detection with NLP and machine learning methodsProceedings of the ACM/IEEE 42nd International Conference on Software Engineering: Companion Proceedings10.1145/3377812.3381404(242-245)Online publication date: 27-Jun-2020
    • (2020)Continuous practices and technical debt: a systematic literature review2020 20th International Conference on Computational Science and Its Applications (ICCSA)10.1109/ICCSA50381.2020.00018(40-44)Online publication date: Jul-2020
    • (2020)Exploring the Relation between Technical Debt Principal and Interest: An Empirical ApproachInformation and Software Technology10.1016/j.infsof.2020.106391128(106391)Online publication date: Dec-2020
    • (2019)Releasing fast and slow: an exploratory case study at INGProceedings of the 2019 27th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering10.1145/3338906.3338978(785-795)Online publication date: 12-Aug-2019
    • Show More Cited By

    View Options

    Login options

    View options

    PDF

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader

    Figures

    Tables

    Media

    Share

    Share

    Share this Publication link

    Share on social media