Results 1 to 10 of about 139,398 (25)
WeakSATD: Detecting Weak Self-admitted Technical Debt [PDF]
Speeding up development may produce technical debt, i.e., not-quite-right code for which the effort to make it right increases with time as a sort of interest. Developers may be aware of the debt as they admit it in their code comments. Literature reports that such a self-admitted technical debt survives for a long time in a program, but it is not yet ...
arxiv +1 more source
Business-Driven Technical Debt Prioritization: An Industrial Case Study [PDF]
Incorporating the business perspective into prioritizing technical debt is essential to contribute to decision making in industry. In this paper, we evolve and evaluate a business-driven approach for technical debt prioritization. The approach was evaluated during a five-month industrial case study with business and technical stakeholders' active ...
arxiv +1 more source
SoHist: A Tool for Managing Technical Debt through Retro Perspective Code Analysis [PDF]
Technical debt is often the result of Short Run decisions made during code development, which can lead to long-term maintenance costs and risks. Hence, evaluating the progression of a project and understanding related code quality aspects is essential.
arxiv +1 more source
Exploration of technical debt in start-ups [PDF]
Context: Software start-ups are young companies aiming to build and market software-intensive products fast with little resources. Aiming to accelerate time-to-market, start-ups often opt for ad-hoc engineering practices, make shortcuts in product engineering, and accumulate technical debt. Objective: In this paper we explore to what extent precedents,
arxiv +1 more source
The Influence of Cognitive Biases on Architectural Technical Debt [PDF]
Cognitive biases exert a significant influence on human thinking and decision-making. In order to identify how they influence the occurrence of architectural technical debt, a series of semi-structured interviews with software architects was performed.
arxiv +1 more source
The Effect of External Debt on Greenhouse Gas Emissions [PDF]
We estimate the causal effect of external debt on greenhouse gas emissions in a panel of 78 emerging market and developing economies over the 1990-2015 period. Unlike previous literature, we use external instruments to address the potential endogeneity in the relationship between external debt and greenhouse gas emissions.
arxiv
UX Debt: Developers Borrow While Users Pay [PDF]
Technical debt has become a well-known metaphor among software professionals, illustrating how shortcuts taken during development can accumulate and become a burden for software projects. In the traditional notion of technical debt, software developers borrow from the maintainability and extensibility of a software system for a short-term speed up in ...
arxiv
Aligning Technical Debt Prioritization with Business Objectives: A Multiple-Case Study [PDF]
Technical debt (TD) is a metaphor to describe the trade-off between short-term workarounds and long-term goals in software development. Despite being widely used to explain technical issues in business terms, industry and academia still lack a proper way to manage technical debt while explicitly considering business priorities. In this paper, we report
arxiv +1 more source
An Exploratory Study on the Occurrence of Self-Admitted Technical Debt in Android Apps [PDF]
Technical debt describes situations where developers write less-than-optimal code to meet project milestones. However, this debt accumulation often results in future developer effort to live with or fix these quality issues. To better manage this debt, developers may document their sub-optimal code as comments in the code (i.e., self-admitted technical
arxiv
The Technical Debt Dataset [PDF]
Technical Debt analysis is increasing in popularity as nowadays researchers and industry are adopting various tools for static code analysis to evaluate the quality of their code. Despite this, empirical studies on software projects are expensive because of the time needed to analyze the projects.
arxiv +1 more source