Technical Debt Management: The Road Ahead for Successful Software
Delivery
- URL: http://arxiv.org/abs/2403.06484v1
- Date: Mon, 11 Mar 2024 07:48:35 GMT
- Title: Technical Debt Management: The Road Ahead for Successful Software
Delivery
- Authors: Paris Avgeriou, Ipek Ozkaya, Alexander Chatzigeorgiou, Marcus
Ciolkowski, Neil A. Ernst, Ronald J. Koontz, Eltjo Poort, Forrest Shull
- Abstract summary: Technical Debt, considered by many to be the'silent killer' of software projects, has undeniably become part of the everyday vocabulary of software engineers.
In this paper, we examine the state of the art in both industry and research communities in managing Technical Debt.
- Score: 40.45645113369735
- License: http://creativecommons.org/licenses/by-nc-nd/4.0/
- Abstract: Technical Debt, considered by many to be the 'silent killer' of software
projects, has undeniably become part of the everyday vocabulary of software
engineers. We know it compromises the internal quality of a system, either
deliberately or inadvertently. We understand Technical Debt is not all
derogatory, often serving the purpose of expediency. But, it is associated with
a clear risk, especially for large and complex systems with extended service
life: if we do not properly manage Technical Debt, it threatens to "bankrupt"
those systems. Software engineers and organizations that develop
software-intensive systems are facing an increasingly more dire future state of
those systems if they do not start incorporating Technical Debt management into
their day to day practice. But how? What have the wins and losses of the past
decade of research and practice in managing Technical Debt taught us and where
should we focus next? In this paper, we examine the state of the art in both
industry and research communities in managing Technical Debt; we subsequently
distill the gaps in industrial practice and the research shortcomings, and
synthesize them to define and articulate a vision for what Technical Debt
management looks like five years hence.
Related papers
- Exploring the Advances in Using Machine Learning to Identify Technical Debt and Self-Admitted Technical Debt [0.0]
This study seeks to provide a reflection on the current research landscape employing machine learning methods for detecting technical debt and self-admitted technical debt in software projects.
We performed a literature review of studies published up to 2024 that discuss technical debt and self-admitted technical debt identification using machine learning.
Our findings reveal the utilization of a diverse range of machine learning techniques, with BERT models proving significantly more effective than others.
arXiv Detail & Related papers (2024-09-06T23:58:10Z) - Contemporary Software Modernization: Perspectives and Challenges to Deal with Legacy Systems [48.33168695898682]
"Software modernization" emerged as a research topic in the early 2000s.
Despite the large amount of work available in the literature, there are significant limitations.
arXiv Detail & Related papers (2024-07-04T15:49:52Z) - Charting a Path to Efficient Onboarding: The Role of Software
Visualization [49.1574468325115]
The present study aims to explore the familiarity of managers, leaders, and developers with software visualization tools.
This approach incorporated quantitative and qualitative analyses of data collected from practitioners using questionnaires and semi-structured interviews.
arXiv Detail & Related papers (2024-01-17T21:30:45Z) - Exploration of technical debt in start-ups [5.664445343364966]
We apply a case survey method to identify aspects of technical debt and contextual information characterizing the engineering context in start-ups.
We found that start-ups accumulate most technical debt in the testing dimension, despite attempts to automate testing.
We found that start-up team size and experience is a leading precedent for accumulating technical debt.
arXiv Detail & Related papers (2023-09-21T19:02:02Z) - Automatically Estimating the Effort Required to Repay Self-Admitted
Technical Debt [1.8208834479445897]
Self-Admitted Technical Debt (SATD) is a specific form of technical debt documented by developers within software artifacts.
We propose a novel approach for automatically estimating SATD repayment effort, utilizing a comprehensive dataset.
Our findings show that different types of SATD require varying levels of repayment effort, with code/design, requirement, and test debt demanding greater effort compared to non-SATD items.
arXiv Detail & Related papers (2023-09-12T07:40:18Z) - Artificial Intelligence for Technical Debt Management in Software
Development [0.0]
Review of existing research on the use of AI powered tools for technical debt avoidance in software development.
Suggests that AI has the potential to significantly improve technical debt management in software development.
Offers practical guidance for software development teams seeking to leverage AI in their development processes.
arXiv Detail & Related papers (2023-06-16T21:59:22Z) - Lessons from Formally Verified Deployed Software Systems (Extended version) [65.69802414600832]
This article examines a range of projects, in various application areas, that have produced formally verified systems and deployed them for actual use.
It considers the technologies used, the form of verification applied, the results obtained, and the lessons that the software industry should draw regarding its ability to benefit from formal verification techniques and tools.
arXiv Detail & Related papers (2023-01-05T18:18:46Z) - Future Computer Systems and Networking Research in the Netherlands: A
Manifesto [137.47124933818066]
We draw attention to CompSys as a vital part of ICT.
Each of the Top Sectors of the Dutch Economy, each route in the National Research Agenda, and each of the UN Sustainable Development Goals pose challenges that cannot be addressed without CompSys advances.
arXiv Detail & Related papers (2022-05-26T11:02:29Z) - UX Debt: Developers Borrow While Users Pay [2.9479490707938982]
User experience (UX) debt focuses on shortcuts taken to speed up development at the expense of subpar usability.
Most research considers code-centric technical debt, focusing on the implementation.
We outline three classes of UX debt that we observed in practice: code-centric, architecture-centric, and process-centric.
arXiv Detail & Related papers (2021-04-14T14:59:44Z) - Machine Learning for Software Engineering: A Systematic Mapping [73.30245214374027]
The software development industry is rapidly adopting machine learning for transitioning modern day software systems towards highly intelligent and self-learning systems.
No comprehensive study exists that explores the current state-of-the-art on the adoption of machine learning across software engineering life cycle stages.
This study introduces a machine learning for software engineering (MLSE) taxonomy classifying the state-of-the-art machine learning techniques according to their applicability to various software engineering life cycle stages.
arXiv Detail & Related papers (2020-05-27T11:56:56Z)
This list is automatically generated from the titles and abstracts of the papers in this site.
This site does not guarantee the quality of this site (including all information) and is not responsible for any consequences.