Design Patterns discussion

["ziane" <mikal.ziane AT lip6.fr>]

Indeed the Problem part of a pattern is essential.
But the problem that a pattern addresses is often difficult to identify
clearly. It is often mixed up with the pattern's solution.
For instance the Intent section seems a bit ill-named since it does
include the solution.
There are also sometimes different problems adressed by the same
pattern.

Hence I would not trust too much what is communicated through a
pattern's name in documentation.
Hence I think that designers should make their quality objectives and
principles explicit and then document which mechanisms (e.g. refactoring
transformations) where used to enforce them.
Patterns are great but not enough.