Abstract is missing.
- How (not) to remove technical debt in testing environments: six good way to failValentin Guerlesquin. 1-2 [doi]
- Supporting analysis of technical debt causes and effects with cross-company probabilistic cause-effect diagramsNicolli Rios, Rodrigo Oliveira Spínola, Manoel Gomes de Mendonça Neto, Carolyn B. Seaman. 3-12 [doi]
- Technical debt triage in backlog managementTerese Besker, Antonio Martini, Jan Bosch. 13-22 [doi]
- Temporal discounting in technical debt: how do software practitioners discount the future?Christoph Becker, Fabian Fagerholm, Rahul Mohanani, Alexander Chatzigeorgiou. 23-32 [doi]
- Leveraging secdevops to tackle the technical debt associated with cybersecurity attack tacticsClemente Izurieta, Mary Prouty. 33-37 [doi]
- Balancing resources and load: eleven nontechnical phenomena that contribute to formation or persistence of technical debtRichard Brenner. 38-47 [doi]
- Identifying scalability debt in open systemsGeir Kjetil Hanssen, Gunnar Brataas, Antonio Martini. 48-52 [doi]
- DV8: automated architecture analysis tool suitesYuanfang Cai, Rick Kazman. 53-54 [doi]
- Teamscale: tackle technical debt and control the quality of your softwareRoman Haas, Rainer Niedermayr, Elmar Jürgens. 55-56 [doi]
- CBR insight: measure and visualize source code qualityJeremy Ludwig, Devin Cline. 57-58 [doi]
- How deep is the mud: fathoming architecture technical debt using designiteTushar Sharma. 59-60 [doi]
- Silverthread CodeMRI careDan Sturtevant. 61 [doi]
- Lessons from the exponential growth of refactoring research in the last decadeDanny Dig. 62-63 [doi]
- TETRA, as a set of techniques and tools for calculating technical debt principal and interestBoris Kontsevoi, Elizabeth Soroka, Sergei Terekhov. 64-65 [doi]
- Mitigating technical and architectural debt with sonargraph: using static analysis to enforce architectural constraintsAlexander von Zitzewitz. 66-67 [doi]
- CodeArena: inspecting and improving code quality metrics using minecraftSimon Baars, Sander Meester. 68-70 [doi]
- SARIF-enabled tooling to encourage gradual technical debt reductionPaul Anderson, Lucja Kot, Neil Gilmore, David Vitek. 71-72 [doi]
- A proposed model-driven approach to manage architectural technical debt life cycleBoris Pérez, Darío Correal, Hernán Astudillo. 73-77 [doi]
- Architectural technical debt in microservices: a case study in a large companySaulo S. de Toledo, Antonio Martini, Agata Przybyszewska, Dag I. K. Sjøberg. 78-87 [doi]
- Architectural smells detected by tools: a catalogue proposalUmberto Azadi, Francesca Arcelli Fontana, Davide Taibi. 88-97 [doi]
- On the diffuseness of code technical debt in Java projects of the apache ecosystemNyyti Saarimäki, Valentina Lenarduzzi, Davide Taibi. 98-107 [doi]
- Investigating on the impact of software clones on technical debtLerina Aversano, Laura Nardi. 108-112 [doi]
- The delta maintainability model: measuring maintainability of fine-grained code changesMarco di Biase, Ayushi Rastogi, Magiel Bruntink, Arie van Deursen. 113-122 [doi]
- TDMentions: a dataset of technical debt mentions in online postsMorgan Ericsson, Anna Wingkvist. 123-124 [doi]