Software design pattern: Difference between revisions

Revision as of 23:49, 17 December 2003

Revision as of 05:23, 22 December 2003

Line 13:

Each pattern comes up with the problem that happens again and again among [[programmer]]s. 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 pattern|Observer]], [[Composite pattern|Composite]]'' and ''[[Strategy pattern|Strategy]]''. It is broadly used today.

Frequent problems that occur in [[programming]] are sometimes less commonly called '''[[anti-pattern]]'''.