imported>Infinitywiki2: Undid revision 1337606309 by ~2026-91779-2 (talk)

2026-02-10T13:29:24Z

Undid revision 1337606309 by ~2026-91779-2 (talk)

← Older revision		Revision as of 14:29, 10 February 2026
Line 29:		Line 29:

	== See also ==		== See also ==
	* [[Style guide]]
	* [[Design paradigm]]
	* [[Anti-pattern]]		* [[Anti-pattern]]
	* [[Dark pattern]]		* [[Dark pattern]]
			* [[Design paradigm]]
			* [[Style guide]]

	== References ==		== References ==

imported>REDACTED403: reads as AI generated (HG) (3.4.12)

2024-11-06T11:25:44Z

reads as AI generated (HG) (3.4.12)

New page

{{Short description|Re-usable form of a solution to a design problem}}
{{Redirect|Design patterns|the book|Design Patterns}}
{{About|a relatively general design concept|application for software development|Software design pattern}}

A '''design pattern''' is the re-usable form of a solution to a design problem. The idea was introduced by the architect [[Christopher Alexander]]<ref name="Alexander, A Pattern Language" >{{cite book |first=Christopher |last=Alexander |author-link=Christopher Alexander |title=[[A Pattern Language: Towns, Buildings, Construction]] |series=Center for Environmental Structure series |volume=2 |location=New York |publisher=[[Oxford University Press]] |year=1977 |isbn=0-19-501919-9 |oclc=3132495}}</ref> and has been adapted for various other disciplines, particularly [[software engineering]].<ref name="Gang of Four" >{{cite book |title=[[Design Patterns: Elements of Reusable Object-Oriented Software]] |first1=Erich |last1=Gamma |first2=Richard |last2=Helm |first3=Ralph |last3=Johnson |first4=John |last4=Vlissides |series=Addison-Wesley professional computing series |location=Reading, Mass. |publisher=[[Addison-Wesley]] |year=1994 |isbn=0-201-63361-2 |oclc=31171684}} The "[[Design Patterns (book)|Gang of Four]]" book.</ref>

== Details ==
{{Further|Pattern language}}

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.

{{Blockquote|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.|author=Christopher Alexander|source=''[[A Pattern Language]]''<ref name="Alexander, A Pattern Language"/>}}

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.<ref>{{cite web |access-date=2011-03-21 |first=James |last=Maioriello |date=2002-10-02 |title=What are design patterns and do I need them? |url=http://www.developer.com/design/article.php/1474561/What-Are-Design-Patterns-and-Do-I-Need-Them.htm |website=developer.com}}</ref> [[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".

== Examples ==

* [[Software design pattern]], in software design
* [[Architectural pattern]], for software architecture
* [[Interaction design pattern]], used in interaction design / human–computer interaction
* [[Pedagogical patterns]], in teaching
* [[Pattern gardening]], in gardening

Business models also have design patterns.<ref>For example: {{cite journal |last1=Mettler |first1=Tobias |last2=Eurich |first2=Markus |date=June 2012 |title=A 'design-pattern'–based approach for analyzing e-health business models |journal=[[Health Policy and Technology]] |volume=1 |issue=2 |pages=77–85 |doi=10.1016/j.hlpt.2012.04.005}}</ref> See {{slink|Business model#Examples}}.

== See also ==
* [[Style guide]]
* [[Design paradigm]]
* [[Anti-pattern]]
* [[Dark pattern]]

== References ==
{{Reflist}}

== Further reading ==
{{Refbegin}}
* {{cite book |last=Erl |first=Thomas |author-link=Thomas Erl |title=SOA Design Patterns |series=Prentice Hall service-oriented computing series from Thomas Erl |publisher=[[Prentice Hall]] |location=Upper Saddle River, NJ |year=2009 |isbn=978-0-13-613516-6 |oclc=156832597}}
* {{cite book |last=Leitner |first=Helmut |date=2015 |title=Pattern Theory: Introduction and Perspectives on the Tracks of Christopher Alexander |series=Pattern research series |volume=1 |location=Graz |publisher=Helmut Leitner, HLS Software |isbn=978-1-5056-3743-4 |oclc=913795677}}
* {{cite book |last=Pree |first=Wolfgang |author-link=Wolfgang Pree |date=1995 |title=Design patterns for object-oriented software development |series=ACM Press books |location=Wokingham, England; Reading, Mass. |publisher=[[Addison-Wesley]] |isbn=0201422948 |oclc=31291883}}
* {{cite book |last1=Schmidt |first1=Douglas C. |author-link2=Douglas C. Schmidt |last2=Buschmann |first2=Frank |last3=Henney |first3=Kevlin |author-link3=Kevlin Henney |date=2007 |title=Pattern-Oriented Software Architecture: On Patterns and Pattern Languages |series=Wiley series in software design patterns |volume=5 |location=Chichester, UK; New York |publisher=[[Wiley (publisher)|Wiley]] |isbn=9780471486480 |oclc=62532759}}
* {{cite book |last1=Tidwell |first1=Jenifer |last2=Brewer |first2=Charles |last3=Valencia |first3=Aynne |date=2020 |orig-year=2005 |title=Designing Interfaces: Patterns For Effective Interaction Design |edition=3rd |location=Sebastopol, CA |publisher=[[O'Reilly Media|O'Reilly]] |isbn=9781492051961 |oclc=1138701080 |quote=Presents solutions to common UI design problems as a collection of patterns—each containing concrete examples, recommendations, and warnings.}}
{{Refend}}

{{Design}}

[[Category:Design patterns| ]]

[[ja:デザインパターン]]
[[pl:Wzorzec projektowy]]
[[tr:Tasarım örüntüsü]]
[[vi:Mẫu thiết kế]]
[[zh:设计模式]]

Design pattern - Revision history

imported>Infinitywiki2: Undid revision 1337606309 by ~2026-91779-2 (talk)

imported>REDACTED403: reads as AI generated (HG) (3.4.12)