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.
computer software term | Q66754793 |
term | Q1969448 |
P646 | Freebase ID | /m/02rwsg4 |
P6366 | Microsoft Academic ID | 159198006 |
P10283 | OpenAlex ID | C159198006 |
P1482 | Stack Exchange tag | https://stackoverflow.com/tags/technical-debt |
P1269 | facet of | technology risk | Q6108858 |
Q110528188 | 10 Years of Technical Debt Research and Practice: Past, Present, and Future |
Q110528356 | 4.6.3 Affordable Systems: Balancing the Capability, Schedule, Flexibility, and Technical Debt Tradespace |
Q56943999 | 4th International workshop on managing technical debt (MTD 2013) |
Q110528449 | A Balancing Act: What Software Practitioners Have to Say about Technical Debt |
Q110528379 | A Clustering Approach Towards Cross-Project Technical Debt Forecasting |
Q110528233 | A Flowchart for Rapid Technical Debt Management Decision Making |
Q60536941 | A Fluctuation-Based Modelling Approach to Quantification of the Technical Debt on Mobile Cloud-Based Service Level |
Q110528189 | A Gap in the Analysis of Technical Debt in Procedural Languages: An Experiential Report on Go |
Q110528184 | A Plea to Tool Vendors: Do Not Mislead How Technical Debt Is Managed |
Q110528218 | A Systematic Method to Evaluate the Software Engineering Practices for Minimizing Technical Debt |
Q110528220 | A Taste of the Software Industry Perception of Technical Debt and its Management in Brazil |
Q110528416 | A comparison of quality flaws and technical debt in model transformation specifications |
Q110528439 | A computational model of a natural language processing system for architectural technical debt management |
Q110528231 | A qualitative-systematic analysis of the relationship between technical debt accumulation and users’ satisfaction throughout enterprise software packages operation |
Q110528390 | A semi-automated framework for the identification and estimation of Architectural Technical Debt: A comparative case-study on the modularization of a software component |
Q110528412 | A survey of self-admitted technical debt |
Q110528420 | A systematic literature review on Technical Debt prioritization: Strategies, processes, factors, and tools |
Q110528403 | A systematic mapping study on technical debt and its management |
Q110528392 | A tertiary study on technical debt: Types, management strategies, research trends, and base information for practitioners |
Q110528264 | A threshold based approach to technical debt |
Q110528381 | Adapting the concept of technical debt to software of automated Production Systems focusing on fault handling, mode of operation and safety aspects |
Q110528178 | An Overview and Comparison of Technical Debt Measurement Tools |
Q110528360 | An empirical assessment of technical debt practices in industry |
Q110528423 | An empirical study on the co-occurrence between refactoring actions and Self-Admitted Technical Debt removal |
Q110528402 | An exploration of technical debt |
Q110528368 | An exploratory study on the introduction and removal of different types of technical debt in deep learning frameworks |
Q110528388 | Analyzing the concept of technical debt in the context of agile software development: A systematic literature review |
Q57390953 | Applicability of Technical Debt as a Concept to Understand Obstacles for Evolution of Automated Production Systems |
Q110528358 | Architectural Technical Debt in Embedded Systems |
Q110528397 | Architectural design decisions that incur technical debt — An industrial case study |
Q59865821 | Assessing technical debt by identifying design flaws in software systems |
Q110528194 | Automating Change-Level Self-Admitted Technical Debt Determination |
Q110528445 | Better Now Than Later: Managing Technical Debt in Systems Development |
Q110528421 | Building and evaluating a theory of architectural technical debt in software-intensive systems |
Q110528415 | CODE reuse in practice: Benefiting or harming technical debt |
Q110528196 | Can Clean New Code reduce Technical Debt Density |
Q110528338 | Characterizing and Mitigating Self-Admitted Technical Debt in Build Systems |
Q110528221 | Comparing Maintainability Index, SIG Method, and SQALE for Technical Debt Identification |
Q110528372 | Comparing four approaches for technical debt identification |
Q57795938 | Conciliating Model-Driven Engineering with Technical Debt Using a Quality Framework |
Q110528436 | Controlling Technical Debt Remediation in Outsourced Enterprise Systems Maintenance: An Empirical Analysis |
Q110528369 | Correction to: Wait for it: identifying “On-Hold” self-admitted technical debt |
Q110528407 | Costs and obstacles encountered in technical debt management – A case study |
Q110528383 | Cross-disciplinary and cross-life-cycle-phase Technical Debt in automated Production Systems: two industrial case studies and a survey |
Q110528187 | Data-Driven Technical Debt Management: Software Engineering or Data Science Challenge? |
Q110528432 | Dealing with technical debt |
Q110528200 | Debt-Prone Bugs: Technical Debt in Software Maintenance |
Q110528441 | Detecting and Classifying Self-Admitted of Technical Debt with CNN-BiLSTM |
Q110528440 | Developing a theory based on the causes of technical debt injection into software projects in Colombia |
Q110528450 | Distributed Agile, Agile Testing, and Technical Debt |
Q110528399 | Does it matter who pays back Technical Debt? An empirical study of self-fixed TD |
Q110528417 | Does migrating a monolithic system to microservices decrease the technical debt? |
Q58487111 | Early evaluation of technical debt impact on maintainability |
Q110528451 | Estimating the Principal of an Application's Technical Debt |
Q57795918 | Evaluating Quality Issues in BPMN Models by Extending a Technical Debt Software Platform |
Q57381080 | Evaluating Technical Debt in Cloud-Based Architectures Using Real Options |
Q110528367 | Evaluating the agreement among technical debt measurement tools: building an empirical benchmark of technical debt liabilities |
Q110528357 | Evaluation of System Integration and Qualification Strategies using the Technical Debt metaphor; a case study in Subsea System Development |
Q110528361 | Evolution of technical debt remediation in Python: A case study on the Apache Software Ecosystem |
Q110528226 | Examining Technical Debt Accumulation in Software Implementations |
Q110528444 | Experience With Managing Technical Debt in Scientific Software Development Using the EXA2PRO Framework |
Q110528446 | Exploratory Testing as a Source of Technical Debt |
Q110528396 | Exploring the Relation between Technical Debt Principal and Interest: An Empirical Approach |
Q110528363 | Exploring the costs of technical debt management – a case study |
Q110528362 | Further investigation of the survivability of code technical debt items |
Q110528181 | Garbage Collect Your Technical Debt |
Q110528175 | GitHub, Technical Debt, Code Formatting, and More |
Q77623696 | Hidden Technical Debt in Machine Learning Systems |
Q110528438 | How do software architects perceive technical debt in Colombian industry? An analysis of technical debt causes |
Q110528404 | How do software development teams manage technical debt? – An empirical study |
Q110528408 | Identification and analysis of the elements required to manage technical debt by means of a systematic mapping study |
Q110528387 | Identification and management of technical debt: A systematic mapping study |
Q110528443 | Identification of Self-Admitted Technical Debt Using Enhanced Feature Selection Based on Word Embedding |
Q110528422 | Identifying architectural technical debt, principal, and interest in microservices: A multiple-case study |
Q110528364 | Identifying self-admitted technical debt in open source projects using text mining |
Q110528393 | Identifying self-admitted technical debt through code comment analysis with a contextualized vocabulary |
Q56944063 | In Search of a Metric for Managing Architectural Technical Debt |
Q110528193 | Integrating Technical Debt Management and Software Quality Management Processes: A Normative Framework and Field Tests |
Q110528419 | Interdisciplinary effects of technical debt in companies with mechatronic products — a qualitative study |
Q110528406 | Introduction to the special issue on technical debt in software systems |
Q110528219 | Investigate, Identify and Estimate the Technical Debt: A Systematic Mapping Study |
Q110528240 | Investigate, Identify and Estimate the Technical Debt: A Systematic Mapping Study |
Q110528386 | Investigating Architectural Technical Debt accumulation and refactoring over time: A multiple-case study |
Q110528186 | Living With Technical Debt—A Perspective From the Video Game Industry |
Q110528339 | Machine Learning for Technical Debt Identification |
Q110528265 | Managing Technical Debt |
Q110528182 | Managing Technical Debt Under Uncertainty |
Q110528195 | Managing Technical Debt in Database Normalization |
Q110528191 | Managing Technical Debt in Enterprise Software Packages |
Q110528448 | Managing Technical Debt with the SQALE Method |
Q110528173 | Managing Technical Debt: Insights from Recent Empirical Evidence |
Q110528411 | Managing architectural technical debt: A unified model and systematic literature review |
Q57407532 | Managing technical debt |
Q110528263 | Managing technical debt in software development |
Q56944197 | Managing technical debt in software-reliant systems |
Q110528370 | Measuring affective states from technical debt |
Q110528190 | Multiclass Classification for Self-Admitted Technical Debt Based on XGBoost |
Q110528276 | Neural Network-based Detection of Self-Admitted Technical Debt |
Q110528232 | OVERVIEW OF THE AUTOMATED MEASUREMENT OF TECHNICAL DEBT |
Q110528180 | On the Relationship Between Technical Debt Management and Process Models |
Q110528250 | On the Relationship between Self-Admitted Technical Debt Removals and Technical Debt Measures |
Q110528395 | On the diffuseness of technical debt items and accuracy of remediation time when using SonarQube |
Q110528359 | On the interest of architectural technical debt: Uncovering the contagious debt phenomenon |
Q110528410 | On the value of a prioritization scheme for resolving Self-admitted technical debt |
Q110528183 | Pitfalls and Solutions for Technical Debt Management in Agile Software Projects |
Q110528373 | Predicting technical debt from commit contents: reproduction and extension with automated feature selection |
Q110528424 | Prevalence, common causes and effects of technical debt: Results from a family of surveys with the IT industry |
Q110528260 | Refactoring Cost Estimation for Architectural Technical Debt |
Q110528431 | SATDBailiff-mining and tracking self-admitted technical debt |
Q56944131 | Second international workshop on managing technical debt |
Q109297285 | Seeking Technical Debt in Critical Software Development Projects: An Exploratory Field Study |
Q110528371 | Self-admitted technical debt practices: a comparison between industry and open-source |
Q110528413 | Software developer productivity loss due to technical debt—A replication and extension study examining developers’ development work |
Q56944080 | Strategic Management of Technical Debt: Tutorial Synopsis |
Q59104411 | Supporting Technical Debt Cataloging with TD-Tracker Tool |
Q110528234 | TECHNICAL DEBT EM PROJETOS DE GOVERNO ELETRÔNICO NO ESTADO DO RIO GRANDE DO SUL |
Q110528246 | TETRA™ Techniques to Assess and Manage the Software Technical Debt |
Q110528201 | Tackling Technical Debt: Managing Advances in DNA Technology that Outpace the Evolution of Law |
Q110528174 | Technical Debt |
Q110528269 | Technical Debt |
Q110528271 | Technical Debt |
Q110528272 | Technical Debt |
Q110528197 | Technical Debt Aware Estimations in Software Engineering: A Systematic Mapping Study |
Q110528225 | Technical Debt and Firm Performance |
Q110528224 | Technical Debt and the Reliability of Enterprise Software Systems: A Competing Risks Analysis |
Q110528238 | Technical Debt and the Reliability of Enterprise Software Systems: A Competing Risks Analysis |
Q110528433 | Technical Debt as an Indicator of Library Metadata Quality |
Q110528434 | Technical Debt as an Indicator of Library Metadata Quality |
Q110528375 | Technical Debt as indicator for weaknesses in engineering of automated production systems |
Q110528273 | Technical Debt in Agile Development |
Q58008782 | Technical Debt in Computational Science |
Q110528382 | Technical Debt indication in PLC Code for automated Production Systems: Introducing a Domain Specific Static Code Analysis Tool |
Q110528430 | Technical Debt tracking: Current state of practice |
Q110528176 | Technical Debt: Challenges and Perspectives |
Q56944087 | Technical Debt: From Metaphor to Theory and Practice |
Q56944033 | Technical Debt: Past, present, and future (Panel) |
Q110528172 | Technical Debt: Where Are the Shareholders' Interests? |
Q110528185 | Technical and Nontechnical Prioritization Schema for Technical Debt: Voice of TD-Experienced Practitioners |
Q110528267 | Technical debt |
Q110528391 | Technical debt and agile software development practices and processes: An industry practitioner survey |
Q110528405 | Technical debt and system architecture: The impact of coupling on defect-related activity |
Q110528437 | Technical debt as an indicator of software security risk: a machine learning approach for software development enterprises |
Q110528268 | Technical debt at the crossroads of research and practice |
Q110528418 | Technical debt forecasting: An empirical study on open-source repositories |
Q57391023 | Technical debt in Automated Production Systems |
Q110528380 | Technical debt in procedural model transformation languages |
Q110528266 | Technical debt in software development |
Q110528398 | Technical debt payment and prevention through the lenses of software architects |
Q110528228 | Technical debt reduction using epsilon-Nash equilibrium for the perturbed software refactor game model |
Q110528229 | Technical debt reduction using epsilon-Nash equilibrium for the perturbed software refactor game model |
Q57991586 | Technical debt reduction using search based automated refactoring |
Q57727312 | The Perception of Technical Debt in the Embedded Systems Domain: An Industrial Case Study |
Q110528378 | The Risk of Generating Technical Debt Interest: A Case Study |
Q110528259 | The Technical Debt Density Over Multiple Releases and the Refactoring Story |
Q123074959 | The WyCash portfolio management system |
Q110528384 | The financial aspect of managing technical debt: A systematic literature review |
Q110528414 | The influence of Technical Debt on software developer morale |
Q110528365 | The 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 |
Q110528389 | The relation between technical debt and corrective maintenance in PHP web applications |
Q110528374 | The temporality of technical debt introduction on new code and confounding factors |
Q110528400 | The use of incentives to promote technical debt management |
Q110528447 | To Pay or Not to Pay Technical Debt |
Q110528179 | Toward a Technical Debt Conceptualization for Serverless Computing |
Q110528277 | Towards Effective Technical Debt Decision Making in Software Startups |
Q110528425 | Towards a taxonomy of technical debt for COTS-intensive cyber physical systems |
Q110528223 | Understanding automated and human-based technical debt identification approaches-a two-phase study |
Q110528377 | Understanding factors affecting technical debt |
Q110528177 | Ur-Technical Debt |
Q110528376 | Using BiLSTM with attention mechanism to automatically detect self-admitted technical debt |
Q110528245 | Using Naming Patterns for Identifying Architectural Technical Debt |
Q110528192 | Using Natural Language Processing to Automatically Detect Self-Admitted Technical Debt |
Q110528222 | VisminerTD: a tool for automatic identification and interactive monitoring of the evolution of technical debt items |
Q110528366 | Wait for it: identifying “On-Hold” self-admitted technical debt |
Q110528230 | Wpł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 |
Q5189918 | cruft | has effect | P1542 |
Q445962 | legacy system | has characteristic | P1552 |
Arabic (ar / Q13955) | دين تقني | wikipedia |
Catalan (ca / Q7026) | Deute tècnic | wikipedia |
Technische Schulden | wikipedia | |
Technical debt | wikipedia | |
Deuda técnica | wikipedia | |
Persian (fa / Q9168) | بدهی فنی | wikipedia |
Tekninen velka | wikipedia | |
Dette technique | wikipedia | |
חוב טכני | wikipedia | |
hi | तकनीकी ऋण | wikipedia |
Debito tecnico | wikipedia | |
技術的負債 | wikipedia | |
기술 부채 | wikipedia | |
nb | Teknisk gjeld | wikipedia |
Dívida tecnológica | wikipedia | |
Технический долг | wikipedia | |
Технічний борг | wikipedia | |
技术负债 | wikipedia |
Search more.