Conference paper Open Access

# Monitoring Technical Debt in an Industrial Setting

Elvira-Maria Arvanitou; Apostolos Ampatzoglou; Stamatia Bibi; Alexander Chatzigeorgiou; Ioannis Stamelos

### Dublin Core Export

<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:creator>Elvira-Maria Arvanitou</dc:creator>
<dc:creator>Apostolos Ampatzoglou</dc:creator>
<dc:creator>Stamatia Bibi</dc:creator>
<dc:creator>Alexander Chatzigeorgiou</dc:creator>
<dc:creator>Ioannis Stamelos</dc:creator>
<dc:date>2019-04-15</dc:date>
<dc:description>Technical Debt (TD) quantification has been studied in the literature and is supported by various tools; however, there is no common ground on what information shall be presented to stakeholders. Similarly to other quality monitoring processes, it is desirable to provide several views of quality through a dashboard, in which metrics concerning the phenomenon of interest are displayed.

The aim of this study is to investigate the indicators that shall be presented in such a dashboard, so as to: (a) be meaningful for industrial stakeholders, (b) present all necessary information, and (c) be simple enough so that stakeholders can use them.

We explore TD Management (TDM) activities (i.e., measurement, prioritization, repayment) and choose the main concepts that need to be visualized, based on existing literature and toolsupport. Next, we perform a survey with 60 software engineers (i.e., architects, developers, etc.) working for 11 software development companies located in 9 countries, to understand their needs for TDM.

The results of the study suggest that different stakeholders need a different view of the quality dashboard, but also some commonalities can be identified. For example, on the one hand, managers are mostly interested in financial concepts, whereas on the other hand developers are more interested in the nature of the problems that exist in the code. The outcomes of this study can be useful to both researchers and practitioners, in the sense that the former can focus their efforts on aspects that are meaningful to industry, whereas the latter to develop meaningful dashboards, with multiple views.</dc:description>
<dc:identifier>https://zenodo.org/record/3380164</dc:identifier>
<dc:identifier>10.1145/3319008.3319019</dc:identifier>
<dc:identifier>oai:zenodo.org:3380164</dc:identifier>
<dc:relation>info:eu-repo/grantAgreement/EC/H2020/780572/</dc:relation>
<dc:rights>info:eu-repo/semantics/openAccess</dc:rights>
<dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
<dc:subject>Technical debt, visualization, metrics, software quality, survey</dc:subject>
<dc:title>Monitoring Technical Debt in an Industrial Setting</dc:title>
<dc:type>info:eu-repo/semantics/conferencePaper</dc:type>
<dc:type>publication-conferencepaper</dc:type>
</oai_dc:dc>

75
125
views
downloads
 Views 75 Downloads 125 Data volume 136.5 MB Unique views 71 Unique downloads 117