아름다운프로'의 JTOP.org 백업사이트

Collapse Hierarchy

A superclass and subclass are not very different.

Merge them together.


For more information see page 344 of Refactoring





***** 아름다운프로님에 의해서 게시물 복사 + 카테고리변경되었습니다 (2003-12-18 17:27)

Change Value to Reference

You have a class with many equal instances that you want to replace with a single object.


Turn the object into a reference object.


For more information see page 179 of Refactoring





***** 아름다운프로님에 의해서 게시물 복사 + 카테고리변경되었습니다 (2003-12-18 17:27)

Change Unidirectional Association to Bidirectional

You have two classes that need to use each other's features, but there is only a one-way link.

Add back pointers, and change modifiers to update both sets.


For more information see page 197 of Refactoring

Additional Comments

Doing a remove

In the example I showed an addOrder method, but I didn't show the removeOrder method. If you want to do a remove, you would write it like the add method but set the customer to null.

Class Customer ...
void removeOrder( Order arg ) {
  arg.setCustomer( null );
}

Contributors

- Andy Bulka
- Don Roberts



***** 아름다운프로님에 의해서 게시물 복사 + 카테고리변경되었습니다 (2003-12-18 17:27)

Change Reference to Value

You have a reference object that is small, immutable, and awkward to manage.

Turn it into a value object.


For more information see page 183 of Refactoring





***** 아름다운프로님에 의해서 게시물 복사 + 카테고리변경되었습니다 (2003-12-18 17:27)

Change Bidirectional Association to Unidirectional

You have a two-way association but one class no longer needs features from the other.

Drop the unneeded end of the association.


For more information see page 200 of Refactoring





***** 아름다운프로님에 의해서 게시물 복사 + 카테고리변경되었습니다 (2003-12-18 17:27)

Add Parameter

A method needs more information from its caller.

Add a parameter for an object that can pass on this information.



For more information see page 275 of Refactoring





***** 아름다운프로님에 의해서 게시물 복사 + 카테고리변경되었습니다 (2003-12-18 17:27)