Originally posted by Leslie Chaim:
Given a problem, I think you first (2) look for Patterns, then (3) identify the use cases, draw diagrams.. and finally (1) look for an OO implementation.
Refactoring, is then a fruit by itself (4), which can mean simple enhancements (or extending) or all of the above.
Correct me if I am wrong.
I will!
Design Patterns are nothing more than often used solutions to common design problems. They are *part of* finding an (OO) solution to a problem. Actually, one of the most effective ways to use patterns is to
refactor to patterns.
Regarding UML, it can be used to communicate aspects of the problem domain and of the design, wether imagined or already existing.
So I would argue that there is no ordering in time for those concepts.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus