Length: 4 pages  
Carey Schwaber September 15, 2005
Take Careful Inventory Before Adopting Standalone Code Quality Tools
by Carey Schwaber
with Carl Zetie, Michael Gavin


This is a document excerptEXECUTIVE 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.

Find Documents In Related Categories

This document falls under the following categories. Click on a link below to find similar documents.
Analyst: Carey Schwaber
Technology: Application Development, Application Development Processes & Tools
Geography: Asia Pacific, Europe, North America

Buy Risk Free
Download and print PDF immediately
Price: US $49.00

Add to Cart

Our Money-Back Guarantee
If you are not completely satisfied, return it for a full refund within three weeks of your online purchase.

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

Archived Teleconference:
Best And Next Practices In Release Management
Original air date: Wednesday, June 18, 2008
corner border corner
Ratings and Comments
NOT YET RATED
Be the first to rate
corner border corner