Results 11 to 20 of about 139,398 (25)

Refactoring Debt: Myth or Reality? An Exploratory Study on the Relationship Between Technical Debt and Refactoring [PDF]

open access: yesarXiv, 2022
To meet project timelines or budget constraints, developers intentionally deviate from writing optimal code to feasible code in what is known as incurring Technical Debt (TD). Furthermore, as part of planning their correction, developers document these deficiencies as comments in the code (i.e., self-admitted technical debt or SATD).
arxiv  

Towards Surgically-Precise Technical Debt Estimation: Early Results and Research Roadmap [PDF]

open access: yesIn Proceedings of the 3rd ACM SIGSOFT International Workshop on Machine Learning Techniques for Software QualityEvaluation (MaLTeSQuE '19), August 27, 2019, Tallinn, Estonia, 2019
The concept of technical debt has been explored from many perspectives but its precise estimation is still under heavy empirical and experimental inquiry. We aim to understand whether, by harnessing approximate, data-driven, machine-learning approaches it is possible to improve the current techniques for technical debt estimation, as represented by a ...
arxiv   +1 more source

Tracy: A Business-driven Technical Debt Prioritization Framework [PDF]

open access: yes, 2019
Technical debt is a pervasive problem in software development. Software development teams have to prioritize debt items and determine whether they should address debt or develop new features at any point in time. This paper presents "Tracy", a framework for the prioritization of technical debt using a business-driven approach built on top of business ...
arxiv   +1 more source

Technical Debt Management: The Road Ahead for Successful Software Delivery [PDF]

open access: yes2023 IEEE/ACM International Conference on Software Engineering: Future of Software Engineering (ICSE-FoSE)
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.
arxiv   +1 more source

Explicit Information-Debt-Optimal Streaming Codes With Small Memory [PDF]

open access: yesarXiv, 2023
For a convolutional code in the presence of a symbol erasure channel, the information debt $I(t)$ at time $t$ provides a measure of the number of additional code symbols required to recover all message symbols up to time $t$. Information-debt-optimal streaming ($i$DOS) codes are convolutional codes which allow for the recovery of all message symbols up
arxiv  

Measuring the default risk of sovereign debt from the perspective of network [PDF]

open access: yes, 2013
Recently, there has been a growing interest in network research, especially in these fields of biology, computer science, and sociology. It is natural to address complex financial issues such as the European sovereign debt crisis from the perspective of network.
arxiv   +1 more source

Debt-Prone Bugs: Technical Debt in Software Maintenance [PDF]

open access: yesarXiv, 2017
Fixing bugs is an important phase in software development and maintenance. In practice, the process of bug fixing may conflict with the release schedule. Such confliction leads to a trade-off between software quality and release schedule, which is known as the technical debt metaphor.
arxiv  

Business-Driven Technical Debt Prioritization [PDF]

open access: yes, 2019
Technical debt happens when teams take shortcuts on software development to gain short-term benefits at the cost of making future changes more expensive. Previous results show that there is a misalignment between the prioritization done by technical professionals and the prioritization expected by business ones.
arxiv   +1 more source

Architecture Smells vs. Concurrency Bugs: an Exploratory Study and Negative Results [PDF]

open access: yesarXiv, 2023
Technical debt occurs in many different forms across software artifacts. One such form is connected to software architectures where debt emerges in the form of structural anti-patterns across architecture elements, namely, architecture smells. As defined in the literature, ``Architecture smells are recurrent architectural decisions that negatively ...
arxiv  

Different Debt: An Addition to the Technical Debt Dataset and a Demonstration Using Developer Personality [PDF]

open access: yes7th International Conference on Technical Debt (TechDebt) 2024
Background: The "Technical Debt Dataset" (TDD) is a comprehensive dataset on technical debt (TD) in the main branches of more than 30 Java projects. However, some TD items produced by SonarQube are not included for many commits, for instance because the commits failed to compile. This has limited previous studies using the dataset.
arxiv   +1 more source

Home - About - Disclaimer - Privacy