Statt 42,99 €**
37,99 €
versandkostenfrei*

inkl. MwSt.
**Früherer Preis
Sofort lieferbar
19 °P sammeln
    Broschiertes Buch

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
…mehr

Produktbeschreibung
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. Product Description
This book provides programmers with the ability to cost effectively handlecommon legacy code problems without having to go through the hugelyexpensive task of rewriting all existing code. It describes a series of practicalstrategies that developers can employ to bring their existing softwareapplications under control. The author provides useful guidance about how touse these strategies when refactoring or making functional changes to codebases. One of the book's key points is that it teaches developers to write teststhat can be used to make sure they are not unintentionally changing theapplication as they optimize it. Examples are provided in Java, C++, and Csharp,and the book assumes that the reader has some knowledge of UMLnotation. Strategies using UML and code in C++ and Java primarily whilelanguage independent advice will be delivered in side bars and appendices forlanguage specific users.

Backcover
Get more out of your legacy systems: more performance, functionality, reliability, and manageability

Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development efforts.

In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. This book draws on material Michael created for his renowned Object Mentor seminars: techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control.

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 or platform-with examples in Java, C++, C, and C#

Accurately identifying where code changes need to be made

Coping with legacy systems that aren't object-oriented

Handling applications that don't seem to have any structure

This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

© Copyright Pearson Education. All rights reserved.

Preface.

Introduction.

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.
Get more out of your legacy systems: more performance, functionality, reliability, and manageability

Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development efforts.

In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. This book draws on material Michael created for his renowned Object Mentor seminars: techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control.

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 or platform-with examples in Java, C++, C, and C#
Accurately identifying where code changes need to be made
Coping with legacy systems that aren't object-oriented
Handling applications that don't seem to have any structure
This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

© Copyright Pearson Education. All rights reserved.
  • Produktdetails
  • Robert C. Martin Series
  • Verlag: Prentice Hall Press
  • Erscheinungstermin: Oktober 2004
  • Englisch
  • Abmessung: 233mm x 179mm x 27mm
  • Gewicht: 736g
  • ISBN-13: 9780131177055
  • ISBN-10: 0131177052
  • Artikelnr.: 21059066