Content deleted Content added
Tom.Reding (talk | contribs) m →References: Rem stub tag (class = non-stub & non-list) using AWB |
rm non-notable |
||
| (5 intermediate revisions by 5 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:
Line 7:
| url = http://c2.com/
| title = Adapter Pipeline
| date = 2010-12-31
| publisher = Cunningham & Cunningham, Inc.
|
|
|
}}</ref>
** Retrofit Interface Pattern:<ref>{{cite web
Line 18 ⟶ 17:
| title = Retrofit Interface Pattern
| author = BobbyWoolf
| publisher = Cunningham & Cunningham, Inc.
|
|
|
}}</ref><ref>{{cite web
| url = http://c2.com/
| title = External Polymorphism
| author = MartinZarate
| publisher = Cunningham & Cunningham, Inc.
|
|
|
}}</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
Line 38 ⟶ 37:
| url = http://c2.com/
| title = Tomb Stone
| date = 2007-06-17
| publisher = Cunningham & Cunningham, Inc.
|
|
|
}}</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 large quantity of objects share a common properties object to save space
* [[Marker interface pattern
* [[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
| |||