Technical Debt: Identify, Measure and Monitor
Nikhil Oswal

TL;DR
This paper discusses methods to identify, measure, and monitor technical debt in software projects, emphasizing the use of tools like SonarQube and PMD to manage maintainability and support continuous delivery.
Contribution
It introduces practical techniques and tools for effectively managing technical debt, focusing on identification, measurement, and ongoing monitoring.
Findings
Effective use of SonarQube and PMD for technical debt management
Techniques enable timely repayment of debt to reduce costs
Monitoring supports sustainable software development
Abstract
Technical Debt is a term begat by Ward Cunningham to signify the measure of adjust required to put a software into that state which it ought to have had from the earliest starting point. Often organizations need to support continuous and fast delivery of customer value both in short and a long-term perspective and later have to compromise with the quality and productivity of the software. So, a simple solution could be to repay the debts as and when they are encountered to avoid maintainability cost and subsequent delays. Therefore, it has become inevitable to identify and come up with techniques so as to know when, what and how TD items to repay. This study aims to explore how to identify, measure and monitor technical debt using SonarQube and PMD.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSoftware Engineering Research · Software Engineering Techniques and Practices · Big Data and Business Intelligence
