Software design pattern: Difference between revisions

Revision as of 13:50, 15 December 2003

Revision as of 23:49, 17 December 2003

Line 5:

They allow [[software developer]]s to make use of the [[knowledge]] of past [[designer]]s. Many [[design project]]s are confronted with similar [[problem]]s that demand similar [[solution]]s. 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 programming language|Smalltalk]] system.

The [[book]] that introduced the ''term'' design pattern to [[software development]] is ''[[Design Patterns]]: [[element]]s of reusable [[object-oriented software]]'' (commonly shortened to ''GoF'' -- Gang of Four a reference to the four authors) says:

:[[Design patterns]] solve specific design problems and make [[object-oriented design]]s more flexible and elegant, and ultimately reusable. They help designers reuse successful [[design]]s 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.