Technical Debt is a metaphor used to express sub-optimal source code implementations
that are introduced for short-term benefits that often need to be paid back later, at an …

To effectively manage Technical Debt (TD), we need reliable means to quantify it. We
conducted a Systematic Mapping Study (SMS) where we identified 39 quantification …

Technical debt denotes shortcuts taken during software development, mostly for the sake of
expedience. When such shortcuts are admitted explicitly by developers (eg, writing a …

Self-Admitted Technical Debt (SATD) is a sub-type of technical debt. It is introduced to
represent such technical debts that are intentionally introduced by developers in the process …

Abstract Self-Admitted Technical Debt (SATD) is primarily studied in Object-Oriented (OO)
languages and traditionally commercial software. However, scientific software coded in …

Self-admitted technical debt (SATD) refers to a specific type of technical debt that is
introduced intentionally in the software development and maintenance processes. SATD …

Self-admitted technical debt refers to situations where a software developer knows that their
current implementation is not optimal and indicates this using a source code comment. In …

Programmers tend to leave incomplete, temporary workarounds and buggy codes that
require rework in software development and such pitfall is referred to as Self-admitted …

Technical Debt (TD) is a metaphor that describes the cost–benefit relationship between
postponing technical development activities and the consequences of this long-term …

For blockchain software systems, framework developers may introduce technical debts that
application developers are not aware of. Because these technical debts can have a negative …