Karsten on the Business of Software et al.
Everybody who's a little bit interested in software development has heard the term "software pattern" and most likely something about the pattern book of the "Gang of Four" (normally cited as "GoF").
For those who are not yet in object-oriented software development: Software patterns give a high-level solution to a development problem, described in a well-defined, commonly known structure.
Patterns are heavily used to discuss the architecture of software applications, i.e. in which relation subparts of it stand to each other and which solutions are used to solve common problems.
It therefore doesn't surprise that a major origin of software design patterns lies in pattern-based approaches for architectonics.
The fascinating and infuential architect Christopher Alexander used a catalogue of patterns for architectural building. These patterns could be used by architects to reflect decisions in the design stage.
Patterns vers. Best Practices
Also, it could be a best practice to use software patterns. But the core of the software pattern is its formal description which lacks the best practice.
In my opinion, the "uniform structure" of the GoF is quite abundant.
/* Sthg. about pattern's history also Baxandall, GotA etc. Which topics pattern could be applied to.
BPM, Design, User-Interaction, Project
Work, Organisation, Algorithms (sic), GoF Workflow Patterns (http://tmitwww.tm.tue.nl/research/patterns/) Antipatterns Baxandall Alexander E. Berne Patterns as... General way to describe a pattern (e.g. environment, problem/solution etc.) */
© 2003-2013 Karsten Gresch