https://wiki.sarg.dev/index.php?action=history&feed=atom&title=Structural_patternStructural pattern - Revision history2026-06-19T21:24:38ZRevision history for this page on the wikiMediaWiki 1.44.2https://wiki.sarg.dev/index.php?title=Structural_pattern&diff=512646&oldid=previmported>Helpful Raccoon: rm non-notable2025-07-26T21:12:00Z<p>rm non-notable</p>
<p><b>New page</b></p><div>In [[software engineering]], '''structural design patterns''' are [[Design pattern (computer science)|design patterns]] that ease the design by identifying a simple way to realize relationships among entities.<br />
<br />
Examples of Structural Patterns include:<br />
<br />
* [[Adapter pattern]]: 'adapts' one interface for a class into one that a client expects<br />
** Adapter pipeline: Use multiple adapters for debugging purposes.<ref>{{cite web<br />
| url = http://c2.com/<br />
| title = Adapter Pipeline<br />
| date = 2010-12-31<br />
| publisher = Cunningham & Cunningham, Inc.<br />
| archive-url = http://c2.com/cgi/wiki?AdapterPipeline<br />
| archive-date = 2010-12-31<br />
| access-date = 2012-07-20<br />
}}</ref><br />
** Retrofit Interface Pattern:<ref>{{cite web<br />
| url = http://c2.com/<br />
| title = Retrofit Interface Pattern<br />
| author = BobbyWoolf<br />
| date = 2002-06-19<br />
| publisher = Cunningham & Cunningham, Inc.<br />
| archive-url = http://c2.com/cgi/wiki?RetrofitInterfacePattern<br />
| archive-date = 2002-06-19<br />
| access-date = 2012-07-20<br />
}}</ref><ref>{{cite web<br />
| url = http://c2.com/<br />
| title = External Polymorphism<br />
| author = MartinZarate <br />
| date = 2010-12-31<br />
| publisher = Cunningham & Cunningham, Inc.<br />
| archive-url = http://c2.com/cgi/wiki?ExternalPolymorphism<br />
| archive-date = 2010-12-31<br />
| access-date = 2012-07-20<br />
}}</ref> An adapter used as a new interface for multiple classes at the same time.<br />
* [[Aggregate pattern]]: a version of the [[Composite pattern]] with methods for aggregation of children<br />
* [[Bridge pattern]]: decouple an abstraction from its implementation so that the two can vary independently<br />
** Tombstone: An intermediate "lookup" object contains the real location of an object.<ref>{{cite web<br />
| url = http://c2.com/<br />
| title = Tomb Stone<br />
| date = 2007-06-17<br />
| publisher = Cunningham & Cunningham, Inc.<br />
| archive-url = http://c2.com/cgi/wiki?AdapterPipeline<br />
| archive-date = 2007-06-17<br />
| access-date = 2012-07-20<br />
}}</ref><br />
* [[Composite pattern]]: a tree structure of objects where every object has the same interface<br />
* [[Decorator pattern]]: add additional functionality to an object at runtime where subclassing would result in an exponential rise of new classes<br />
* [[Extensibility pattern]]: a.k.a. Framework - hide complex code behind a simple interface<br />
* [[Facade pattern]]: create a simplified interface of an existing interface to ease usage for common tasks<br />
* [[Flyweight pattern]]: a large quantity of objects share a common properties object to save space<br />
* [[Marker interface pattern|Marker pattern]]: an empty interface to associate metadata with a class.<br />
* [[Pipes and filters]]: a chain of processes where the output of each process is the input of the next<br />
* [[Opaque pointer]]: a pointer to an undeclared or private type, to hide implementation details<br />
* [[Proxy pattern]]: a class functioning as an interface to another thing<br />
<br />
==See also==<br />
* [[Behavioral pattern]]<br />
* [[Concurrency pattern]]<br />
* [[Creational pattern]]<br />
<br />
==References==<br />
{{Commons category|Structural software design patterns}}<br />
{{Reflist}}<br />
<br />
{{Design Patterns patterns}}<br />
<br />
{{DEFAULTSORT:Structural Pattern}}<br />
[[Category:Software design patterns]]<br />
[[Category:Articles with example Java code]]<br />
[[Category:Articles with example C Sharp code]]</div>imported>Helpful Raccoon