-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathMain_Paper.tex
More file actions
78 lines (59 loc) · 2.35 KB
/
Main_Paper.tex
File metadata and controls
78 lines (59 loc) · 2.35 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
\documentclass[conference]{IEEEtran}
\makeatletter
% IEEEtran.cls defines \labelindent for backward compatibility reasons
% Undefine \labelindent to allow the use of package enumitem
\let\labelindent\relax
\makeatother
\usepackage{array}
\usepackage{booktabs}
\usepackage{cite}
\usepackage{comment}
\usepackage{enumitem}
\usepackage{fixltx2e}
\usepackage{url}
\usepackage{url}
\usepackage{graphicx}
%\usepackage{lipsum}
\input{macros}
% correct bad hyphenation here
\hyphenation{op-tical net-works semi-conduc-tor}
\begin{document}
\title{A Framework for Estimating Interest on Technical Debt by Monitoring Developer Activity Related to Code Comprehension}
\author{
\IEEEauthorblockN{Vallary Singh}
\IEEEauthorblockA{%
University of Delaware\\
Newark, DE USA\\
vallary@udel.edu}
\and
\IEEEauthorblockN{Will Snipes and Nicholas A. Kraft}
\IEEEauthorblockA{%
ABB Corporate Research\\
Raleigh, NC USA\\
\{will.snipes, nicholas.a.kraft\}@us.abb.com}
}
\maketitle
\begin{abstract}
Evaluating technical debt related to code structure at a fine-grained level of detail is feasible using static code metrics to identify troublesome areas of a software code base. However, estimating the interest payments at a similar level of detail is a manual process relying on developers to submit their estimates as they encounter instances of technical debt. We propose a framework that continuously estimates interest payments using code comprehension metrics produced by a tool that monitors developer activities in the Integrated Development Environment. We describe the framework and demonstrate how it is used to evaluate the presence of technical debt and interest payments accumulated for code in an industrial software product.
\end{abstract}
\begin{IEEEkeywords}
Technical debt; program comprehension; static analysis; software maintenance; code metrics; code smells
\end{IEEEkeywords}
\section{Introduction}
\input{Introduction}
\section{Framework}
\label{sec:DataFramework}
\input{Framework}
%\input{DataSource}
\section{Analysis}
\label{sec:AnalysisResults}
\input{AnalysisResults}
\section{Conclusions and Future Ideas}
\input{Future}
\vspace*{-4mm}
\section*{Acknowledgment}
The authors would like to thank ABB Corporate Research for supporting this work.
%\IEEEtriggeratref{8}
\bibliographystyle{IEEEtran}
\bibliography{Monitoring,wbsnipes-td,nkraft}
\end{document}