Exploring the Relation between Technical Debt Principal and Interest: An Empirical Approach

Ampatzoglou, Apostolos; Mittas, Nikolaos; Tsintzira, Angeliki Agathi; Arvanitou, Elvira Maria; Chatzigeorgiou, Alexander; Avgeriou, Paris; Angelis, Lefteris

doi:10.1016/j.infsof.2020.106391

Cited by 15 publications

(8 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A consistent measurement enables comparison of the impact of multiple TD items. TD has been measured as the financial cost [37], the amount of time required to do the work [54], and the work required to be performed [46]. Each of these terms have varying degrees of usability in systems engineering, and roughly align to the three system dimensions of budget (financial cost), schedule (time required), and performance (work required).…”

Section: E Technical Debt Measurement Unitsmentioning

confidence: 99%

See 1 more Smart Citation

Ontology for Technical Debt in Systems Engineering

Kleinwaks,

Batchelor,

Bradley

2023

IEEE Open J. Syst. Eng.

View full text Add to dashboard Cite

The technical debt metaphor is used to describe the long-term consequences of engineering decisions made to achieve a short-term benefit. The metaphor originated in the field of software engineering and has begun to migrate to other fields, including systems engineering. The usage of the metaphor, its associated terminology, and basic definitions vary both within the software field and within the greater engineering community. The lack of consistent definitions inhibits the ability of system developers to understand and control technical debt within their system developments. This paper presents an ontology for technical debt, focusing on the field of systems engineering. By providing a set of concise and consolidated definitions, this ontology enables precise discussion of technical debt and associated techniques for mitigating its impact within systems engineering.

show abstract

Section: E Technical Debt Measurement Unitsmentioning

confidence: 99%

“…The existing definitions of the principal vary, but are typically centered on the effort required to correct the issue causing the TD [5], [54], [56], [57]. Ampatzoglou et al define it as "the effort that is required to address the difference between the current and the optimal level of design-time quality" [40].…”

Section: ) Principalmentioning

confidence: 99%

Ontology for Technical Debt in Systems Engineering

Kleinwaks,

Batchelor,

Bradley

2023

IEEE Open J. Syst. Eng.

View full text Add to dashboard Cite

show abstract

“…In order to calculate the principal of the PD, we remind that ‘ In most approaches, principal is subsequently quantified by summing up the estimated effort to fix each individual inefficiency’ . [55].…”

Section: Privacy Security and Privacy Debtmentioning

confidence: 99%

Towards a privacy debt

2021

View full text Add to dashboard Cite

This study argues the difference between security and privacy and outlines the concept of Privacy Debt as a new Technical Debt. Privacy is gaining momentum in any software system due to mandatory compliance with respect to laws and regulations. There are several types of technical debts within the umbrella of software engineering, and most of them arise during different phases of software development. Several research studies have been focussed on highlighting different types of technical debts. However, authors introduce Privacy Debt as a particular technical debt focussed on privacy management and linked to a perturbative method. Privacy must be considered not only as technical debt requirements but also at design and deployment phases, among others. In addition, this method is illustrated with a use case.

show abstract

“…For example, the current studies on principle and interest of technical debt such as [1,2] assume that some architectural technical debt has already be identified, and demand architects to provide an estimation of interest if the payment of debt is postponed. However, as we have discussed earlier, the identification of technical debt itself requires enough competence and tools whose absence is presented as people debt and infrastructure debt.…”

Section: Open Challengesmentioning

confidence: 99%

The Need for Holistic Technical Debt Management across the Value Stream: Lessons Learnt and Open Challenges

Malakuti¹,

Heuschkel²

2021

Preprint

View full text Add to dashboard Cite

The long lifetime and the evolving nature of industrial products make them subject to technical debt at different levels. Despite multiple years of research on technical debt management, our industrial experience shows that introducing systematic technical debt management in a large-scale company is very challenging. To identify the challenges, we provide a conceptual framework for holistic debt management across the product development value stream, which takes multiple categories of debt and their interplays into account. We use this framework to identify multiple challenges that are still open to be explored by the research community. Due to the practical nature of technical debt management, we believe this paper can guide the research community on the needs of industry for the effective application of technical debt management in practice. CCS CONCEPTS• Software and its engineering → Software creation and management; Software development process management.

show abstract

Exploring the Relation between Technical Debt Principal and Interest: An Empirical Approach

Cited by 15 publications

References 16 publications

Ontology for Technical Debt in Systems Engineering

Ontology for Technical Debt in Systems Engineering

Towards a privacy debt

The Need for Holistic Technical Debt Management across the Value Stream: Lessons Learnt and Open Challenges

Contact Info

Product

Resources

About