CSC/ECE 517 Fall 2009/wiki1a 8 nd: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
 
(134 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Problem Statement=
='''Problem Statement'''=


The list of refactorings has become quite long.  But people don't remember long lists very well.  To promote learning the different patterns, they should be categorized in some way, or perhaps, along various dimensions. As a reference we have taken the list of refactorings available [http://www.refactoring.com/catalog/index.html here] and categorized them along as many different dimensions as makes sense.
The list of refactorings has become quite long & people don't remember long lists very well.  To promote learning the different patterns, they should be categorized in some way, or perhaps, along various dimensions.Here is an attempt to categorize the various available refactoring methods into different categories along as many different dimensions as makes sense. As a reference we have taken the list of refactorings methods available at http://www.refactoring.com/catalog/index.html.


='''Categorization of Refactoring Methods'''=
=='''Categorization Framework Used'''==
When an application is developed using an object oriented programming language the code architecture is designed in the following way. First the functionality of the application is divided into major chunks and assigned to sets of packages which form the first level of hierarchy for the program.


Here are the categories & sub-categories using which the refactorings available [http://www.refactoring.com/catalog/index.html here] have been categorized.
The second level of hierarchy is the compilation unit which has access to all public types declared in its package and also automatically imports them. Types consist of classes and interfaces.  


=Package=
The functionality implemented in a package is further broken down and implemented using classes at the third level of hierarchy. Classes are made out of items, which are basically methods and fields. Fields declare data which are associated with the class.Interfaces encode the similarities among classes.
*Extract Package
*Move Class


The fourth level of hierarchy consists of objects which act as data structures and store data associated with the class. This helps to store multiple values of the same type of data.


At the lowest level i.e the fifth is the data, which is a part of the object. At this level, the code which is a part of the method processes this data.


=Class=
This hierarchy is followed during any application development using an object oriented language and when an analyst is asked to refactor code, he/she also parses through this same hierarchy to understand the code functionality and to find spots where the code can be refactored.


**'''Changing Class Association'''         
Most of the refactoring methods belong to level 3, level 4 and level 5, hence these categories have again been divided into sub-categories, to reduce generalization & make the categorization more specific. Here is an attempt to make categorization of the refactoring methods based on the said hierarchy. Also there are a few categories which aren't derived from the above hierarchy. Here are the categories and sub-categories using which the refactoring methods available at http://www.refactoring.com/catalog/index.html have been categorized.
***Change Unidirectional Association to Bidirectional
***Change Unidirectional Association to Bidirectional


**'''Change of Class Structure'''
=='''Categories'''==
***Collapse Hierarchy
===Refactoring the Package===
***Duplicate Observed Data
A refactoring method will fall under this category if the changes made affect the package structure or add to the functionality to the package. The refactoring method generally may involve breaking a package to smaller packages to divide the functionality or moving classes to a more relevant package.
***Extract Class
*Extract Package
***Extract SubClass
*Move Class
***Extract SuperClass
***Inline Class
***Replace Subclass with Fields
***Separate Data Access Code


**'''Addition to a Class'''
===Refactoring the Class===
***Pull up Constructor Body
***Pull up Field
***Pull up Method
***Push Down Field
***Push Down Method


=Method=
*'''Changing Class Association'''
A refactoring method falls in this category if it tries to change the association between two classes so that features of a class may be added or removed.
*Change Unidirectional Association to Bidirectional
*Change Bidirectional  Association to Unidirectional
*Extract Interface


**'''Meaningful and Detailed Method Calls'''
*'''Change of Class Structure''' A refactoring method falls in this category when it tries to change the hierarchy that the classes share amongst them.
***Add Parameter
**Splitting of Class
***Rename Method
*Duplicate Observed Data
***Preserve Whole Object
*Extract Class
*Extract SubClass
*Extract SuperClass
*Separate Data Access Code
*Localize Disparate Logic
**Merging of  Class
*Collapse Hierarchy
*Replace Subclass with Fields
*Inline Class


**'''Change of Structure of the Method Code'''
*'''Inter-Class Movement of Items'''
***Extract Method
A refactoring method falls in this category when it tries to move functionality/detail between classes. This may involve movement of constructors, fields or methods between classes.
***Inline Method
*Pull up Constructor Body
***Consolidate Conditional Expression
*Pull up Field
***Encapsulation Collection
*Pull up Method
***Form Template Method
*Push Down Field
***Replace Nested Conditional with Guard Clauses
*Push Down Method
***Replace Parameter with Method
*Move Field
*Move Method
*'''Moving Additional Functionality to Client Class'''
A refactoring method falls in this category when functionality needs to be added to a server class which cannot be altered. The refactoring method achieves it by adding sever class extensions to the client method.
*Introduce Local Extension 
*Introduce Foreign Method


**'''Change Method Call Hierarchy'''
*'''Replacement of Class Instantiation with Constructors'''
***Remove Middle man
A refactoring method falls in this category when it tries to convert loading of some of the classes from dynamic to static or vice-versa.
***Replace Delegation with Inheritance
***Replace Inheritance with Delegation


**'''Improve Method Readability'''
*Convert Static to Dynamic Construction
***Introduce Explaining Variable
*Convert Dynamic to Static Construction
***Replace Magic No with Symbolic Constant
***Split Temporary Variable


**'''Method Code Refactoring based on Method Arguments'''
===Refactoring the Method===
***Replace Conditional with Polymorphism
***Replace Conditional with Visitor
***Replace Parameter with Explicit Methods


*'''Meaningful and Detailed Method Calls'''
A refactoring method will fall under this category if it modifies a method call to pass more data to the method or tries to make the method call more understandable.
*Add Parameter
*Preserve Whole Object
*Rename Method


*'''Change of Structure of the Method Code'''
A refactoring method will fall under this category if it deliberately changes the internal flow of the code without affecting the output. These methods need not result in the optimization of the code or simplification.
*Consolidate Conditional Expression
*Encapsulation Collection
*Extract Method
*Inline Method
*Form Template Method
*Replace Nested Conditional with Guard Clauses
*Replace Parameter with Method


=Object=
*'''Change Method Call Hierarchy/Sequence'''
A refactoring method will fall in this category when it tries to change the method call flow in any way.
*Remove Middle man
*Replace Delegation with Inheritance
*Replace Inheritance with Delegation


**'''Replacements with Objects'''
*'''Improve Method Readability'''
***Introduce Null Object
A refactoring method will fall under this category when it increases the readability of the code for a new person reading the code or for debugging purpose if ever needed.
***Replace Array with Object
*Introduce Explaining Variable
***Introduce Parameter Object
*Replace Magic No with Symbolic Constant
***Replace Data Value with Object
*Replace Recursion with Iteration
***Replace Method with Method Object
*Split Temporary Variable


**'''Object Initialization'''
*'''Method Code Refactoring based on Method Arguments'''
***Replace Constructor with Factory Method
A refactoring method will fall under this category when it makes the behavior of the executed method code, change depending on the argument passed, or when it frees the method code of this feature.
*Parameterize Method
*Replace Conditional with Polymorphism
*Replace Conditional with Visitor
*Replace Parameter with Explicit Methods


**'''Accessing the Object/Data'''
===Refactoring the Object===
***Change Reference to Value
***Change Value to Reference
***Refactor Architecture by Tiers
***Self Encapsulate Field


*'''Replacements with Objects'''
A refactory method will fall under this category when the code is changed such that its execution is more centered around the object. And different parameters like array, data values are replaced by objects.
*Introduce Null Object
*Introduce Parameter Object
*Replace Array with Object
*Replace Data Value with Object
*Replace Method with Method Object
*Replace Record with Data Class


*'''Object Initialization'''
A refactory method will fall under this category when it tries to alter the constructor used for the initialization of the object.
*Replace Constructor with Factory Method
*Remove Setting Method


=Code=
*'''Accessing the Object/Data'''
A refactory method will fall under this category if the method changes the way an object or data is accessed.
*Change Reference to Value
*Change Value to Reference
*Refactor Architecture by Tiers
*Self Encapsulate Field


**'''Code Optimization'''
===Refactoring the Code===
***Replace Temp with Query
***Consolidate Duplicate Conditional Fragments
***Decompose Conditional
***Inline Temp
***Introduce Assertion
***Replace Iteration with Recursion
***Remove Control Flag


**'''Redundant Code Elimination'''
*'''Code Optimization'''
***Parametrize Method
A refactoring method will fall under this category when the method brings about change in the code such a way that its execution is optimized.
***Remove Parameter
*Consolidate Duplicate Conditional Fragments
*Eliminate Inter-Entity Bean Communication
*Inline Temp
*Remove Control Flag
*Replace Iteration with Recursion
*Replace Temp with Query
*Use a Connection Pool


**'''Method Code Simplification'''
*'''Code Reliability Improvement'''
***Remove Double Negative
A refactoring method will fall under this category if it helps to make the code less prone to errors and adhere more to its intended functionality.
***Replace Assignment with Initialization
*Introduce Assertion
***Encapsulate Downcast
*Introduce A Controller
***Reduce Scope of Variable
*Introduce Synchronizer Token
***Reverse Conditional
*Reduce Scope of Variable
***Separate Query from Modifier
*Remove Assignments to Parameters
***Split Loop
***Substitute Algorithm


**'''"Removal of "Type Code"'''
*'''Code Simplification'''
***Replace Type Code with Class
A refactoring method will fall under this category when it causes simplification of the code making it more readable and understandable, it may or may not optimize the execution.
***Replace Type Code with State/Strategy
*Encapsulate Downcast
***Replace Type Code with Subclasses
*Remove Double Negative
*Replace Assignment with Initialization
*Reverse Conditional
*Separate Query from Modifier
*Split Loop
*Substitute Algorithm
*Decompose Conditional


*'''Redundant Code Elimination'''
A refactoring method will fall under this category if it helps to eliminate the unnecessary code
and makes the code cleaner.
*Parametrize Method
*Remove Parameter


*'''Removal of "Type Code"'''
A refactory method will fall under the category Removal of  "Type Code" if the method helps to remove the type code.
*Replace Type Code with Class
*Replace Type Code with State/Strategy
*Replace Type Code with Subclasses


=Refactoring for Privacy=
===Refactoring for Privacy===
**Hide Delegate
A refactoring method will fall under this category if it helps in data protection and privacy.
**Hide Method
*Encapsulate Field
**Encapsulate Field
*Hide Delegate
**Hide Presentation Tier-Specific Details from the Business tier
*Hide Method
**Introduce Business Delegate
*Hide Presentation Tier-Specific Details from the Business tier
**Wrap Entities with Session
*Introduce Business Delegate
*Wrap Entities with Session


 
===Dealing with Exceptions===
 
A refactoring method will fall under this category if it optimizes the way the code handles an exception situation.
=Dealing with Exceptions=
*Remove Error Code with Exception
**Remove Error Code with Exception
*Replace Exception with Test
**Replace Exception with Test


=References=
=References=
http://www.refactoring.com<br>
Refactoring: Improving the Design of Existing Code by Martin Fowler.

Latest revision as of 14:39, 11 September 2009

Problem Statement

The list of refactorings has become quite long & people don't remember long lists very well. To promote learning the different patterns, they should be categorized in some way, or perhaps, along various dimensions.Here is an attempt to categorize the various available refactoring methods into different categories along as many different dimensions as makes sense. As a reference we have taken the list of refactorings methods available at http://www.refactoring.com/catalog/index.html.

Categorization of Refactoring Methods

Categorization Framework Used

When an application is developed using an object oriented programming language the code architecture is designed in the following way. First the functionality of the application is divided into major chunks and assigned to sets of packages which form the first level of hierarchy for the program.

The second level of hierarchy is the compilation unit which has access to all public types declared in its package and also automatically imports them. Types consist of classes and interfaces.

The functionality implemented in a package is further broken down and implemented using classes at the third level of hierarchy. Classes are made out of items, which are basically methods and fields. Fields declare data which are associated with the class.Interfaces encode the similarities among classes.

The fourth level of hierarchy consists of objects which act as data structures and store data associated with the class. This helps to store multiple values of the same type of data.

At the lowest level i.e the fifth is the data, which is a part of the object. At this level, the code which is a part of the method processes this data.

This hierarchy is followed during any application development using an object oriented language and when an analyst is asked to refactor code, he/she also parses through this same hierarchy to understand the code functionality and to find spots where the code can be refactored.

Most of the refactoring methods belong to level 3, level 4 and level 5, hence these categories have again been divided into sub-categories, to reduce generalization & make the categorization more specific. Here is an attempt to make categorization of the refactoring methods based on the said hierarchy. Also there are a few categories which aren't derived from the above hierarchy. Here are the categories and sub-categories using which the refactoring methods available at http://www.refactoring.com/catalog/index.html have been categorized.

Categories

Refactoring the Package

A refactoring method will fall under this category if the changes made affect the package structure or add to the functionality to the package. The refactoring method generally may involve breaking a package to smaller packages to divide the functionality or moving classes to a more relevant package. 

*Extract Package
*Move Class

Refactoring the Class

  • Changing Class Association

A refactoring method falls in this category if it tries to change the association between two classes so that features of a class may be added or removed. 

*Change Unidirectional Association to Bidirectional
*Change Bidirectional  Association to Unidirectional
*Extract Interface
  • Change of Class Structure A refactoring method falls in this category when it tries to change the hierarchy that the classes share amongst them.
    • Splitting of Class
*Duplicate Observed Data
*Extract Class
*Extract SubClass
*Extract SuperClass
*Separate Data Access Code
*Localize Disparate Logic
    • Merging of Class
*Collapse Hierarchy
*Replace Subclass with Fields
*Inline Class
  • Inter-Class Movement of Items

A refactoring method falls in this category when it tries to move functionality/detail between classes. This may involve movement of constructors, fields or methods between classes. 

*Pull up Constructor Body
*Pull up Field
*Pull up Method
*Push Down Field 
*Push Down Method
*Move Field
*Move Method
  • Moving Additional Functionality to Client Class

A refactoring method falls in this category when functionality needs to be added to a server class which cannot be altered. The refactoring method achieves it by adding sever class extensions to the client method. 

*Introduce Local Extension  
*Introduce Foreign Method
  • Replacement of Class Instantiation with Constructors

A refactoring method falls in this category when it tries to convert loading of some of the classes from dynamic to static or vice-versa. 

*Convert Static to Dynamic Construction
*Convert Dynamic to Static Construction

Refactoring the Method

  • Meaningful and Detailed Method Calls

A refactoring method will fall under this category if it modifies a method call to pass more data to the method or tries to make the method call more understandable. 

*Add Parameter
*Preserve Whole Object
*Rename Method
  • Change of Structure of the Method Code

A refactoring method will fall under this category if it deliberately changes the internal flow of the code without affecting the output. These methods need not result in the optimization of the code or simplification. 

*Consolidate Conditional Expression
*Encapsulation Collection
*Extract Method
*Inline Method
*Form Template Method
*Replace Nested Conditional with Guard Clauses
*Replace Parameter with Method
  • Change Method Call Hierarchy/Sequence

A refactoring method will fall in this category when it tries to change the method call flow in any way. 

*Remove Middle man
*Replace Delegation with Inheritance
*Replace Inheritance with Delegation
  • Improve Method Readability

A refactoring method will fall under this category when it increases the readability of the code for a new person reading the code or for debugging purpose if ever needed. 

*Introduce Explaining Variable
*Replace Magic No with Symbolic Constant
*Replace Recursion with Iteration 
*Split Temporary Variable
  • Method Code Refactoring based on Method Arguments

A refactoring method will fall under this category when it makes the behavior of the executed method code, change depending on the argument passed, or when it frees the method code of this feature. 

*Parameterize Method
*Replace Conditional with Polymorphism
*Replace Conditional with Visitor
*Replace Parameter with Explicit Methods

Refactoring the Object

  • Replacements with Objects

A refactory method will fall under this category when the code is changed such that its execution is more centered around the object. And different parameters like array, data values are replaced by objects. 

*Introduce Null Object
*Introduce Parameter Object
*Replace Array with Object
*Replace Data Value with Object
*Replace Method with Method Object
*Replace Record with Data Class
  • Object Initialization

A refactory method will fall under this category when it tries to alter the constructor used for the initialization of the object. 

*Replace Constructor with Factory Method
*Remove Setting Method
  • Accessing the Object/Data

A refactory method will fall under this category if the method changes the way an object or data is accessed. 

*Change Reference to Value
*Change Value to Reference
*Refactor Architecture by Tiers
*Self Encapsulate Field

Refactoring the Code

  • Code Optimization

A refactoring method will fall under this category when the method brings about change in the code such a way that its execution is optimized. 

*Consolidate Duplicate Conditional Fragments
*Eliminate Inter-Entity Bean Communication
*Inline Temp
*Remove Control Flag
*Replace Iteration with Recursion
*Replace Temp with Query
*Use a Connection Pool
  • Code Reliability Improvement

A refactoring method will fall under this category if it helps to make the code less prone to errors and adhere more to its intended functionality. 

*Introduce Assertion
*Introduce A Controller
*Introduce Synchronizer Token
*Reduce Scope of Variable
*Remove Assignments to Parameters
  • Code Simplification

A refactoring method will fall under this category when it causes simplification of the code making it more readable and understandable, it may or may not optimize the execution. 

*Encapsulate Downcast
*Remove Double Negative
*Replace Assignment with Initialization
*Reverse Conditional
*Separate Query from Modifier
*Split Loop
*Substitute Algorithm
*Decompose Conditional
  • Redundant Code Elimination

A refactoring method will fall under this category if it helps to eliminate the unnecessary code and makes the code cleaner. 

*Parametrize Method
*Remove Parameter
  • Removal of "Type Code"

A refactory method will fall under the category Removal of "Type Code" if the method helps to remove the type code. 

*Replace Type Code with Class
*Replace Type Code with State/Strategy
*Replace Type Code with Subclasses

Refactoring for Privacy

A refactoring method will fall under this category if it helps in data protection and privacy. 

*Encapsulate Field
*Hide Delegate
*Hide Method
*Hide Presentation Tier-Specific Details from the Business tier
*Introduce Business Delegate
*Wrap Entities with Session

Dealing with Exceptions

A refactoring method will fall under this category if it optimizes the way the code handles an exception situation. 

*Remove Error Code with Exception
*Replace Exception with Test

References

http://www.refactoring.com
Refactoring: Improving the Design of Existing Code by Martin Fowler.

Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2009/wiki1a_8_nd&oldid=19044"