![](https://dblp1.uni-trier.de/img/logo.ua.320x120.png)
![](https://dblp1.uni-trier.de/img/dropdown.dark.16x16.png)
![](https://dblp1.uni-trier.de/img/peace.dark.16x16.png)
Остановите войну!
for scientists:
![search dblp search dblp](https://dblp1.uni-trier.de/img/search.dark.16x16.png)
![search dblp](https://dblp1.uni-trier.de/img/search.dark.16x16.png)
default search action
TechDebt@ICSE 2018: Gothenburg, Sweden
- Robert L. Nord, Frank Buschmann, Philippe Kruchten:
Proceedings of the 2018 International Conference on Technical Debt, TechDebt@ICSE 2018, Gothenburg, Sweden, May 27-28, 2018. ACM 2018
Incurring debt
- Reem Alfayez
, Pooyan Behnamghader, Kamonphop Srisopha, Barry W. Boehm:
An exploratory study on the influence of developers in technical debt. 1-10 - Roberto Verdecchia
, Ivano Malavolta
, Patricia Lago
:
Architectural technical debt identification: the research landscape. 11-20
Assessing debt
- Luigi Lavazza, Sandro Morasca, Davide Tosi
:
Technical debt as an external software attribute. 21-30 - Mashel Al-Barak, Rami Bahsoon:
Prioritizing technical debt in database normalization using portfolio theory and data quality metrics. 31-40 - Allan Mori
, Gustavo Vale, Markos Viggiato, Johnatan Oliveira, Eduardo Figueiredo, Elder Cirilo, Pooyan Jamshidi
, Christian Kästner:
Evaluating domain-specific metric thresholds: an empirical study. 41-50
Tools track
- Svante Arvedahl:
Introducing debtgrep, a tool for fighting technical debt in base station software. 51-52 - Jeremy Ludwig, Steven Xu, Frederick Webber:
Static software metrics for reliability and maintainability. 53-54 - Antonio Martini:
Anacondebt: a tool to assess and track technical debt. 55-56 - G. Ann Campbell:
Cognitive complexity: an overview and evaluation. 57-58 - Adam Tornhill:
Prioritize technical debt in large-scale systems using codescene. 59-60
Managing the debt I (short papers)
- Eoin Woods:
The past, present and future of technical debt: learning from the past to prepare for the future. 61 - Theodoros Amanatidis, Nikolaos Mittas
, Alexander Chatzigeorgiou, Apostolos Ampatzoglou, Lefteris Angelis:
The developer's dilemma: factors affecting the decision to repay code debt. 62-66 - Abdullah Aldaeej
, Carolyn B. Seaman:
From lasagna to spaghetti, a decision model to manage defect debt. 67-71 - Will Snipes, Srini Ramaswamy:
A proposed sizing model for managing 3rd party code technical debt. 72-75
Managing the debt II
- Johan Magnusson, Carlos Juiz, Beatriz Gómez
, Belén Bermejo:
Governing technology debt: beyond technical debt. 76-84 - Christoph Becker, Ruzanna Chitchyan
, Stefanie Betz, Curtis McCord:
Trade-off decisions across time in technical debt management: a systematic literature review. 85-94 - Reinhold Plösch, Johannes Bräuer, Matthias Saft, Christian Körner:
Design debt prioritization: a design best practice-based approach. 95-104
Practice in industry
- Terese Besker
, Antonio Martini, Jan Bosch:
Technical debt cripples software developer productivity: a longitudinal study on developers' daily software development work. 105-114 - Areti Ampatzoglou, Alexandros Michailidis, Christos Sarikyriakidis, Apostolos Ampatzoglou, Alexander Chatzigeorgiou, Paris Avgeriou
:
A framework for managing interest in technical debt: an industrial validation. 115-124 - Justus Bogner
, Jonas Fritzsch, Stefan Wagner
, Alfred Zimmermann:
Limiting technical debt with maintainability assurance: an industry survey on used techniques and differences with service- and microservice-based systems. 125-133
Future research (short papers)
- Thomas Stablein, Donald J. Berndt, Matthew Mullarkey:
Technical debt-related information asymmetry between finance and IT. 134-137 - Clemente Izurieta
, David Rice, Kali Kimball, Tessa Valentien:
A position study to investigate technical debt associated with security weaknesses. 138-142
![](https://dblp1.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.