Content deleted Content added
rm non-notable |
|||
| (24 intermediate revisions by 22 users not shown) | |||
Line 1:
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
Examples of Structural Patterns include:
* [[Adapter pattern]]: 'adapts' one interface for a class into one that a client expects
** Adapter pipeline: Use multiple adapters for debugging purposes.<ref>
| url = http://c2.com/
▲** Adapter pipeline: Use multiple adapters for debugging purposes.<ref>http://c2.com/cgi/wiki?AdapterPipeline</ref>
| title = Adapter Pipeline
| date = 2010-12-31
| publisher = Cunningham & Cunningham, Inc.
| archive-url = http://c2.com/cgi/wiki?AdapterPipeline
| archive-date = 2010-12-31
| access-date = 2012-07-20
}}</ref>
** Retrofit Interface Pattern:<ref>{{cite web
| url = http://c2.com/
| title = Retrofit Interface Pattern
| author = BobbyWoolf
| date = 2002-06-19
| publisher = Cunningham & Cunningham, Inc.
| archive-url = http://c2.com/cgi/wiki?RetrofitInterfacePattern
| archive-date = 2002-06-19
| access-date = 2012-07-20
}}</ref><ref>{{cite web
| url = http://c2.com/
| title = External Polymorphism
| author = MartinZarate
| date = 2010-12-31
| publisher = Cunningham & Cunningham, Inc.
| archive-url = http://c2.com/cgi/wiki?ExternalPolymorphism
| archive-date = 2010-12-31
| access-date = 2012-07-20
}}</ref> An adapter used as a new interface for multiple classes at the same time.
* [[Aggregate pattern]]: a version of the [[Composite pattern]] with methods for aggregation of children
* [[Bridge pattern]]: decouple an abstraction from its implementation so that the two can vary independently
** Tombstone: An intermediate "lookup" object contains the real ___location of an object.<ref>
| url = http://c2.com/
| title = Tomb Stone
| date = 2007-06-17
| publisher = Cunningham & Cunningham, Inc.
| archive-url = http://c2.com/cgi/wiki?AdapterPipeline
| archive-date = 2007-06-17
| access-date = 2012-07-20
}}</ref>
* [[Composite pattern]]: a tree structure of objects where every object has the same interface
* [[Decorator pattern]]: add additional functionality to
* [[Extensibility pattern]]:
* [[Facade pattern]]: create a simplified interface of an existing interface to ease usage for common tasks
* [[Flyweight pattern]]: a
* [[Marker interface pattern|Marker pattern]]: an empty interface to associate metadata with a class.
* [[Pipes and filters]]: a chain of processes where the output of each process is the input of the next▼
* [[Opaque pointer]]: a pointer to an undeclared or private type, to hide implementation details
* [[Proxy pattern]]: a class functioning as an interface to another thing
▲* [[Pipes and filters]]: a chain of processes where the output of each process is the input of the next
==See also==
* [[Behavioral pattern]]
* [[Creationism pattern]]▼
* [[Concurrency pattern]]
==References==
{{Commons category|Structural software design patterns}}
{{Reflist}}
{{Design Patterns patterns}}
{{DEFAULTSORT:Structural Pattern}}
[[Category:Software design patterns]]
[[Category:Articles with example Java code]]
[[Category:Articles with example C Sharp code]]
| |||