Difference between revisions of "Design pattern"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) (→See also) |
||
| Line 16: | Line 16: | ||
* [[Pattern]] | * [[Pattern]] | ||
* [[Pattern language]] | * [[Pattern language]] | ||
| + | * [[Pattern matching]] | ||
| + | * [[Pattern recognition]] | ||
* [[Problem solving]] | * [[Problem solving]] | ||
| + | * [[Software design pattern]] | ||
| + | * [[Structure]] | ||
== External links == | == External links == | ||
* [https://en.wikipedia.org/wiki/Design_pattern Design pattern] @ Wikipedia | * [https://en.wikipedia.org/wiki/Design_pattern Design pattern] @ Wikipedia | ||
Revision as of 06:26, 1 September 2015
A design pattern in architecture and computer science is a formal way of documenting a solution to a design problem in a particular field of expertise.
Description
The idea was introduced by the architect Christopher Alexander in the field of architecture, and has been adapted for various other disciplines, including computer science.
An organized collection of design patterns that relate to a particular field is called a pattern language.
The elements of this language are entities called patterns. Each pattern describes a problem that occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice. — Christopher Alexander
The usefulness of speaking of patterns is to have a common terminology for discussing the situations designers already see over and over.
See also
- Design
- Pattern
- Pattern language
- Pattern matching
- Pattern recognition
- Problem solving
- Software design pattern
- Structure
External links
- Design pattern @ Wikipedia
