Annotatie

The topics covered include: understanding the mechanics of software change: adding features, fixing bugs, improving design, optimizing performance; getting legacy code into a test harness; writing tests that protect you against introducing new problems; techniques that can be used with any language

Flaptekst

Proven strategies for maintaining and optimizing legacy code to get the most out of your existing applications. - Examples in C-sharp, C++, and Java, as well as strategies for better using the industry standard modeling language: UML 2.0 - Addresses the very concrete problems that programmers face working in the context of large untested code bases - Based on successful classes for Object Mentor, the author helps organizations maintain older systems rather than go to the cost of developing new ones This book provides programmers with the ability to cost effectively handle common legacy code problems without having to go through the hugely expensive task of rewriting all existing code. It describes a series of practical strategies that developers can employ to bring their existing software applications under control. The author provides useful guidance about how to use these strategies when refactoring or making functional changes to code bases. One of the book's key points is that it teaches developers to write tests that can be used to make sure they are not unintentionally changing the application as they optimize it. Examples are provided in Java, C++, and Csharp, and the book assumes that the reader has some knowledge of UML notation. Strategies using UML and code in C++ and Java primarily while language independent advice will be delivered in side bars and appendices for language specific users.