The Seventh International Workshop on Managing Technical Debt is coming to Bremen, Germany, during the week of September 29 in conjunction with ICSME 2015.
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. Technical debt succinctly communicates the issues observed in large-scale long-term projects:
- There is an optimization problem where focusing on the short-term puts the long-term into economic and technical jeopardy.
- Design shortcuts can give the perception of success until their consequences start slowing projects down.
- Software development decisions, especially architectural ones, must be actively managed and continuously analyzed quantitatively as they incur cost, value, and debt.
Yet many questions remain open, such as:
- What is the lifecycle of technical debt?
- How is technical debt related to evolution and maintenance activities?
- How can information about technical debt be empirically collected for developing conceptual models?
- What metrics need to be collected so that key measurement and pay-off analysis can be conducted?
- How can technical debt be visualized and analyzed?
- How should we manage technical debt incurred by external business constraints such as acquisitions and market ecosystems?
- How can we assign business value to intrinsic qualities (e.g., cohesion and coupling)?
- How do we manage dependencies between different items of technical debt?
- How can we create traces between technical debt items and other software engineering artifacts?
- How we can quantify costs and benefits of refactorings?
- What are the right tools for managing technical debt?
- How can we apply financial theories to manage technical debt?
- How can we benchmark the tools that identify and measure technical debt?
The keynote speaker is Arie van Deursen from the Delft University of Technology (bio).
12 papers will be presented at the conference:
- Detecting and Quantifying Different Types of Self-Admitted Technical Debt, Everton Maldonado and Emad Shihab
- Estimating the Breaking Point for Technical Debt, Alexander Chatzigeorgiou, Apostolos Ampatzoglou, Areti Ampatzoglou, and Theodoros Amanatidis
- Toward a Prioritization of Code Debt: A Code Smell Intensity Index, Francesca Arcelli Fontana, Vincenzo Ferme, Marco Zanoni, and Riccardo Roveda
- Toward an Open-Source Tool for Measuring and Visualizing the Interest of Technical Debt, Davide Falessi and Andreas Reichel
- Technical Debt in Automated Production Systems, Birgit Vogel-Heuser, Susanne Rösch, Antonio Martini, and Matthias Tichy
- The Restructuring and Refinancing of Technical Debt, Raul Zablah and Christian Murphy
- An Analysis of the Elements of Technical Debt Management, Carlos Fernández-Sánchez, Juan Garbajosa, and Agustín Yagüe
- Technical Debt of Standardized Test Software, Kristóf Szabados and Attila Kovács
- A Contextualized Vocabulary Model for Identifying Technical Debt on Code Comments, Mário André Freitas Farias, André Batista Silva, Manoel G. De Mendonça Neto, and Rodrigo Oliveira Spínola
- Identifying and Visualizing Architectural Debt and Its Efficiency Interest in the Automotive Domain: A Case Study, Ulf Eliasson, Antonio Martini, Robert Kaufmann, and Sam Odeh
- Validating and Prioritizing Quality Rules for Managing Techncial Debt: An Industrial Case Study, Davide Falessi
- Decision-Making Framework for Refactoring, Marko Leppänen, Samuel Lahtinen, Kati Kuusinen, Simo Mäkinen, Tomi Männistö, Juha Itkonen, Jesse Yli-Huumo, and Timo Lehtonen
Neil Ernst, Software Engineering Institute, USA
Paris Avgeriou, University of Groningen, the Netherlands
Philippe Kruchten, University of British Columbia, Canada
CISQ will be attending MTD 2015.
To learn more click here.