• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Q for Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma

 
Ranch Hand
Posts: 61
1
IntelliJ IDE Tomcat Server Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What tools are usually used to measure technical debt?
 
Author
Posts: 63
6
  • Likes 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There are various dimensions of technical debt; some of the prominent dimensions are:
  • Implementation debt (Examples- code duplication, static tool rules violations, and code smells)
  • Design and architecture debt (Examples - Design smells, design rules violations, and architectural rules violations)
  • Test debt (Examples - Lack of tests, inadequate test coverage, and improper test design)
  • Documentation debt (Examples - No documentation for important concerns, poor documentation, outdated documentation)


  • There are various tools available to measure different dimensions of technical debt for different programming languages. You can find a detailed presentation about tools related to technical debt here.

    In this book, when we refer technical debt, we mean "design debt" arising mainly due to design smells.
     
    Author
    Posts: 93
    14
    • Likes 1
    • Mark post as helpful
    • send pies
      Number of slices to send:
      Optional 'thank-you' note:
    • Quote
    • Report post to moderator
    Just to add to Tushar's answer. There are many tools available that measure technical debt such as SonarQube (see http://www.sonarqube.org/evaluate-your-technical-debt-with-sonar/), CAST (see http://www.castsoftware.com/research-labs/technical-debt-estimation). But it is possible to evaluate technical debt using existing code duplication, metrics, smell detection, and architecture analysis tools that you may be already using in your projects (as mentioned by Tushar).
     
    reply
      Bookmark Topic Watch Topic
    • New Topic