Global ETD Search
Search theses and dissertations gathered from participating repositories worldwide. Every result links back to the library that holds it. No account is needed.
Results
Showing 1 to 20 of 98 for “"technical debt"”.
-
Business-driven technical debt prioritization
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 misalignment between the prioritization done by technical professionals and the prioritization expected by business ones. …
-
Identifying Self-Admitted Technical Debt
Technical debt is a metaphor coined to express the trade off between productivity and quality, e.g., when developers take shortcuts or perform quick hacks during the development of software projects. These non optimal solutions are often implemented to allow the project to move faster in the short …
-
Identifying technical debt through issue trackers
Technical debt is a figurative expression to describe a phenomenon where software development organizations compromise some quality attributes of their products (e.g., maintainability and evolvability) in order to achieve some business benefits in the software development lifecycle. Technical debt …
-
Technical debt decision-making under uncertainty
The key to effective technical debt management (TDM) decision-making is to select a feasible and conclusive decision on time. Decision-making, in general, can suffer from uncertainties, obscuring a problem domain and challenging one from producing a useful decision. However, the presence of …
-
Risk Assessment of Architecture Technical Debt
Technical Debt (TD) is a metaphor that refers to short-term solutions in software development that may affect the software development life cycle cost. Researchers have found many TD types. These TD types include but are not limited to code debt (CD), design debt (DD), and architecture technical …
-
Modelling the Quantification of Technical Debt: A Theoretical Foundation for Quantifying Code, Design, Architecture, and Requirements Technical Debt
… such as faster time to market. The metaphor 'Technical Debt (TD)' captures the consequences of such sub-optimal decisions. TD could be detrimental to a software company unless managed; it could lead to large cost overruns and have adverse effects on the company's reputation. When taken …
-
Estimating Refactoring Efforts for Architecture Technical Debt
Paying-off the Architectural Technical Debt by refactoring the flawed code is important to control the debt and to keep it as low as possible. Project Managers tend to delay paying off this debt because they face difficulties in comparing the cost of the refactoring against the benefits they gain. …
-
Measuring affective states from architectural technical debt
… While the technological and financial aspects of technical debt have been extensively researched, the consequences on human aspects remain mostly uncharted. At the same time, recent psychoempirical software engineering research links the affects of software practitioners to organisational …
-
Managing technical debt in modern software applications
Technical Debt (TD) is a metaphor which is used to describe the software inefficiencies that are introduced in the code base as “the price to pay” for the quicker delivery of the product. In recent years TD has attracted a lot of attention from academia and industry, probably due to the ability of …
-
Technical debt : what software practitioners have to say
Technical debt is a metaphor for the consequences that software projects face when they make trade-offs to implement a lower quality, less complete solution to satisfy business realities. While interest in the metaphor is slowly gaining traction in academic research, there already exists a …
-
Towards the Repayment of Self-Admitted Technical Debt
Technical Debt is a metaphor used to express sub-optimal source code implementations that are introduced for short-term benefits that often must be paid back later, at an increased cost. In recent years, various empirical studies have focused on investigating source code comments that indicate …
-
Technical debt-aware elasticity management in cloud computing environments
… decisions. We draw inspiration from the technical debt metaphor in software engineering and we explore it in a dynamic setting to present a debt-aware elasticity management. In particular, we introduce a managerial approach that assesses the value of elasticity decisions to adapt the …
-
When-to-release Planning in Consideration of Technical Debt
… Such consequences are categorized as “technical debt”, on which “interest” (e.g. delays in implementation on sub-optimal code) have to be paid as long as the “principle” (e.g. flaws in design, documentation and implementation) is not refactored and restructured. There are multifaceted …
-
How to Manage Technical Debt in a Lean Startup
… be handled is a novel subject, the concept of technical debt has been known within the field Software Engineering for over a decade but there is very little research on how it is, or should be handled in startup contexts. This study aims to fill this void through interviewing nine startups …
-
Improving our understanding of test code: technical debt and evolution
… of test-code maintenance: self-admitted technical debt (SATD) and method-level evolution. To understand SATD in test code, comments from open-source Java projects were manually analyzed and classified into a taxonomy that includes both source-code-like and test-specific categories. The …
-
Data-driven techniques for identifying and automatically repaying technical debt
… expedite processes, developers may introduce ``technical debts'', making short-term compromises to afford ongoing development at the expense of long-term maintenance. Therefore, the introduction of technical debts is an expensive decision, thus the mitigation of technical debt is a crucial …
-
Investigating the causes of software technical debt at the architectural level
Architectural technical debt (ATD) describes the consequences of intentionally or unintentionally making architectural design decisions that compromise the internal quality of a software system. These consequences include long-term software evolution and maintenance issues that jeopardize software …
-
The Economics of Technical Debt: Venture Capital, Cybersecurity, and Engineering Quality
… studies the economic consequences of technical debt—the accumulated cost of expedient engineering decisions in a firm’s software codebase—and how external forces shape it. Using direct codebase analysis of over 80,000 monthly snapshots from 600+ open-core technology firms (2010–2025), …
-
Empirical Analysis of Hidden Technical Debt Patterns in Machine Learning Software
… were explained under the framework of "Hidden Technical Debt" (HTD) by Sculley et al. [10] by making an analogy to technical debt in traditional software. HTD patterns are due to a group of ML software practices and activities leading to the future difficulty in ML system improvements, many …
-
Identifying Technical Debt Impact on Maintenance Effort - - An Industrial Case Study
Technical Debt refers to sub-optimal solutions in software development that affect the life cycle properties of a system. Source Code Technical Debt is considered to be a problem for many software projects, as neglecting Technical Debt on actively developed software will increase the required …
Page 1 of 5