Tracking technical debt &amp;#x2014; An exploratory case study

Guo, Yuepu; Seaman, Carolyn; Gomes, Rebeka; Cavalcanti, Antonio; Tonin, Graziela; Silva, Fábio Q. B. da; Santos, André L. M.; Siebra, Clauirton

doi:10.1109/icsm.2011.6080824

Cited by 99 publications

(48 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Curtís et al [22] detect code and architectural violations and use information obtained from several projects to estímate the effort needed to solve these kinds of violations, considering the programming language. The second strategy consists of detecting technical debt items and utilizing the typical effort estimation that the organization uses [36] 3) Interest Estimation: For the interest estimation, some studies use an estimated maintenance effort based on information collected from other projects using the same technology [20] [35]. Others use defect likelihood and change likelihood to estímate the technical debt items' impact on system quality; in their case, they focus on classes with the God class code smell [14] [29].…”

Section: ) Identify Technical Debt íTemsmentioning

confidence: 99%

An Analysis of Techniques and Methods for Technical Debt Management: A Reflection from the Architecture Perspective

Fernández-Sánchez

Garbajosa

Vidal

et al. 2015

2015 IEEE/ACM 2nd International Workshop on Software Architecture and Metrics

View full text Add to dashboard Cite

Abstract-Technical debt is a metaphor referring to the consequences of weak software development. Managing technical debt is necessary in order to keep it under control, and several techniques have been developed with the goal of accomplishing this. However, available techniques have grown disperse and managers lack guidance. This paper covers this gap by providing a systematic mapping of available techniques and methods for technical debt management, covering architectural debt, and identifying existing gaps that prevent to manage technical debt efflciently.

show abstract

Section: ) Identify Technical Debt íTemsmentioning

confidence: 99%

An Analysis of Techniques and Methods for Technical Debt Management: A Reflection from the Architecture Perspective

Fernández-Sánchez

Garbajosa

Vidal

et al. 2015

2015 IEEE/ACM 2nd International Workshop on Software Architecture and Metrics

View full text Add to dashboard Cite

show abstract

“…These types summarize all defined types proposed by [31]. Each type of technical debt represents a different activity since the process or tool used in identification of this activity can be different.…”

Section: The Proposed Approachmentioning

confidence: 99%

“…The structure for cataloging technical debt in the proposed approach is based on the documentation structure introduced as part of the Technical Debt Management Framework (TDMF) [4,31] by Seaman et al This structure is extended in order to decompose entries into reusable components as well as to properly present technical debt in different software development activities.…”

Section: Cataloging Technical Debtmentioning

confidence: 99%

“…At this point it is necessary to contextualize decision making, but it is not detailed since the work is limited to TD identification and cataloging process, also to describe a tool for tracking TD. Guo et al [31] described one scenario in which the technical debt list is used to facilitate decision making in release planning. For this planning, the project manager sorts TD according to their cost and benefit and determines the set that should be paid to minimize the cost and maximize the benefits of the project.…”

Section: Cataloging Technical Debtmentioning

confidence: 99%

See 1 more Smart Citation

Supporting Technical Debt Cataloging with TD-Tracker Tool

Foganholi

Garcia

Eler

et al. 2015

Advances in Software Engineering

View full text Add to dashboard Cite

Technical debt (TD) is an emergent area that has stimulated academic concern. Managers must have information about debt in order to balance time-to-market advantages and issues of TD. In addition, managers must have information about TD to plan payments. Development tasks such as designing, coding, and testing generate different sorts of TD, each one with specific information. Moreover, literature review pointed out a gap in identifying and accurately cataloging technical debt. It is possible to find tools that can identify technical debt, but there is not a described solution that supports cataloging all types of debt. This paper presents an approach to create an integrated catalog of technical debts from different software development tasks. The approach allows tabulating and managing TD properties in order to support managers in the decision process. It also allows managers to track TD. The approach is implemented by TD-Tracker tool, which can integrate different TD identification tools and import identified debts. We present integrations between TD-Tracker and two external tools, used to identify potential technical debts. As part of the approach, we describe how to map the relationship between TD-Tracker and the external tools. We also show how to manage external information within TD-Tracker.

show abstract

“…It is vital that people and organizations recognize and learn from near-miss events. Another example is captured in the phrase 'technical debt' (Brown et al 2010, Guo et al 2011, Klinger et al 2011, which refers to short cuts and other expedient actions taken by IT system designers prior to a release. These may not 'cost' them anything in the very short-run, but sooner or later the 'debt' must be paid off eventually, either through patching or through the cost of security breaches.…”

Section: Why Breach Impact Estimation Is Hardmentioning

confidence: 99%