Technical Debt
Organisations that do not have mechanisms to measure the quality of code delivered by outsourcers and project teams, risk under-estimating project whole of life costs.
What is Technical Debt?
Hasty software development or cutting corners during project implementation can result in reduced code quality, and a lower quality product being delivered to production. This results in increased operational expenditure on maintenance in future years. Deferring costs for technical activities to future years is sometimes referred to as generating Technical Debt.
deferring technical activities to future years only generates a technical debt and increases your costs
Drivers of Technical Debt
Project pressures often degrade the quality of the finished product, these can include:
- profit motive or budget pressures;
- schedule pressures;
- implementation complications; and
- requests for change.
How Sanity4J can assist with reducing Technical Debt
Sanity 4J is an objective tool which can be embedded in a standard process for tracking quality,
allowing enforceable quality targets to be set and measured against. Enforcement of the Sanity4J
output reduces the Technical Debt that is created during project development: producing a higher
quality product, reducing development costs, and ongoing maintenance costs.
Sanity4J was developed to provide code quality measurement for Java code. It has been
proven on large number of Java applications as a key tool for improving application code quality.
It helps to reduce Technical Debt, lowering development and ongoing maintenance costs.
