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 12 of 12 for “"Self-admitted technical debt"”.
-
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 …
-
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 …
-
On the Relationship Between Self-Admitted Technical Debt and Software Quality
… in development, which has been referred to as “technical debt.” And like its financial analogue, if not carefully monitored and mediated, technical debt can compromise the very project it was intended to expedite. Several approaches have been proposed to aid developers in tracking the technical …
-
Self-Admitted Technical Debt - An Investigation from Farm to Table to Refactoring
Self-Admitted Technical Debt (SATD) is a metaphorical concept which describes the self-documented contribution of technical debt to a software project in the manner of source-code comments. SATD can linger in projects and degrade source-code quality, but its palpable visibility draws a peculiar …
-
Automated Self-Admitted Technical Debt Tracking, Classification, and Repayment for Sustainable Software Development
Self-Admitted Technical Debt (SATD), a concept that highlights sub-optimal choices in software development documented in code comments or other project resources, poses challenges to the maintainability and evolution of software systems. Recognizing the importance of managing SATD to mitigate its …
-
An empirical study on discovering a new self-admitted technical debt type - API-debt
Self-Admitted Technical Debt (SATD) is when developers intentionally choose to take short-cuts, non-optimal solutions (e.g. temporary fix or rush code development) that negatively contribute to long-term source-code quality in order to achieve short-term goals such as product deadline. Several …
-
LLM-SATD: An Empirical Study of Self-Admitted Technical Debt in Software Integrating Large Language Models
… gain first-mover advantage, developers may incur technical debt: workarounds and shortcuts that accelerate short-term delivery but make future software maintenance and evolution more difficult. Developers often acknowledge such debt in code comments, forming Self-Admitted Technical Debt (SATD). …
-
Large Language Models for Test Code Comprehension
… the rise of LLM APIs has created new forms of Self-Admitted Technical Debt (SATD) centered on prompt design, hyperparameter configurations, and framework orchestration. Objective: This dissertation systematically investigates (i) how transformer/LLM pipelines affect test quality (with a focus …
-
Prompt Engineering with Requirements in GitHub Copilot
… with more context when prompting it to repay self-admitted technical debt expressed through TODO comments. Three different prompt tem plates were created to evaluate this approach. The first template had no require ments in the prompt, the second template had some relevant requirements, and …
-
Self-admitted scientific debt: Navigating cross-domain challenges in scientific software
… disciplines. These challenges often manifest as technical debt, specifically in the form of Self-Admitted Technical Debt (SATD). While technical debt is a well-recognized issue in software engineering, its impact within scientific software remains underexplored. In particular, the integration of …
-
Improving our understanding of test code: technical debt and evolution
… two dimensions 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 …
-
Investigating Technical Debt & Post-Deployment Evolution in Ethereum Smart Contracts: A Double-Edged Sword
… bugs and deliberate compromises known as Technical Debt (TD). In this immutable context, TD poses unique risks as retroactive fixes are costly or infeasible. This thesis addresses this challenge through three interconnected studies. First, we conduct a large-scale empirical analysis of …