Home > Store

Working Effectively with Legacy Code

Register your product to gain access to bonus material or receive a coupon.

Working Effectively with Legacy Code

Best Value Purchase

Book + eBook Bundle

  • Your Price: $73.69
  • List Price: $126.98
  • Includes EPUB and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    Adobe Reader PDF The popular standard, used most often with the free Acrobat® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

More Purchase Options

Book

  • Your Price: $51.99
  • List Price: $64.99
  • Usually ships in 24 hours.

eBook

  • Your Price: $49.59
  • List Price: $61.99
  • Includes EPUB and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    Adobe Reader PDF The popular standard, used most often with the free Acrobat® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

Description

  • Copyright 2005
  • Dimensions: 7" x 9-1/4"
  • Pages: 464
  • Edition: 1st
  • Book
  • ISBN-10: 0-13-117705-2
  • ISBN-13: 978-0-13-117705-5

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 codebases.

One of the book's key points is that it teaches developers to write tests that can be used to ensure they are not unintentionally changing the application as they optimize it. Examples are provided in Java, C++, and C#, and the book assumes that the reader has some knowledge of UML notation. Strategies using UML and code in C++ and Java are emphasized, while language-independent advice is delivered in sidebars and appendices for language-specific users.

Extras

Related Articles

Kicking the Code Monkey: Migrating Your Ancient Code for Fun and Profit

Saving Money with Legacy Data

Saving Money with Legacy Source Code

Links

Untitled Document Visit this link for more information related to this title.

Sample Content

Online Sample Chapters

Changing Software and Legacy Code

Testing Effectively With Legacy Code

Downloadable Sample Chapter

Untitled Document

Download Chapter 1 of this title.

Download Chapter 4 of this title.

Table of Contents

  • I. THE MECHANICS OF CHANGE.
  • 1. Changing Software.
  • 2. Working with Feedback.
  • 3. Sensing and Separation.
  • 4. The Seam Model.
  • 5. Tools.
  • II. CHANGING SOFTWARE.
  • 6. I Don’t Have Much Time and I Have To Change It.
  • 7. It Takes Forever To Make a Change.
  • 8. How Do I Add a Feature?
  • 9. I Can’t Get This Class into a Test Harness.
  • 10. I Can’t Run This Method into a Test Harness.
  • 11. I Need to Make a Change. What Methods Should I Test?
  • 12. I Need to Make Many Changes In One Area Do I Have To Break.
  • 13. I Need To Make a Change but I Don’t Know What Tests To Write.
  • 14. Dependencies on Libraries Are Killing Me.
  • 15. My Application Is All API Calls.
  • 16. I Don’t Understand the Code Well Enough To Change It.
  • 17. My Application Has No Structure.
  • 18. My Test Code Is in the Way.
  • 19. My Project Is Not Object-Oriented. How Do I Make Safe Changes?
  • 20. This Class Is Too Big and I Don’t Want It to Get Any Bigger.
  • 21. I’m Changing The Same Code All Over the Place.
  • 22. I Need To Change a Monster Method and I Can’t Write Tests for It.
  • 23. How Do I Know That I’m Not Breaking Anything?
  • 24. We Feel Overwhelmed. It Isn’t Going To Get Any Better.
  • III. DEPENDENCY BREAKING TECHNIQUES.
  • 25. Dependency Breaking Techniques.
  • Appendix: Refactoring.
  • Glossary.

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.