Software design pattern: Difference between revisions

Revision as of 08:42, 10 August 2003

Revision as of 15:08, 21 October 2003

Line 1:

[[ja:デザインパターン]]

'''Design patterns''' are standardised solutions to recurring problems. They represent the accumulated lessons that have been accumulated inby the community of [[computer programming]].

They allow onea 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 thea best solutionssolution 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]]: elements of reusable object-oriented software'' (commonly shortened to ''GoF'') says:

:[Design patterns] solve specific design problems and make object-oriented designs more flexible and 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.