technical debt

the implied cost of additional rework caused by picking a fast and easy solution now instead of a better and harder-to-implement but more suitable approach

DBpedia resource is: http://dbpedia.org/resource/Technical_debt

Abstract is: In software development, technical debt (also known as design debt or code debt) is the implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer. Analogous with monetary debt, if technical debt is not repaid, it can accumulate "interest", making it harder to implement changes. Unaddressed technical debt increases software entropy and cost of further rework. Similarly to monetary debt, technical debt is not necessarily a bad thing, and sometimes (e.g. as a proof-of-concept) is required to move projects forward. On the other hand, some experts claim that the "technical debt" metaphor tends to minimize the ramifications, which results in insufficient prioritization of the necessary work to correct it. As a change is started on a codebase, there is often the need to make other coordinated changes in other parts of the codebase or documentation. Changes required that are not completed are considered debt, and until paid, will incur interest on top of interest, making it cumbersome to build a project. Although the term is primarily used in software development, it can also be applied to other professions.

technical debt is …
instance of (P31):
computer software termQ66754793
termQ1969448

External links are
P646Freebase ID/m/02rwsg4
P6366Microsoft Academic ID159198006
P10283OpenAlex IDC159198006
P1482Stack Exchange taghttps://stackoverflow.com/tags/technical-debt

P1269facet oftechnology riskQ6108858

Reverse relations

main subject (P921)
Q11052818810 Years of Technical Debt Research and Practice: Past, Present, and Future
Q1105283564.6.3 Affordable Systems: Balancing the Capability, Schedule, Flexibility, and Technical Debt Tradespace
Q569439994th International workshop on managing technical debt (MTD 2013)
Q110528449A Balancing Act: What Software Practitioners Have to Say about Technical Debt
Q110528379A Clustering Approach Towards Cross-Project Technical Debt Forecasting
Q110528233A Flowchart for Rapid Technical Debt Management Decision Making
Q60536941A Fluctuation-Based Modelling Approach to Quantification of the Technical Debt on Mobile Cloud-Based Service Level
Q110528189A Gap in the Analysis of Technical Debt in Procedural Languages: An Experiential Report on Go
Q110528184A Plea to Tool Vendors: Do Not Mislead How Technical Debt Is Managed
Q110528218A Systematic Method to Evaluate the Software Engineering Practices for Minimizing Technical Debt
Q110528220A Taste of the Software Industry Perception of Technical Debt and its Management in Brazil
Q110528416A comparison of quality flaws and technical debt in model transformation specifications
Q110528439A computational model of a natural language processing system for architectural technical debt management
Q110528231A qualitative-systematic analysis of the relationship between technical debt accumulation and users’ satisfaction throughout enterprise software packages operation
Q110528390A semi-automated framework for the identification and estimation of Architectural Technical Debt: A comparative case-study on the modularization of a software component
Q110528412A survey of self-admitted technical debt
Q110528420A systematic literature review on Technical Debt prioritization: Strategies, processes, factors, and tools
Q110528403A systematic mapping study on technical debt and its management
Q110528392A tertiary study on technical debt: Types, management strategies, research trends, and base information for practitioners
Q110528264A threshold based approach to technical debt
Q110528381Adapting the concept of technical debt to software of automated Production Systems focusing on fault handling, mode of operation and safety aspects
Q110528178An Overview and Comparison of Technical Debt Measurement Tools
Q110528360An empirical assessment of technical debt practices in industry
Q110528423An empirical study on the co-occurrence between refactoring actions and Self-Admitted Technical Debt removal
Q110528402An exploration of technical debt
Q110528368An exploratory study on the introduction and removal of different types of technical debt in deep learning frameworks
Q110528388Analyzing the concept of technical debt in the context of agile software development: A systematic literature review
Q57390953Applicability of Technical Debt as a Concept to Understand Obstacles for Evolution of Automated Production Systems
Q110528358Architectural Technical Debt in Embedded Systems
Q110528397Architectural design decisions that incur technical debt — An industrial case study
Q59865821Assessing technical debt by identifying design flaws in software systems
Q110528194Automating Change-Level Self-Admitted Technical Debt Determination
Q110528445Better Now Than Later: Managing Technical Debt in Systems Development
Q110528421Building and evaluating a theory of architectural technical debt in software-intensive systems
Q110528415CODE reuse in practice: Benefiting or harming technical debt
Q110528196Can Clean New Code reduce Technical Debt Density
Q110528338Characterizing and Mitigating Self-Admitted Technical Debt in Build Systems
Q110528221Comparing Maintainability Index, SIG Method, and SQALE for Technical Debt Identification
Q110528372Comparing four approaches for technical debt identification
Q57795938Conciliating Model-Driven Engineering with Technical Debt Using a Quality Framework
Q110528436Controlling Technical Debt Remediation in Outsourced Enterprise Systems Maintenance: An Empirical Analysis
Q110528369Correction to: Wait for it: identifying “On-Hold” self-admitted technical debt
Q110528407Costs and obstacles encountered in technical debt management – A case study
Q110528383Cross-disciplinary and cross-life-cycle-phase Technical Debt in automated Production Systems: two industrial case studies and a survey
Q110528187Data-Driven Technical Debt Management: Software Engineering or Data Science Challenge?
Q110528432Dealing with technical debt
Q110528200Debt-Prone Bugs: Technical Debt in Software Maintenance
Q110528441Detecting and Classifying Self-Admitted of Technical Debt with CNN-BiLSTM
Q110528440Developing a theory based on the causes of technical debt injection into software projects in Colombia
Q110528450Distributed Agile, Agile Testing, and Technical Debt
Q110528399Does it matter who pays back Technical Debt? An empirical study of self-fixed TD
Q110528417Does migrating a monolithic system to microservices decrease the technical debt?
Q58487111Early evaluation of technical debt impact on maintainability
Q110528451Estimating the Principal of an Application's Technical Debt
Q57795918Evaluating Quality Issues in BPMN Models by Extending a Technical Debt Software Platform
Q57381080Evaluating Technical Debt in Cloud-Based Architectures Using Real Options
Q110528367Evaluating the agreement among technical debt measurement tools: building an empirical benchmark of technical debt liabilities
Q110528357Evaluation of System Integration and Qualification Strategies using the Technical Debt metaphor; a case study in Subsea System Development
Q110528361Evolution of technical debt remediation in Python: A case study on the Apache Software Ecosystem
Q110528226Examining Technical Debt Accumulation in Software Implementations
Q110528444Experience With Managing Technical Debt in Scientific Software Development Using the EXA2PRO Framework
Q110528446Exploratory Testing as a Source of Technical Debt
Q110528396Exploring the Relation between Technical Debt Principal and Interest: An Empirical Approach
Q110528363Exploring the costs of technical debt management – a case study
Q110528362Further investigation of the survivability of code technical debt items
Q110528181Garbage Collect Your Technical Debt
Q110528175GitHub, Technical Debt, Code Formatting, and More
Q77623696Hidden Technical Debt in Machine Learning Systems
Q110528438How do software architects perceive technical debt in Colombian industry? An analysis of technical debt causes
Q110528404How do software development teams manage technical debt? – An empirical study
Q110528408Identification and analysis of the elements required to manage technical debt by means of a systematic mapping study
Q110528387Identification and management of technical debt: A systematic mapping study
Q110528443Identification of Self-Admitted Technical Debt Using Enhanced Feature Selection Based on Word Embedding
Q110528422Identifying architectural technical debt, principal, and interest in microservices: A multiple-case study
Q110528364Identifying self-admitted technical debt in open source projects using text mining
Q110528393Identifying self-admitted technical debt through code comment analysis with a contextualized vocabulary
Q56944063In Search of a Metric for Managing Architectural Technical Debt
Q110528193Integrating Technical Debt Management and Software Quality Management Processes: A Normative Framework and Field Tests
Q110528419Interdisciplinary effects of technical debt in companies with mechatronic products — a qualitative study
Q110528406Introduction to the special issue on technical debt in software systems
Q110528219Investigate, Identify and Estimate the Technical Debt: A Systematic Mapping Study
Q110528240Investigate, Identify and Estimate the Technical Debt: A Systematic Mapping Study
Q110528386Investigating Architectural Technical Debt accumulation and refactoring over time: A multiple-case study
Q110528186Living With Technical Debt—A Perspective From the Video Game Industry
Q110528339Machine Learning for Technical Debt Identification
Q110528265Managing Technical Debt
Q110528182Managing Technical Debt Under Uncertainty
Q110528195Managing Technical Debt in Database Normalization
Q110528191Managing Technical Debt in Enterprise Software Packages
Q110528448Managing Technical Debt with the SQALE Method
Q110528173Managing Technical Debt: Insights from Recent Empirical Evidence
Q110528411Managing architectural technical debt: A unified model and systematic literature review
Q57407532Managing technical debt
Q110528263Managing technical debt in software development
Q56944197Managing technical debt in software-reliant systems
Q110528370Measuring affective states from technical debt
Q110528190Multiclass Classification for Self-Admitted Technical Debt Based on XGBoost
Q110528276Neural Network-based Detection of Self-Admitted Technical Debt
Q110528232OVERVIEW OF THE AUTOMATED MEASUREMENT OF TECHNICAL DEBT
Q110528180On the Relationship Between Technical Debt Management and Process Models
Q110528250On the Relationship between Self-Admitted Technical Debt Removals and Technical Debt Measures
Q110528395On the diffuseness of technical debt items and accuracy of remediation time when using SonarQube
Q110528359On the interest of architectural technical debt: Uncovering the contagious debt phenomenon
Q110528410On the value of a prioritization scheme for resolving Self-admitted technical debt
Q110528183Pitfalls and Solutions for Technical Debt Management in Agile Software Projects
Q110528373Predicting technical debt from commit contents: reproduction and extension with automated feature selection
Q110528424Prevalence, common causes and effects of technical debt: Results from a family of surveys with the IT industry
Q110528260Refactoring Cost Estimation for Architectural Technical Debt
Q110528431SATDBailiff-mining and tracking self-admitted technical debt
Q56944131Second international workshop on managing technical debt
Q109297285Seeking Technical Debt in Critical Software Development Projects: An Exploratory Field Study
Q110528371Self-admitted technical debt practices: a comparison between industry and open-source
Q110528413Software developer productivity loss due to technical debt—A replication and extension study examining developers’ development work
Q56944080Strategic Management of Technical Debt: Tutorial Synopsis
Q59104411Supporting Technical Debt Cataloging with TD-Tracker Tool
Q110528234TECHNICAL DEBT EM PROJETOS DE GOVERNO ELETRÔNICO NO ESTADO DO RIO GRANDE DO SUL
Q110528246TETRA™ Techniques to Assess and Manage the Software Technical Debt
Q110528201Tackling Technical Debt: Managing Advances in DNA Technology that Outpace the Evolution of Law
Q110528174Technical Debt
Q110528269Technical Debt
Q110528271Technical Debt
Q110528272Technical Debt
Q110528197Technical Debt Aware Estimations in Software Engineering: A Systematic Mapping Study
Q110528225Technical Debt and Firm Performance
Q110528224Technical Debt and the Reliability of Enterprise Software Systems: A Competing Risks Analysis
Q110528238Technical Debt and the Reliability of Enterprise Software Systems: A Competing Risks Analysis
Q110528433Technical Debt as an Indicator of Library Metadata Quality
Q110528434Technical Debt as an Indicator of Library Metadata Quality
Q110528375Technical Debt as indicator for weaknesses in engineering of automated production systems
Q110528273Technical Debt in Agile Development
Q58008782Technical Debt in Computational Science
Q110528382Technical Debt indication in PLC Code for automated Production Systems: Introducing a Domain Specific Static Code Analysis Tool
Q110528430Technical Debt tracking: Current state of practice
Q110528176Technical Debt: Challenges and Perspectives
Q56944087Technical Debt: From Metaphor to Theory and Practice
Q56944033Technical Debt: Past, present, and future (Panel)
Q110528172Technical Debt: Where Are the Shareholders' Interests?
Q110528185Technical and Nontechnical Prioritization Schema for Technical Debt: Voice of TD-Experienced Practitioners
Q110528267Technical debt
Q110528391Technical debt and agile software development practices and processes: An industry practitioner survey
Q110528405Technical debt and system architecture: The impact of coupling on defect-related activity
Q110528437Technical debt as an indicator of software security risk: a machine learning approach for software development enterprises
Q110528268Technical debt at the crossroads of research and practice
Q110528418Technical debt forecasting: An empirical study on open-source repositories
Q57391023Technical debt in Automated Production Systems
Q110528380Technical debt in procedural model transformation languages
Q110528266Technical debt in software development
Q110528398Technical debt payment and prevention through the lenses of software architects
Q110528228Technical debt reduction using epsilon-Nash equilibrium for the perturbed software refactor game model
Q110528229Technical debt reduction using epsilon-Nash equilibrium for the perturbed software refactor game model
Q57991586Technical debt reduction using search based automated refactoring
Q57727312The Perception of Technical Debt in the Embedded Systems Domain: An Industrial Case Study
Q110528378The Risk of Generating Technical Debt Interest: A Case Study
Q110528259The Technical Debt Density Over Multiple Releases and the Refactoring Story
Q123074959The WyCash portfolio management system
Q110528384The financial aspect of managing technical debt: A systematic literature review
Q110528414The influence of Technical Debt on software developer morale
Q110528365The practitioners’ point of view on the concept of technical debt and its causes and consequences: a design for a global family of industrial surveys and its first results from Brazil
Q110528389The relation between technical debt and corrective maintenance in PHP web applications
Q110528374The temporality of technical debt introduction on new code and confounding factors
Q110528400The use of incentives to promote technical debt management
Q110528447To Pay or Not to Pay Technical Debt
Q110528179Toward a Technical Debt Conceptualization for Serverless Computing
Q110528277Towards Effective Technical Debt Decision Making in Software Startups
Q110528425Towards a taxonomy of technical debt for COTS-intensive cyber physical systems
Q110528223Understanding automated and human-based technical debt identification approaches-a two-phase study
Q110528377Understanding factors affecting technical debt
Q110528177Ur-Technical Debt
Q110528376Using BiLSTM with attention mechanism to automatically detect self-admitted technical debt
Q110528245Using Naming Patterns for Identifying Architectural Technical Debt
Q110528192Using Natural Language Processing to Automatically Detect Self-Admitted Technical Debt
Q110528222VisminerTD: a tool for automatic identification and interactive monitoring of the evolution of technical debt items
Q110528366Wait for it: identifying “On-Hold” self-admitted technical debt
Q110528230Wpływ świadomości dotyczącej długu technicznego i wiedzy o nim na powodzenie projektów informatycznych / Impact of knowledge and awareness of technical debt in software developing teams on IT projects success

Q5189918crufthas effectP1542
Q445962legacy systemhas characteristicP1552

The articles in Wikimedia projects and languages

Arabic (ar / Q13955)دين تقنيwikipedia
Catalan (ca / Q7026)Deute tècnicwikipedia
      Technische Schuldenwikipedia
      Technical debtwikipedia
      Deuda técnicawikipedia
Persian (fa / Q9168)بدهی فنیwikipedia
      Tekninen velkawikipedia
      Dette techniquewikipedia
      חוב טכניwikipedia
hiतकनीकी ऋणwikipedia
      Debito tecnicowikipedia
      技術的負債wikipedia
      기술 부채wikipedia
nbTeknisk gjeldwikipedia
      Dívida tecnológicawikipedia
      Технический долгwikipedia
      Технічний боргwikipedia
      技术负债wikipedia

Search more.