Software design pattern: Difference between revisions

Revision as of 00:24, 26 May 2003

Revision as of 01:21, 26 May 2003

Line 1:

'''Design patterns''' are lessons that have been cumulatied in the community of [[computer programming]]. Frequent problems that occur in programming are sometimes less commonly called '''[[anti-pattern]]'''.

They allow one 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 the best solutions 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 programming language|Smalltalk]] system.

The book that introduced the ''term'' design pattern to software development, ''[[Design Patterns]]: elements of reusable object-oriented software'' or [[GoF]] says:

Line 13:

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 [[anti-pattern]], [[amelioration pattern]]

See also [[anti-pattern]], [[amelioration pattern]]

Fundamental patterns

Line 54 ⟶ 56:

Concurrency patterns

* [[Action at a distance pattern]]

* [[Balking pattern]]

* [[Guarded suspension]]

Line 63 ⟶ 66:

RealTime patterns

* [[Scheduled task pattern]]

* [[User interface pattern]]

* [[Disable job requests while running job pattern]]

Line 80 ⟶ 82:

== External Links ==

* [[http://java.sun.com/blueprints/corej2eepatterns/Patterns/index.html Java J2EE pattern catalog]]

== Credit ==