Dealing with Generalisation
Abstraction has its own group of refactoring techniques, primarily associated with moving functionality along the class inheritance hierarchy, creating new classes and interfaces, and replacing inheritance with delegation and vice versa.
- Pull Up Field
Problem: Two classes have the same field.
Solution: Remove the field from subclasses and move it to the superclass.
- Pull Up Method
Problem: Your subclasses have methods that perform similar work.
Solution: Make the methods identical and then move them to the relevant superclass.
- Pull Up Constructor Body
Problem: Your subclasses have constructors with code that is mostly identical.
Solution: Create a superclass constructor and move the code that is the same in the subclasses to it. Call the superclass constructor in the subclass constructors.
- Push Down Method
Problem: Is behavior implemented in a superclass used by only one (or a few) subclasses?
Solution: Move this behavior to the subclasses.
- Push Down Field
Problem: Is a field used only in a few subclasses?
Solution: Move the field to these subclasses.
- Extract Subclass
Problem: A class has features that are used only in certain cases.
Solution: Create a subclass and use it in these cases.
- Extract Superclass
Problem: You have two classes with common fields and methods.
Solution: Create a shared superclass for them and move all the identical fields and methods to it.
- Extract Interface
Problem: Multiple clients are using the same part of a class interface. Another case: part of the interface in two classes is the same.
Solution: Move this identical portion to its own interface.
- Collapse Hierarchy
Problem: You have a class hierarchy in which a subclass is practically the same as its superclass.
Solution: Merge the subclass and superclass.
- Form Template Method
Problem: Your subclasses implement algorithms that contain similar steps in the same order.
Solution: Move the algorithm structure and identical steps to a superclass, and leave implementation of the different steps in the subclasses.
- Replace Inheritance with Delegation
Problem: You have a subclass that uses only a portion of the methods of its superclass (or it's not possible to inherit superclass data).
Solution: Create a field and put a superclass object in it, delegate methods to the superclass object, and get rid of inheritance.
- Replace Delegation with Inheritance
Problem: A class contains many simple methods that delegate to all methods of another class.
Solution: Make the class a delegate inheritor, which makes the delegating methods unnecessary.
Tired of reading?
No wonder, there are 7 hours worth of the text on this website.
Try out something different. We've just launched the interactive learning course on refactoring. It has more content and much more fun than a boring text.Learn more...