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 11 of 11 for “"Technical debt"”.

  1. Business-driven technical debt prioritization

    brazil-ufrn Repository record for Business-driven technical debt prioritization (opens in a new tab)

  2. Technical debt : the cost of doing nothing

    … concept of product health is largely ignored. Technical debt - the consequence of making short-term design decisions at the expense of long-term health - has been accumulating within code bases as developers and managers struggle to identify, quantify, and manage it properly. In this thesis, an …

    mit Repository record for Technical debt : the cost of doing nothing (opens in a new tab)

  3. 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 …

    queens Repository record for Automated Self-Admitted Technical Debt Tracking, Classification, and Repayment for Sustainable Software Development (opens in a new tab)

  4. Hitting the Bullseye: The Influence of Technical Debt on the Accuracy of Effort Estimation in Agile Projects

    … may be implemented. These shortcuts represent “technical debt,” a metaphor which succinctly describes a software solution that should be “paid in full” or remediated in the future. Software architects and developers intend to resolve the “debt” in future product releases, but practitioners …

    mississippi Repository record for Hitting the Bullseye: The Influence of Technical Debt on the Accuracy of Effort Estimation in Agile Projects (opens in a new tab)

  5. Empirical analysis of software refactoring motivation and effects

    As complexity and levels of technical debt within software systems increase over time the incentive of an organization to refactor legacy software likewise increases. However, the opportunity cost of such refactoring in terms of engineering time and monetary investment have proven difficult to …

    mit Repository record for Empirical analysis of software refactoring motivation and effects (opens in a new tab)

  6. An empirical study on software quality : developer perception of quality, metrics, and visualizations

    … during the lifetime of a software product, its technical debt can be held in check, reducing total cost of ownership. The measurement of quality faces challenges due to disagreement in the meaning of software quality, the inability to directly measure quality factors, and the lack of measurement …

    texas Repository record for An empirical study on software quality : developer perception of quality, metrics, and visualizations (opens in a new tab)

  7. Characterising Algorithm Debt in Machine and Deep Learning Systems

    … challenges, often due to design choices, lead to Technical Debt (TD). Algorithm Debt (AD) in ML/DL systems is a TD type caused by inefficient algorithmic decisions, leading to poor scalability and model degradation. Despite its impact, AD remains underexplored in ML/DL systems due to its novelty, …

    aus-cath Repository record for Characterising Algorithm Debt in Machine and Deep Learning Systems (opens in a new tab)

  8. Characterising Algorithm Debt in Machine and Deep Learning Systems

    … challenges, often due to design choices, lead to Technical Debt (TD). Algorithm Debt (AD) in ML/DL systems is a TD type caused by inefficient algorithmic decisions, leading to poor scalability and model degradation. Despite its impact, AD remains underexplored in ML/DL systems due to its novelty, …

    anu Repository record for Characterising Algorithm Debt in Machine and Deep Learning Systems (opens in a new tab)

  9. Investigating the frustrations in managing and engineering defense system-of systems

    … A total of twelve common themes were observed: Technical Challenges: 1) Poor Requirements Engineering, 2) High Complexity and Magnitude of SoS, 3) Complex Stakeholder Management, 4) Evolving SoS Requirements. Management 'Pain Points': 5) Lack of Strong Leadership, 6) Misalignment between …

    mit Repository record for Investigating the frustrations in managing and engineering defense system-of systems (opens in a new tab)

  10. IntelliCode Review: An AI-Powered Platform for Automated Code Quality Analysis with Actionable Feedback

    … code clones, refactoring suggestions, dead code, technical debt, documentation coverage, performance hotspots, dependency coupling, and readability. Four of the twelve dimensions use trained machine learning models; the other eight are deterministic AST analysers. The deterministic modules are …

    unr Repository record for IntelliCode Review: An AI-Powered Platform for Automated Code Quality Analysis with Actionable Feedback (opens in a new tab)

  11. Proactive Software Complexity Assessment

    Large software development companies primarily deliver value to their customers by continuously enhancing the functionality of their products. Continuously developing software for customers insures the enduring success of a company. In continuous development, however, software complexity tends to …

    goteborg Repository record for Proactive Software Complexity Assessment (opens in a new tab)