A systematic mapping study on technical debt definition

The goal of this study was to explore and understand the definition of technical debt. Technical debt refers to situation in a software development, where shortcuts or workarounds are taken in technical decision. However, the original definition has been applied to other parts of software development and it is currently difficult to define technical debt. We used mapping study process as a research methodology to collect literature related to the research topic. We collected 159 papers that referred to original definition of technical debt, which were retrieved from scientific literature databases to conduct the search process. We retrieved 107 definitions that were split into keywords. The keyword map is one of the main results of this work. Apart from that, resulting synonyms and different types of technical debt were analyzed and added to the map as branches.

[1]  Ward Cunningham,et al.  The WyCash portfolio management system , 1992, OOPSLA '92.

[2]  Watts S. Humphrey,et al.  Software process development and enactment: concepts and definitions , 1993, [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement.

[3]  Taghi M. Khoshgoftaar,et al.  Modeling the relationship between source code complexity and maintenance difficulty , 1994, Computer.

[4]  Joseph W. Yoder,et al.  Big Ball of Mud , 1997 .

[5]  David R. Jones,et al.  Synthesising qualitative and quantitative evidence: A review of possible methods , 2005 .

[6]  Pearl Brereton,et al.  Performing systematic literature reviews in software engineering , 2006, ICSE.

[7]  Tore Dybå,et al.  A systematic review of statistical power in software engineering experiments , 2006, Inf. Softw. Technol..

[8]  Tore Dybå,et al.  A Systematic Review of Theory Use in Software Engineering Experiments , 2007, IEEE Transactions on Software Engineering.

[9]  Pearl Brereton,et al.  Preliminary results of a study of the completeness and clarity of structured abstracts , 2007, EASE.

[10]  Khaled El Emam,et al.  A Replicated Survey of IT Software Project Failures , 2008, IEEE Software.

[11]  Kai Petersen,et al.  Systematic Mapping Studies in Software Engineering , 2008, EASE.

[12]  Pearl Brereton,et al.  Systematic literature reviews in software engineering - A systematic literature review , 2009, Inf. Softw. Technol..

[13]  Roel Wieringa,et al.  Harmfulness of Code Duplication - A Structured Review of the Evidence , 2009, EASE.

[14]  Forrest Shull,et al.  Domain-specific tailoring of code smells: an empirical study , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[15]  Oualid Ktata,et al.  Designing and implementing a measurement program for Scrum teams: what do agile developers really need and want? , 2010, C3S2E '10.

[16]  Forrest Shull,et al.  Building empirical support for automated code smell detection , 2010, ESEM '10.

[17]  Lech Madeyski,et al.  The impact of Test-First programming on branch coverage and mutation score indicator of unit tests: An experiment , 2010, Inf. Softw. Technol..

[18]  Carolyn B. Seaman,et al.  A portfolio approach to technical debt management , 2011, MTD '11.

[19]  Nitin Taksande,et al.  Empirical study on technical debt as viewed by software practitioners , 2011 .

[20]  Peri L. Tarr,et al.  An enterprise perspective on technical debt , 2011, MTD '11.

[21]  Carolyn B. Seaman,et al.  Measuring and Monitoring Technical Debt , 2011, Adv. Comput..

[22]  Eleni Stroulia,et al.  Code convention adherence in evolving software , 2011, 2011 27th IEEE International Conference on Software Maintenance (ICSM).

[23]  Joost Visser,et al.  An empirical model of technical debt and interest , 2011, MTD '11.

[24]  Erin Lim,et al.  Technical debt : what software practitioners have to say , 2012 .

[25]  Robert L. Nord,et al.  Technical debt in software development: from metaphor to theory report on the third international workshop on managing technical debt , 2012, SOEN.

[26]  Thomas Bäck,et al.  What is the value of your software? , 2012, 2012 Third International Workshop on Managing Technical Debt (MTD).

[27]  Peter DePasquale,et al.  Identifying effective pedagogical practices for commenting computer source code (abstract only) , 2012, SIGCSE '12.

[28]  Bill Curtis,et al.  Estimating the Principal of an Application's Technical Debt , 2012, IEEE Software.

[29]  Robert L. Nord,et al.  Technical Debt: From Metaphor to Theory and Practice , 2012, IEEE Software.

[30]  Robert L. Nord,et al.  In Search of a Metric for Managing Architectural Technical Debt , 2012, 2012 Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture.

[31]  Carolyn B. Seaman,et al.  A Balancing Act: What Software Practitioners Have to Say about Technical Debt , 2012, IEEE Softw..

[32]  Markus Lindgren.  Bridging the software quality gap , 2012 .

[33]  Ipek Ozkaya,et al.  Technical debt: from source to mitigation , 2013, SPLASH '13.

[34]  Forrest Shull,et al.  A case study on effectively identifying technical debt , 2013, EASE '13.

[35]  Zadia Codabux,et al.  Managing technical debt: An industrial case study , 2013, 2013 4th International Workshop on Managing Technical Debt (MTD).

[36]  Forrest Shull,et al.  Technical Debt: Showing the Way for Better Transfer of Empirical Results , 2013, Perspectives on the Future of Software Engineering.

[37]  Robert L. Nord,et al.  Technical debt: towards a crisper definition report on the 4th international workshop on managing technical debt , 2013, SOEN.

[38]  Philippe Kruchten,et al.  What is social debt in software engineering? , 2013, 2013 6th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE).

[39]  Richard T. Vidgen,et al.  An exploration of technical debt , 2013, J. Syst. Softw..

[40]  Gal Shachor,et al.  Restraining Technical Debt when Developing Large-Scale Ajax Applications , 2013 .

[41]  Rodrigo O. Spínola,et al.  Exploring the costs of technical debt management – a case study , 2016, Empirical Software Engineering.

[42]  Jesse Yli-Huumo,et al.  The Sources and Approaches to Management of Technical Debt: A Case Study of Two Product Lines in a Middle-Size Finnish Software Company , 2014, PROFES.

[43]  Reinhold Plösch,et al.  A Benchmarking-Based Model for Technical Debt Calculation , 2014, 2014 14th International Conference on Quality Software.

[44]  Rodrigo O. Spínola,et al.  Towards an Ontology of Terms on Technical Debt , 2014, 2014 Sixth International Workshop on Managing Technical Debt.

[45]  Johannes Holvitie.  Software implementation knowledge management with technical debt and network analysis , 2014, 2014 IEEE Eighth International Conference on Research Challenges in Information Science (RCIS).

[46]  Anton Johansson,et al.  Evaluating future IT-investment options through technology debt -A case study and theory testing approach on Company AB , 2014 .

[47]  Robert L. Nord,et al.  Technical debt at the crossroads of research and practice: report on the fifth international workshop on managing technical debt , 2014, SOEN.

[48]  Clemente Izurieta,et al.  A simulation study of practical methods for technical debt management in agile software development , 2014, Proceedings of the Winter Simulation Conference 2014.

[49]  Narayan Ramasubbu,et al.  Managing Technical Debt in Enterprise Software Packages , 2014, IEEE Transactions on Software Engineering.

[50]  A. D. Lucia,et al.  When and Why Your Code Starts to Smell Bad , 2017, 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering.

[51]  Peng Liang,et al.  A systematic mapping study on technical debt and its management , 2015, J. Syst. Softw..

[52]  Mauricio A. Saca.  Refactoring improving the design of existing code , 2017, 2017 IEEE 37th Central America and Panama Convention (CONCAPAN XXXVII).