Hi. I think design patterns is a set of common solutions to recurring problems in development. We may think they as best practices you can apply when solving problems, it's divided in behavioral, structural and creational patterns. Refactoring is a technique when you rewrite or modify your code to make it clean, concise, small, with no redundancies, using object oriented approach and making use of design patterns of course. I guess they go hand in hand!

You could specify what you want to refactor, is it a class, method or some procedural legacy code?

Please go through the below link, may you can get an Idea how to refactoring approach in design pattern

http://www.cs.uni.edu/~wallingf/miscellaneous/student-papers/noborikawa-paper.pdf

@Juliano:-Thanks for replying me. I appreciate your answer but i want to refactor a total design pattern. It means that, first i will choose a design pattern as observer and i want to refactor it totally.Can it be possible.Thanks.

Yes, you can @Salman. Because practice makes perfect... :D

Design patterns are "best practices" to solve problems and you can implement them in a bunch of different ways.

After programming, you can apply a refator technique you find suitable in the resulting code, to make it better.

The strategy could be the extract method, collapse hierarchy, replace conditional code with polymorphism, etc. It depends on your code, of course.

An example of a situation and technique (inline class) to apply refactoring could be the following:

- When we have to change two different methods of two different classes, we can move the method in the most representative class.

If we instead have to change attributes of different classes, we can move

only attributes in the most representative class.

Sometimes we might remove all classes and move all attributes within the class that uses it. This strategy takes the name of "inline class."