Jump to content

Design pattern

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by SindHind (talk | contribs) at 12:01, 6 February 2017 (omit TOC). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

"Design patterns" redirects here. For the book, see Design Patterns.

A design pattern is the re-usable form of a solution to a design problem. The idea was introduced by the architect Christopher Alexander[1] and has been adapted for various other disciplines, most notably computer science.[2]

An organized collection of design patterns that relate to a particular field is called a pattern language. This language gives a common terminology for discussing the situations designers are faced with.

The elements of this language are entities called patterns. Each pattern describes a problem that occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice. — Christopher Alexander[1]

Documenting a pattern requires explaining why a particular situation causes problems, and how the components of the pattern relate to each other to give the solution.[3] Christopher Alexander describes common design problems as arising from "conflicting forces" — such as the conflict between wanting a room to be sunny and wanting it not to overheat on summer afternoons. A pattern would not tell the designer how many windows to put in the room; instead, it would propose a set of values to guide the designer toward a decision that is best for their particular application. Alexander, for example, suggests that enough windows should be included to direct light all around the room. He considers this a good solution because he believes it increases the enjoyment of the room by its occupants. Other authors might come to different conclusions, if they place higher value on heating costs, or material costs. These values, used by the pattern's author to determine which solution is "best", must also be documented within the pattern.

Pattern documentation should also explain when it is applicable. Since two houses may be very different from one another, a design pattern for houses must be broad enough to apply to both of them, but not so vague that it doesn't help the designer make decisions. The range of situations in which a pattern can be used is called its context. Some examples might be "all houses", "all two-story houses", or "all places where people spend time".

For instance, in Christopher Alexander's work, bus stops and waiting rooms in a surgery center are both within the context for the pattern "A PLACE TO WAIT".

Domain-specific articles

See also

Further reading

  • Alexander, Christopher (1977). A Pattern Language: Towns, Buildings, Construction. Oxford University Press. ISBN 0-19-501919-9.
  • Erl, Thomas (2009). SOA Design Patterns. New York: Prentice Hall/PearsonPTR. p. 864. ISBN 0-13-613516-1.
  • Frank Buschmann, Kevlin Henney, Douglas C. Schmidt "On Patterns and Pattern Languages"
  • Gamma, Helm, Johnson & Vlissides (1994). Design Patterns (the Gang of Four book). Addison-Wesley. ISBN 0-201-63361-2.{{cite book}}: CS1 maint: multiple names: authors list (link)

[6] (Note: there is debate about whether the "Gang of Four" book actually contains any patterns in the Alexandrian's sense.)

  • Jenifer Tidwell. Designing Interfaces
  • Wolfgang Pree. Design Patterns for Object-Oriented Software Development
  • Leitner, Helmut (2015). Pattern Theory: Introduction and Perspectives on the Tracks of Christopher Alexander, ISBN 1505637430.

References

  1. ^ a b Alexander, A Pattern Language
  2. ^ Gamma et al., 1994, Design Patterns (the "Gang of Four" book)
  3. ^ James Maioriello (2002-10-02). "What Are Design Patterns and Do I Need Them?". Retrieved 2011-03-21. The patterns are documented from a template that identifies the information needed to understand the software problem and the solution in terms of the relationships between the classes and objects necessary to implement the solution.
  4. ^ Mettler T, Eurich M (2012). "A "design-pattern"-based approach for analyzing e-health business models". Health Policy & Technology. 1 (2): 77–85. doi:10.1016/j.hlpt.2012.04.005.
  5. ^ Sprenger M, Mettler T (2016). On the Utility of E-Health Business Model Design Patterns. European Conference on Information Systems.
  6. ^ James Coplien (2014-07-11). "Patterns: The Notion is Grounded in Alexander's Work". Retrieved 2014-07-16. The GoF claims to take its pattern inspiration from Christopher Alexander (as they say in the front matter of the book), who popularized the term in the broader field of design. To Alexander a pattern: is always an element of pattern language; contributes to deep human feeling; and is always geometric in nature. At least some of the GoF patterns fail on at least one of these points, and several fail on all three.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Design_pattern&oldid=763990375"