Examination of tools for managing different dimensions of Technical Debt
This work helps software developers and managers in selecting tools for Technical Debt management, but it is incremental as it focuses on summarizing existing tools rather than introducing new methods.
The paper addresses the challenge of selecting appropriate tools for managing various dimensions of Technical Debt in software development, such as Code, Test, Design, Architecture, Documentation, and Environment debts, by presenting findings to reduce the time-consuming and tiring process of tool identification.
With lots of freemium and premium, open and closed source software tools that are available in the market for dealing with different activities of Technical Debt management across different dimensions, identifying the right set of tools for a specific activity and dimension can be time consuming. The new age cloud-first tools can be easier to get onboard, whereas the traditional tools involve a considerable amount of time before letting the users know what it has to offer. Also, since many tools only deal with few dimensions of Technical Debt like Code and Test debts, identifying and choosing the right tool for other dimensions like Design, Architecture, Documentation, and Environment debts can be tiring. We have tried to reduce that tiring process by presenting our findings that could help others who are getting into the field of "Technical Debt in Software Development" and subsequently further into "Technical Debt Management".