An Analysis of Techniques and Methods for Technical Debt Management: A Reflection from the Architecture Perspective
Open Access
- 1 May 2015
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 22-28
Abstract
Technical debt is a metaphor referring to the consequences of weak software development. Managing technical debt is necessary in order to keep it under control, and several techniques have been developed with the goal of accomplishing this. However, available techniques have grown disperse and managers lack guidance. This paper covers this gap by providing a systematic mapping of available techniques and methods for technical debt management, covering architectural debt, and identifying existing gaps that prevent to manage technical debt efficiently.Keywords
This publication has 44 references indexed in Scilit:
- Titan: a toolset that connects software architecture with quality analysis2014
- Uncertainty, risk, and information value in software requirements and architecture2014
- A Decision-Support System Approach to Economics-Driven Modularity Evaluation2014
- Aspects of Software Valuation2014
- An exploration of technical debtJournal of Systems and Software, 2013
- Comparing four approaches for technical debt identificationSoftware Quality Journal, 2013
- An empirical validation of FindBugs issues related to defects2011
- An empirical study of the bad smells and class error probability in the post-release object-oriented system evolutionJournal of Systems and Software, 2007
- Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary CodeManagement Science, 2006
- The WyCash portfolio management systemACM SIGPLAN OOPS Messenger, 1992