Minimizing technical debt: developer's viewpoint

Krishna, Vinay; Basu, Anirban

doi:10.1049/ic.2012.0147

Cited by 7 publications

(2 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Power [13] reported on how historical data in a large technology company can be used to quantify TD, track team's debt, and finally visualize the results of this historical analysis. Krishna and Basu [11] analyzed a codebase to explore methods for relief from TD and provided 13 steps for developers to reduce their projects' debt. Al Mamun et al [1] described a study where software developers were asked via interview and questionnaire to identify the important issues related to the development process that need to be adapted to reduce the existing technical debt for teams.…”

Section: Empirical Studies Assessing Technical Debt In Industrial Conmentioning

confidence: 99%

Understanding the impact of technical debt in coding and testing

Abad

Karimpour

et al. 2016

Proceedings of the 3rd International Workshop on Software Engineering Research and Industrial Practice

View full text Add to dashboard Cite

Technical Debt (TD) refers to the long-term consequences of shortcuts taken during different phases of software development life cycle. Lack of attention to monitoring and managing testing and development debt can contribute to unexpectedly large cost overruns and severe quality issues in software development projects. This paper describes a case study conducted with an industry partner to explore the impact of TD in coding and testing. By conducting (i) a semistructured interview, and (ii) a quantitative survey, we found that (1) the status of TD is largely project-independent, (2) we could not reject that there is no significant difference between the percentage of existing TD and the required time for reducing this TD in testing and development teams, (3) there is a statistically significant difference between the perceived influence of reducing TD on productivity increase in testing and development teams, (4) team member's experience has impact on the existing percentage of TD and influences productivity increase that is caused by reducing TD, (5) allocating more resources such as time, budget, and infrastructure is considered a potential solution for reducing TD.

show abstract

Section: Empirical Studies Assessing Technical Debt In Industrial Conmentioning

confidence: 99%

Understanding the impact of technical debt in coding and testing

Abad

Karimpour

et al. 2016

Proceedings of the 3rd International Workshop on Software Engineering Research and Industrial Practice

View full text Add to dashboard Cite

show abstract

“…Implementing the practices proposed in this paper require discipline and strict adherence to defined practices. The prescribed practices were implemented in real life software projects and initial results have been presented in [3]. Since then the techniques have been implemented in more projects and data collected shows that the proposed techniques can substantially reduce the Technical Debt.…”

Section: Introductionmentioning

confidence: 99%

A Systematic Method to Evaluate the Software Engineering Practices for Minimizing Technical Debt

Krishna¹,

Basu²

2015

IJCA

View full text Add to dashboard Cite

Often we find it difficult to incorporate any changes in a software project during later phases of its development, or during post-delivery maintenance. Primary reason for this is inflexibility in design and code which makes it difficult for changes to be incorporated. This inflexibility substantially increases the cost of making changes and this metaphor has been termed as Technical Debt [1]. While Technical Debt cannot be eliminated completely, its burden needs to be reduced. Many practitioners, especially from agile community, have suggested some practices to avoid or eliminate Technical Debt. This paper discusses on a systematic method to evaluate the six software engineering practices that a developer can follow to minimize Technical Debt. These practices have been used and found to be effective when implemented in projects as discussed here.

show abstract

The Nature of Technical Debt in the Development of Descriptive Models for MBSE

Noguchi

2024

INCOSE International Symp

View full text Add to dashboard Cite

Model‐Based Systems Engineering (MBSE) is the growing practice of systems engineering (SE) in which descriptive models replace documents as the embodiment of SE knowledge. These descriptive models capture SE information in place of documents, are developed in a similar manner to software source code, and are encoded and used in machine‐to‐machine applications as data. This paper describes how the Technical Debt concept widely used in the software domain—rework deferred to the future for expediency—needs to be modified for the domain of descriptive models. Technical Debt is often associated with agile development practices of software or descriptive models, which emphasize the rapid creation and iterative evolution of a Minimum Viable Product (MVP). Consciously applying appropriate modeling principles and practices is essential to make informed decisions during the modeling process to prevent the accumulation of excessive model Technical Debt—particularly during this iterative evolutionary process—which can require substantial rework to correct. The paper establishes a foundation for characterizing the Technical Debt implications of key model architecture and implementation decisions that are made explicitly or implicitly by modelers when developing descriptive models. To illustrate the model Technical Debt concept, several examples of modeling principles pertaining to model purpose and implementation are described along with their implications on model Technical Debt.

show abstract

Minimizing technical debt: developer's viewpoint

Cited by 7 publications

References 3 publications

Understanding the impact of technical debt in coding and testing

Understanding the impact of technical debt in coding and testing

A Systematic Method to Evaluate the Software Engineering Practices for Minimizing Technical Debt

The Nature of Technical Debt in the Development of Descriptive Models for MBSE

Contact Info

Product

Resources

About