Software security is a complex topic, and for development projects it can be challenging to
assess what security is necessary and cost-effective. Agile Software Development (ASD) …

Context: Knowing the effects of technical debt (TD) can support software development teams
in the prioritization of TD items to pay off. However, little is known about the relations …

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 …

Context: Architectural decisions are considered one of the most common sources of
technical debt (TD). Thus, it is necessary to understand how TD is perceived by software …

Abstract Context: Technical Debt (TD) is a metaphor for technical problems that are not
visible to users and customers but hinder developers in their work, making future changes …

Context. Technical debt (TD) prevention allows software practitioners to apply practices to
avoid potential TD items in their projects. Aims. To uncover and prioritize, from the point of …

Context: Technical debt (TD) payment refers to the activity of expending maintenance effort
and resources to make up for the effects of previous technical compromises. Aims: To …

Context: Technical debt (TD) can bring short-term benefits to software projects, but its
presence is also associated with issues such as decreasing product quality. Recent …

Context: Developers often introduce the self-admitted technical debt (SATD), ie, a
compromised solution to satisfy the delivery of the current goals, in code comments but do …