For Application Development Professionals

Primary Analyst Photo	Document Information	Rate this Document
	September 15, 2005 Take Careful Inventory Before Adopting Standalone Code Quality Tools by Carey Schwaber with Carl Zetie, Michael Gavin	Average: 8  (1 rating)

This is an excerpt

Executive Summary

Most development shops understand that the cost of repairing a defect increases exponentially as the application proceeds through the life cycle. But fewer shops know what they can do to identify defects early on. To improve the quality of their code even before formal testing begins, developers can perform unit testing, static analysis, performance analysis, and security testing. Full-featured integrated development environments (IDEs) include much — but not all — of the functionality that developers will need to accomplish these tasks. Shops using such IDEs will need to perform a careful inventory of their current tool sets before adopting additional code quality tools. To get the features they need, they may have to accept some degree of feature redundancy. The situation is different for developers working in Eclipse, who have both the freedom and the obligation to select their own code quality plug-ins.

This is an excerpt

Buy Risk-Free

Price: US $199

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.