OODesign - Design Pattern 6 (Structural Patterns)

Ref: http://www.oodesign.com/design-principles.html

Adapter Pattern
> Convert the interface of a class into another interface clients expect.
> Adapter lets classes work together, that could not otherwise because of incompatible interfaces.
(example: HA7Adaptor (from HA7 Study/Series/Image/Annotation -> PatientVO/SeriesVO/ImageVO/AnnotationVO)
(example: HL7Adat0r (convert HL7 Object to XML and other format)


Bridge Pattern
> The intent of this pattern is to decouple abstraction from implementation so that the two can vary independently.
(ref: GoF Design Pattern)
(ref: wiki)

Composite Pattern
> The intent of this pattern is to compose objects into tree structures to represent part-whole hierarchies.
> Composite lets clients treat individual objects and compositions of objects uniformly.
(example:
DrawingTool (Component)
FreeHand (Composite)
ControlPoint (leaf)
AddFreeHandCommand (client) )