Refactoring Improving the Design of Existing Code

BookInfo

ISBN: 9780201485677	Number of Pages: 464
Publisher: Pearson Education The Limited	Book Title: Refactoring: Improving the Design of Existing Code
Publication Year: 1999	Target Audience: Scholarly & Professional
Author: Martin Fowler	Format: Hardcover

Abstract

The Book Refactoring Improving the Design of Existing Code is Immortal classics of software development,it explain the principles and specific methods of reconfiguration vividly

Refactoring, in a word, is to improve the code methodically without changing the external behavior. Many years ago, it was the publication of the original edition of this book that made refactoring finally come out of the small circle of programmers and become an indispensable part of the daily development work of many ordinary programmers.

As a result, this book has become a classic with the same name as design mode. It has been translated into many languages such as Chinese, Germany, Russia and Japan, and has been selling well all over the world.

Refactoring Improving the Design of Existing Code clearly reveals the process of refactoring, explains the principle and practice of refactoring, and gives where and when to start mining code for improvement.

The book gives more than 70 feasible refactorings, each of which introduces the motivation and technology of a proven code transformation technique. The refactoring guidelines proposed in refactoring to improve the design of existing code will help you modify your code one step at a time, thus reducing the risks in the development process.

About the Author

Martin Fowler, who received his Ph.D. from Yale University, is a world famous software development expert. He made outstanding contributions in the fields of Object-Oriented analysis and design, UML, patterns, XP and refactoring. He is now the Chief Scientist of ThoughtWorks, a software development consulting company. Many of his works, such as Analysis Pattern, UML essence and Enterprise Application Architecture Pattern have become popular classics.

Other participants：
Kent Beck is a leading authority in software development, He is also the founder of extreme programming. He is the president of three rivers Institute and a member of agitar software.

John Brant and Don Roberts, founder of the refactory company, refactoring browser. For many years, he has been engaged in researching the practice and theory of refactoring.

William Opdyke currently works at lucent Bell Laboratories. His doctoral thesis on Object-Oriented Framework is the first famous article on refactoring.

Refactoring Improving the Design of Existing Code  PDF version is avaliable Later ,Please come back soon.

Table of Contents

1. Refactoring, a First Example.

• The Starting Point.
• The First Step in Refactoring.
• Decomposing and Redistributing the Statement Method.
• Replacing the Conditional Logic on Price Code with Polymorphism.
• Final Thoughts.

2. Principles in Refactoring.

• Defining Refactoring.
• Why Should You Refactor?
• When Should You Refactor?
• What Do I Tell My Manager?
• Problems with Refactoring.
• Refactoring and Design.
• Refactoring and Performance.
• Where Did Refactoring Come From?

3. Bad Smells in Code.

• Duplicated Code.
• Long Method.
• Large Class.
• Long Parameter List.
• Divergent Change.
• Shotgun Surgery.
• Feature Envy.
• Data Clumps.
• Primitive Obsession.
• Switch Statements.
• Parallel Inheritance Hierarchies.
• Lazy Class.
• Speculative Generality.
• Temporary Field.
• Message Chains.
• Middle Man.
• Inappropriate Intimacy.
• Alternative Classes with Different Interfaces.
• Incomplete Library Class.
• Data Class.
• Refused Bequest.
• Comments.

4. Building Tests.

• The Value of Self-testing Code.
• The JUnit Testing Framework.
• Adding More Tests.

5. Toward a Catalog of Refactorings.

• Format of the Refactorings.
• Finding References.
• How Mature Are These Refactorings?

6. Composing Methods.

• Extract Method.
• Inline Method.
• Inline Temp.
• Replace Temp with Query.
• Introduce Explaining Variable.
• Split Temporary Variable.
• Remove Assignments to Parameters.
• Replace Method with Method Object.
• Substitute Algorithm.

7. Moving Features Between Objects.

• Move Method. Move Field.
• Extract Class.
• Inline Class.
• Hide Delegate.
• Remove Middle Man.
• Introduce Foreign Method.
• Introduce Local Extension.

8. Organizing Data.

• Self Encapsulate Field.
• Replace Data Value with Object.
• Change Value to Reference.
• Change Reference to Value.
• Replace Array with Object.
• Duplicate Observed Data.
• Change Unidirectional Association to Bidirectional.
• Change Bidirectional Association to Unidirectional.
• Replace Magic Number with Symbolic Constant.
• Encapsulate Field.
• Encapsulate Collection.
• Replace Record with Data Class.
• Replace Type Code with Class.
• Replace Type Code with Subclasses.
• Replace Type Code with State/Strategy.
• Replace Subclass with Fields.

9. Simplifying Conditional Expressions.

• Decompose Conditional.
• Consolidate Conditional Expression.
• Consolidate Duplicate Conditional Fragments.
• Remove Control Flag.
• Replace Nested Conditional with Guard Clauses.
• Replace Conditional with Polymorphism.
• Introduce Null Object.
• Introduce Assertion.

10. Making Method Calls Simpler.

• Rename Method.
• Add Parameter.
• Remove Parameter.
• Separate Query from Modifier.
• Parameterize Method.
• Replace Parameter with Explicit Methods.
• Preserve Whole Object.
• Replace Parameter with Method.
• Introduce Parameter Object.
• Remove Setting Method.
• Hide Method.
• Replace Constructor with Factory Method.
• Encapsulate Downcast.
• Replace Error Code with Exception.
• Replace Exception with Test.

11. Dealing with Generalization.

• Pull Up Field. Pull Up Method.
• Pull Up Constructor Body.
• Push Down Method.
• Push Down Field.
• Extract Subclass.
• Extract Superclass.
• Extract Interface.
• Collapse Hierarchy.
• Form Template Method.
• Replace Inheritance with Delegation.
• Replace Delegation with Inheritance.

12. Big Refactorings.

• Tease Apart Inheritance.
• Convert Procedural Design to Objects.
• Separate Domain from Presentation.
• Extract Hierarchy.

13. Refactoring, Reuse, and Reality.

• A Reality Check.
• Why Are Developers Reluctant to Refactor Their Programs?
• A Reality Check (Revisited).
• Resources and References for Refactoring.
• Implications Regarding Software Reuse and Technology Transfer.
• A Final Note. References.

14. Refactoring Tools.

• Refactoring with a Tool.
• Technical Criteria for a Refactoring Tool.
• Practical Criteria for a Refactoring Tool.
• Wrap Up.

15. Putting It All Together.

• References.
• List of Soundbites.
• List of Refactorings.