2018 IEEE/ACM International Conference on Technical Debt (TechDebt)

27 May-3 June 2018

Filter Results

Displaying Results 1 - 25 of 32
  • [Title page i]

    Publication Year: 2018, Page(s): 1
    Request permission for reuse | PDF file iconPDF (40 KB)
    Freely Available from IEEE
  • [Title page iii]

    Publication Year: 2018, Page(s): 3
    Request permission for reuse | PDF file iconPDF (96 KB)
    Freely Available from IEEE
  • Table of contents

    Publication Year: 2018, Page(s):5 - 7
    Request permission for reuse | PDF file iconPDF (117 KB)
    Freely Available from IEEE
  • Message from ICSE 2018 General Chair

    Publication Year: 2018, Page(s):8 - 10
    Request permission for reuse | PDF file iconPDF (3047 KB)
    Freely Available from IEEE
  • Message from TechDebt 2018 Chairs

    Publication Year: 2018, Page(s): 11
    Request permission for reuse | PDF file iconPDF (118 KB)
    Freely Available from IEEE
  • Organizing Committee

    Publication Year: 2018, Page(s): 12
    Request permission for reuse | PDF file iconPDF (169 KB)
    Freely Available from IEEE
  • Program Committee

    Publication Year: 2018, Page(s):13 - 14
    Request permission for reuse | PDF file iconPDF (85 KB)
    Freely Available from IEEE
  • ICSE 2018 Sponsors and Supporters

    Publication Year: 2018, Page(s): 15
    Request permission for reuse | PDF file iconPDF (1047 KB)
    Freely Available from IEEE
  • An Exploratory Study on the Influence of Developers in Technical Debt

    Publication Year: 2018, Page(s):1 - 10
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (517 KB) | HTML iconHTML

    Software systems are often developed by many developers who have a varying range of skills and habits. These developers have a big impact on software quality. Understanding how different developers and developer characteristics impact the quality of a software is crucial to properly deploy human resources and help managers improve quality outcomes which is essential for software systems success. A... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Architectural Technical Debt Identification: The Research Landscape

    Publication Year: 2018, Page(s):11 - 20
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (341 KB) | HTML iconHTML

    Architectural Technical Debt (ATD) regards sub-optimal design decisions that bring short-term benefits to the cost of long-term gradual deterioration of the quality of the architecture of a software system. The identification of ATD strongly in uences the technical and economic sustainability of software systems and is attracting growing interest in the scientific community. During the years sever... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Technical Debt as an External Software Attribute

    Publication Year: 2018, Page(s):21 - 30
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (287 KB) | HTML iconHTML

    Background: Technical debt is currently receiving increasing attention from practitioners and researchers. Several metaphors, concepts, and indications concerning technical debt have been introduced, but no agreement exists about a solid definition of technical debt. Objective: We aim at providing a solid basis to the definition of technical debt and the way it should be quantified. Method: We vie... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Prioritizing Technical Debt in Database Normalization Using Portfolio Theory and Data Quality Metrics

    Publication Year: 2018, Page(s):31 - 40
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (10318 KB) | HTML iconHTML

    Database normalization is the one of main principles for designing relational databases. The benefits of normalization can be observed through improving data quality and performance, among the other qualities. We explore a new context of technical debt manifestation, which is linked to ill-normalized databases. This debt can have long-term impact causing systematic degradation of database qualitie... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Evaluating Domain-Specific Metric Thresholds: An Empirical Study

    Publication Year: 2018, Page(s):41 - 50
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (257 KB) | HTML iconHTML

    Software metrics and thresholds provide means to quantify several quality attributes of software systems. Indeed, they have been used in a wide variety of methods and tools for detecting different sorts of technical debts, such as code smells. Unfortunately, these methods and tools do not take into account characteristics of software domains, as the intrinsic complexity of geo-localization and sci... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Introducing Debtgrep: A Tool for Fighting Technical Debt in Base Station Software

    Publication Year: 2018, Page(s):51 - 52
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (94 KB) | HTML iconHTML

    One of the biggest challenges in a large software development project is to manage technical debt. For example, if an API is replaced by a newer version and the old one is deprecated, there is a big risk that a substantial technical debt is incurred. The time where two versions of an API can co-exist can be quite long, and in a big organization like Ericsson 4G5G Baseband there can be a big challe... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Static Software Metrics for Reliability and Maintainability

    Publication Year: 2018, Page(s):53 - 54
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (270 KB) | HTML iconHTML

    This paper identifies a small, essential set of static software code metrics linked to the software product quality characteristics of reliability and maintainability and to the most commonly identified sources of technical debt. An open-source plug-in is created for the Understand code analysis tool that calculates and visualizes these metrics. The plug-in was developed as a first step in an ongo... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • AnaConDebt: A Tool to Assess and Track Technical Debt

    Publication Year: 2018, Page(s):55 - 56
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (84 KB) | HTML iconHTML

    It is challenging to assess and manage Technical Debt. Technical Debt is avoided or refactored if the long-term bene ts, such as preventing extra-costs, exceed the cost of repaying the debt. Some tools have been recently proposed for the identification of Technical Debt, but most of them do not help in assessing the cost-bene ts of repaying the Debt. Besides, it is challenging to track, visualize ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Cognitive Complexity — An Overview and Evaluation

    Publication Year: 2018, Page(s):57 - 58
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (87 KB) | HTML iconHTML

    As a measure of understandability, Cyclomatic Complexity is widely regarded as unsatisfactory, but until December 2016 it was the only one available. This paper describes Cognitive Complexity, a new metric designed specifically to measure understandability, and a brief survey of Cognitive Complexity issues in a subset of open source projects under static analysis on SonarCloud. From this analysis,... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Prioritize Technical Debt in Large-Scale Systems Using CodeScene

    Publication Year: 2018, Page(s):59 - 60
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (419 KB) | HTML iconHTML

    Large-scale systems often contain considerable amounts of code that is overly complicated, hard to understand, and hence expensive to change. An organization cannot address and refactor all of that code at once, nor should they. Ideally, actionable refactoring targets should be prioritized based on the technical debt interest rate to balance the trade-offs between improvements, risk, and new featu... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Past, Present and Future of Technical Debt: Learning from the Past to Prepare for the Future

    Publication Year: 2018, Page(s): 61
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (70 KB)

    While technical debt has emerged as a formal concept relatively recently we have had technical debt from the earliest days of software development, it has simply evolved in nature. So what can we learn from past types of technical debt to allow us to prepare for its future forms? When we look back over recent software history, we can see identifiable evolutions of software systems, each one roughl... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Developer's Dilemma: Factors Affecting the Decision to Repay Code Debt

    Publication Year: 2018, Page(s):62 - 66
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (215 KB) | HTML iconHTML

    The set of concepts collectively known as Technical Debt (TD) assume that software liabilities set up a context that can make a future change more costly or impossible; and therefore repaying the debt should be pursued. However, software developers often disagree with an automatically generated list of improvement suggestions, which they consider not fitting or important for their own code. To she... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • From Lasagna to Spaghetti: A Decision Model to Manage Defect Debt

    Publication Year: 2018, Page(s):67 - 71
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (257 KB) | HTML iconHTML

    In this paper, we propose a model that formalizes the role of software evolution in characterizing Technical Debt (TD) by defining a series of software product states, where each successive state represents an increased level of maintenance code churn, and thus presumably an increased level of change difficulty. We also propose a way to use these states to estimate TD principal and interest and us... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A Proposed Sizing Model for Managing 3rd Party Code Technical Debt

    Publication Year: 2018, Page(s):72 - 75
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (216 KB) | HTML iconHTML

    Commercial software development projects frequently build code on third-party components. However, depending on third-party code requires that projects keep current with the latest version of each component. When projects do not stay current, they begin to incur a form of technical debt where API calls that have been deprecated remain in the code base. At some point, projects must upgrade the thir... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Governing Technology Debt: Beyond Technical Debt

    Publication Year: 2018, Page(s):76 - 84
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (346 KB) | HTML iconHTML

    Technical debt has successfully captured the interest of practitioners and researchers alike. We argue that the concept of technical debt holds much more currency within the strategic Information Systems literature. Hence, we have developed a research framework for expanding the concept of technical debt into a new concept we dub “technology debt”. This expanded concept aims at capturing the path-... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Trade-Off Decisions across Time in Technical Debt Management: A Systematic Literature Review

    Publication Year: 2018, Page(s):85 - 94
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (330 KB) | HTML iconHTML

    Technical Debt arises from decisions that favour short-term outcomes at the cost of longer-term disadvantages. They may be taken knowingly or based on missing or incomplete awareness of the costs; they are taken in different roles, situations, stages and ways. Whatever technical or business factor motivate such decisions, they always imply a trade-off in time, a 'now vs. later'. How exactly are su... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Design Debt Prioritization: A Design Best Practice-Based Approach

    Publication Year: 2018, Page(s):95 - 104
    Request permission for reuse | Click to expandAbstract | PDF file iconPDF (330 KB) | HTML iconHTML

    Technical debt (TD) in a software system is a metaphor that tries to illustrate the remediation effort of the already introduced quality deficit and the impact thereof to the business value of the system. To address TD, various management activities are proposed, each addressing a particular purpose. Whereas the activities of debt identification and measurement are broadly considered in literature... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.