The paper examines the company’s proprietary means for determining the quality of a software product and measuring its technical debt. The paper's authors explain how a software product's quality is directly correlated with the amount of varying technical debts that the end-users receive. All debts can be paid, and technical debt is no exception: one can use various parameters, techniques, and dimensions to effectively measure and optimize the quality of a software product. The authors share information about the company’s proprietary method to technical debt management, which is done via the Technical dEbT Reduction plAtform, otherwise known as TETRA™. They give details about the assessment's major dimensions, tools, and measurement p
