<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-forward-container">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p class="MsoNormal">Seventh International Workshop on Managing
Technical Debt (MTD 2015)<o:p></o:p></p>
<p class="MsoNormal">October 2<sup>nd</sup> 2015, Bremen, Germany,
in conjunction with ICSME 2015<o:p></o:p></p>
<p class="MsoNormal"><a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://www.sei.cmu.edu/community/td2015/">http://www.sei.cmu.edu/community/td2015/</a><o:p></o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal">Technical debt succinctly communicates the
issues observed in large-scale long-term projects:<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• There is an optimization problem where focusing on the
short-term puts the long-term into economic and technical
jeopardy.<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• Design shortcuts can give the perception of success
until their consequences start slowing projects down.<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• 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></p>
<p class="MsoNormal"><o:p> </o:p>Yet many questions remain open,
such as<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• What is the lifecycle of technical debt?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How is technical debt related to evolution and
maintenance activities?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How can information about technical debt be empirically
collected for developing conceptual models?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• What metrics need to be collected so that key
measurement and pay-off analysis can be conducted?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How can technical debt be visualized and analyzed?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How should we manage technical debt incurred by
external business constraints such as acquisitions and market
ecosystems?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How can we assign business value to intrinsic qualities
(e.g., cohesion and coupling)?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How do we manage dependencies between different items
of technical debt?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How can we create traces between technical debt items
and other software engineering artifacts?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How we can quantify costs and benefits of refactorings?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• What are the right tools for managing technical debt?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How can we apply financial theories to manage technical
debt?<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• How can we benchmark the tools that identify and
measure technical debt?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p>SUBMISSIONS<o:p></o:p></p>
<p class="MsoNormal">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 moz-do-not-send="true"
class="moz-txt-link-freetext"
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></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• Research papers, describing innovative and significant
original research in the field<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-tab-count:1">
</span>• Industrial papers, describing industrial experience,
case studies, challenges, problems, and solutions<o:p></o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal">IMPORTANT DATES: <o:p></o:p></p>
<p class="MsoListParagraphCxSpFirst"
style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-family:Symbol;mso-fareast-font-family:Symbol;mso-bidi-font-family:
Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman""> </span></span></span><!--[endif]-->Paper
submissions: June 12, 2015<o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle"
style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-family:Symbol;mso-fareast-font-family:Symbol;mso-bidi-font-family:
Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman""> </span></span></span><!--[endif]-->Notification
of authors: July 3, 2015<o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle"
style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-family:Symbol;mso-fareast-font-family:Symbol;mso-bidi-font-family:
Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman""> </span></span></span><!--[endif]-->Camera-ready
copies:<span style="mso-spacerun:yes"> </span>July 24, 2015<o:p></o:p></p>
<p class="MsoListParagraphCxSpLast"
style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-family:Symbol;mso-fareast-font-family:Symbol;mso-bidi-font-family:
Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman""> </span></span></span><!--[endif]-->Workshop:
October 2nd, 2015<o:p></o:p></p>
<p class="MsoNormal">ORGANIZERS:<o:p></o:p></p>
<p class="MsoNormal">Neil Ernst, Software Engineering Institute,
USA<o:p></o:p></p>
<p class="MsoNormal">Paris Avgeriou, University of Groningen, the
Netherlands<o:p></o:p></p>
<p class="MsoNormal">Philippe Kruchten, University of British
Columbia, Canada<o:p></o:p></p>
</div>
</body>
</html>