Content deleted Content added
m Highlighting |
TakuyaMurata (talk | contribs) rewrite definition |
||
Line 1:
Using '''Design pattern'''s is to reuse the ways that past designers discovered without efforts of rediscovering it. MVC or [[Model view contoller triad]] is an good antiqueted example of design pattern.
The first widely seen catalogue of '''software design patterns''' was ''[[Design Patterns]]: elements of reusable object-oriented software'' by the "[[gang of four]]", Gamma, Helm, Johnson and Vlissides.▼
▲The
:[Design patterns] solve specific design problems and make object-oriented desings more flexiblem elegant, and ultimately reusable. They help designers reuse successful designs by basing new designs on prior experience. A designer who is familiar with such patterns can apply them immediately to design problems without having to rediscover them.
In computer programming, the incredible gap on productivility between amatures and expers is partly a different in experience, if not all. Experts have weathered a lot of problems again and again. Typically experts end up with the same pattern to solve the problems as each other's. That is a design pattern. (GoF)
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 alog with the trade-off, which is convinient to assess that apply the solution before it costs too much to accept. It is important that patterns accompany a name because it makes possible to describe problems, solutions and talk about them with other folks.
See also [[anti-pattern]], [[amelioration pattern]]
Creational patterns
Line 63 ⟶ 72:
== Related Topics ==
* [[Pattern Mining]]
== External Links ==
* [[http://java.sun.com/blueprints/corej2eepatterns/Patterns/index.html Java J2EE pattern catalog]]
== Credit ==
* The list of design patterns is entirely based on a [[wiki page]] http://c2.com/cgi/wiki?CategoryPattern.
* The definition of design pattern is based on [[GoF]].
| |||