Capers Jones, the internationally recognized expert on software engineering, shares his latest insights in his new book from McGraw-Hill, Software Engineering Best Practices. In this book he provides definitive evidence that:

	One of the best proven ways to maintain quality and reduce defects in your software code is to take advantage of automated static analysis tools.		"Formal inspections coupled with the static analysis and formal testing tools like those found in CodePro Analytix and others, can result in defect removal rates in excess of 98%. This high level of defect removal efficiency can result in 20% less development costs, 15% shorter schedules and a potential 40% reduction in annual maintenance costs over identical projects with poor quality." – T. Capers Jones 2009
	The ability to catch and fix defects early in the development process can result in an increase in return on investment in excess of 50% over finding the same defects during system test. The really significant benefits to early testing using static analysis tools can result in a combined ROI of 600% due to accelerated schedules from reduced testing and repair in the later stages of a project.
	Most forms of testing are less than 35% efficient in finding bugs or defects. However, when combined, formal inspections and static code analysis are more than 85% efficient in finding bugs or defects and sometimes top 98%.

Capers has an important message for all serious software professionals. You will definitely want to add his new must-have book to your technical library. In fact, if you talk to us about how to tune up your software quality processes and maximize the efficiency and productivity of your development teams, we’ll give you a free copy of Caper’s book.

Like Capers, Instantiations has built an international reputation for helping software engineers deliver the highest quality code possible. Our expertise is delivered in both our world-class consulting services and through our popular CodePro AnalytiX product line. Call or email us before December 31, 2009 and let’s explore how Instantiations’ professional services and award-winning products can help make 2010 the year your software projects reach new levels of quality, reliability, and maintainability.

Click here for more information.

On October 6, Instantiations released GWT Designer v7.2 with new support for the Ext GWT widget library and GWT 1.7. Updates to the entire Eclipse-based product line followed on October 20, featuring extensive enhancements to WindowTester Pro and WindowBuilder Pro, as well as all component products. We are committed to providing these regular updates to advance our solutions and to provide continued value to our customers with active Support and Maintenance contracts.

Highlights of the October 6 and October 20 releases include:

Highlights of the October 20th Java releases include extensive improvements in WindowTester Pro and the entire WindowBuilder Pro suite. One of the most popular enhancements is comprehensive support for the Ext GWT widget library, now available in GWT Designer.

For you seasoned vets already experienced with GWT and GWT Designer, that is probably all you need to hear to send you on your way to check it out. For those of you just making your first foray into rich Internet applications, let me provide some insight. The Ext GWT widget library is made by the same folks who created the Ext JS library. When Google created GWT to make dynamic web applications more accessible to developers, the immediate request was that the Ext library be made available within the new technology. As that transition took place, developers turned to Instantiations’ GWT Designer and demanded access to this powerful set of widgets from within the designer they were already using!

And there you have it. GWT Designer v7.2 comes with extensive support for the Ext GWT widget library. This translates to:

If you would like a FREE full-featured evaluation of GWT Designer, download it here.

You can download the latest Ext GWT (GXT) update here and access the Ext GWT (GXT) docs here.

To configure your project to use Ext GWT (GXT), you can either follow the instructions in the setup.txt file in the Ext GWT download, or you can select your GWT module file and right-click to select the Google Web Toolkit > Configure for using Ext GWT (GXT) command. This will add the gxt.jar to your classpath and module file and various GXT files to your war folder.

After you try it, drop me a note and let me know what you think! You can reach me here.