Design patterns represent the accumulated knowledge of the community of software developers of standardised solutions to recurring problems.
They allow software developers to make use of the knowledge of past designers. Many design projects are confronted with similar problems that demand similar solutions. A design pattern is an abstraction of a solution for a particular class of problems. MVC or model view controller triad is a classical example of design pattern. It was introduced 1980 in the Smalltalk system.
The book that introduced the term design pattern to software development is Design Patterns: elements of reusable object-oriented software (commonly shortened to GoF -- Gang of Four a reference to the four authors) says:
Each pattern comes up with the problem that happens again and again among programmers. Then it shows a typical solution for such a problem, if not the best solution, along with the trade-off, which is a convenient assessment to make prior to applying a potentially costly solution. It is important that patterns accompany a name because it makes possible to describe problems, solutions and talk about them with other folks.
For example the classical MVC pattern is actually a combination of three patterns listed below - Observer, Composite and Strategy. It is broadly used today.
Frequent problems that occur in programming are sometimes less commonly called anti-pattern.
See also amelioration pattern
Fundamental patterns
| Table of contents |
|
2 References 3 External links |
Related Topics
References
External links