Context Technical debt (TD) is a metaphor reflecting technical compromises that can yield
short-term benefit but may hurt the long-term health of a software system. Objective This …

Abstract Large Software Companies need to support the continuous and fast delivery of
customer value in both the short and long term. However, this can be impeded if the …

Abstract Context: Requirements Technical Debt are related to the distance between the
ideal value of the specification and the actual implementation of the system, which are …

Technical debt is a metaphor indicating sub-optimal solutions implemented for short-term
benefits by sacrificing the long-term maintainability and evolvability of software. A special …

As the pace of software delivery increases and technology rapidly changes, organizations
seek guidance on how to insure the sustainability of their software development effort. Over …

Technical debt management entails the quantification of principal and interest. In our
previous work we had introduced a framework for calculating the Technical Debt Breaking …

Fast software deliveries are hindered by high maintenance efforts due to internal quality
issues and Technical Debt (TD) and specifically, Architectural Technical Debt (ATD) has …

Context: During software development, some architectural design decisions incur technical
debt, either deliberately or inadvertently. These have serious impact on the quality of a …

Abstract Requirements Technical Debt (RTD) applies the Technical Debt (TD) metaphor to
capture the consequences of sub-optimal decisions made concerning Requirements …

When not appropriately managed, technical debt is considered to have negative effects to
the long term success of software projects. However, how the debt metaphor applies to …