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 …

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 …

Abstract Context: Technical Debt (TD) is a term for software solutions that are beneficial in
the short-term but impede future change. Goal: Previous research on TD indicates various …

Context Software startups are immature software organizations that focus on the
development of a single software product or service. This organizational context …

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 …

To meet project timelines or budget constraints, developers intentionally deviate from writing
optimal code to feasible code in what is known as incurring Technical Debt (TD) …

Technical debt (TD) entails the shortcuts and unsuitable choices made during the
development or maintenance of an IT system, which can result in negative consequences …

Abstract Model‐Based Systems Engineering (MBSE) is the growing practice of systems
engineering (SE) in which descriptive models replace documents as the embodiment of SE …

Technical debt (TD) poses a significant risk in the software industry, representing the
compromises made during software development that result in long-term consequences. To …

Context: Test-related technical debt (TRTD) refers to debt items that affect software testing
activities, compromising their quality. Having information on indicators of their presence …