![](https://dblp.uni-trier.de./img/logo.320x120.png)
![search dblp search dblp](https://dblp.uni-trier.de./img/search.dark.16x16.png)
![search dblp](https://dblp.uni-trier.de./img/search.dark.16x16.png)
default search action
TechDebt@ICSE 2019: Montreal, QC, Canada
- Paris Avgeriou, Klaus Schmid:
Proceedings of the Second International Conference on Technical Debt, TechDebt@ICSE 2019, Montreal, QC, Canada, May 26-27, 2019. IEEE / ACM 2019, ISBN 978-1-7281-3371-3
Keynote presentation
- Valentin Guerlesquin:
How (not) to remove technical debt in testing environments: six good way to fail. 1-2
Managing technical debt at viger
- Nicolli Rios, Rodrigo Oliveira Spínola, Manoel Gomes de Mendonça Neto
, Carolyn B. Seaman:
Supporting analysis of technical debt causes and effects with cross-company probabilistic cause-effect diagrams. 3-12 - Terese Besker
, Antonio Martini, Jan Bosch:
Technical debt triage in backlog management. 13-22 - Christoph Becker, Fabian Fagerholm
, Rahul Mohanani, Alexander Chatzigeorgiou:
Temporal discounting in technical debt: how do software practitioners discount the future? 23-32
Technical debt in practice at viger
- Clemente Izurieta
, Mary Prouty:
Leveraging secdevops to tackle the technical debt associated with cybersecurity attack tactics. 33-37 - Richard Brenner:
Balancing resources and load: eleven nontechnical phenomena that contribute to formation or persistence of technical debt. 38-47 - Geir Kjetil Hanssen, Gunnar Brataas
, Antonio Martini:
Identifying scalability debt in open systems. 48-52
Tool demos at viger
- Yuanfang Cai, Rick Kazman:
DV8: automated architecture analysis tool suites. 53-54 - Roman Haas, Rainer Niedermayr, Elmar Jürgens:
Teamscale: tackle technical debt and control the quality of your software. 55-56 - Jeremy Ludwig, Devin Cline:
CBR insight: measure and visualize source code quality. 57-58 - Tushar Sharma
:
How deep is the mud: fathoming architecture technical debt using designite. 59-60 - Dan Sturtevant:
Silverthread CodeMRI care. 61
Keynote presentation
- Danny Dig:
Lessons from the exponential growth of refactoring research in the last decade. 62-63
Tool demos at viger
- Boris Kontsevoi, Elizabeth Soroka, Sergei Terekhov:
TETRA, as a set of techniques and tools for calculating technical debt principal and interest. 64-65 - Alexander von Zitzewitz:
Mitigating technical and architectural debt with sonargraph: using static analysis to enforce architectural constraints. 66-67 - Simon Baars
, Sander Meester:
CodeArena: inspecting and improving code quality metrics using minecraft. 68-70 - Paul Anderson, Lucja Kot, Neil Gilmore, David Vitek:
SARIF-enabled tooling to encourage gradual technical debt reduction. 71-72
Architectural technical debt at viger
- Boris Pérez, Darío Correal, Hernán Astudillo
:
A proposed model-driven approach to manage architectural technical debt life cycle. 73-77 - Saulo S. de Toledo, Antonio Martini, Agata Przybyszewska, Dag I. K. Sjøberg:
Architectural technical debt in microservices: a case study in a large company. 78-87 - Umberto Azadi, Francesca Arcelli Fontana, Davide Taibi
:
Architectural smells detected by tools: a catalogue proposal. 88-97
Technical debt in source code and code quality at viger
- Nyyti Saarimäki
, Valentina Lenarduzzi
, Davide Taibi
:
On the diffuseness of code technical debt in Java projects of the apache ecosystem. 98-107 - Lerina Aversano
, Laura Nardi:
Investigating on the impact of software clones on technical debt. 108-112 - Marco di Biase, Ayushi Rastogi, Magiel Bruntink, Arie van Deursen
:
The delta maintainability model: measuring maintainability of fine-grained code changes. 113-122
Poster paper
- Morgan Ericsson, Anna Wingkvist
:
TDMentions: a dataset of technical debt mentions in online posts. 123-124
![](https://dblp.uni-trier.de./img/cog.dark.24x24.png)
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.