<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText"><span lang="EN-US">CALL FOR PAPERS<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Seventh International Workshop on Managing Technical Debt (MTD 2015)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">October 2nd 2015, Bremen, Germany, in conjunction with ICSME 2015<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><a href="http://www.sei.cmu.edu/community/td2015/">http://www.sei.cmu.edu/community/td2015/</a><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Delivering complex, large-scale systems faces the ongoing challenge of how best to balance rapid deployment with long-term value. Theoretical foundations and empirical evidence for analyzing and optimizing short- term
versus long-term goals in large-scale projects are needed. From the original description—“not quite right code, which we postpone making right”—various people have used the metaphor of technical debt to describe many kinds of debts or ills of software development.
On one hand, the practitioner community has increased interest in understanding and managing debt. On the other hand, the research community has an opportunity to study this phenomenon and improve the way it is handled. We can offer software engineers a foundation
for managing such tradeoffs based on models of their economic impacts. <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Technical debt succinctly communicates the issues observed in large-scale long-term projects:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - There is an optimization problem where focusing on the short-term puts the long-term into economic and technical jeopardy.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - Design shortcuts can give the perception of success until their consequences start slowing projects down.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - Software development decisions, especially architectural ones, must be actively managed and continuously analyzed quantitatively as they incur cost, value, and debt.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Yet many questions remain open, such as<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - What is the lifecycle of technical debt?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How is technical debt related to evolution and maintenance activities?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How can information about technical debt be empirically collected for developing conceptual models?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - What metrics need to be collected so that key measurement and pay-off analysis can be conducted?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How can technical debt be visualized and analyzed?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How should we manage technical debt incurred by external business constraints such as acquisitions and market ecosystems?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How can we assign business value to intrinsic qualities (e.g., cohesion and coupling)?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How do we manage dependencies between different items of technical debt?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How can we create traces between technical debt items and other software engineering artifacts?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How we can quantify costs and benefits of refactorings?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - What are the right tools for managing technical debt?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How can we apply financial theories to manage technical debt?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - How can we benchmark the tools that identify and measure technical debt?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">SUBMISSIONS<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">We seek papers on practical experience with technical debt and approaches that attempt to answer these questions. All submitted papers must conform to the IEEE Conference Publishing Services (CPS) formatting instructions,
and must not exceed 8 pages for all text, inclusive of figures, tables, and appendices, with up to one additional page for references only. All submissions must be in PDF. Submit your paper electronically via EasyChair (<a href="https://easychair.org/conferences/?conf=mtd15">https://easychair.org/conferences/?conf=mtd15</a>).
We invite submissions of papers in the following categories:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - Research papers, describing innovative and significant original research in the field<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> - Industrial papers, describing industrial experience, case studies, challenges, problems, and solutions<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">In either category, we look for long papers (8 pages), describing mature results, and short papers (4 pages), describing emerging results and future trends.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">IMPORTANT DATES: <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">- Paper submissions: June 12, 2015<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">- Notification of authors: July 3, 2015<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">- Camera-ready copies: July 24, 2015<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">- Workshop: October 2nd, 2015<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">ORGANIZERS:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Neil Ernst, Software Engineering Institute, USA<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Paris Avgeriou, University of Groningen, the Netherlands<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Philippe Kruchten, University of British Columbia, Canada<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Visit the workshop website at <a href="http://www.sei.cmu.edu/community/td2015/">
http://www.sei.cmu.edu/community/td2015/</a><o:p></o:p></span></p>
</div>
</body>
</html>