Chapter 4: Structural Design Patterns

Chapter 4 comprehensively details structural design patterns, which provide systematic methods for assembling classes and objects into larger, more functional systems. These structural designs are broadly divided into class patterns, which leverage inheritance to compose interfaces or implementations (such as the class form of the Adapter), and object patterns, which employ object composition to achieve flexibility that can be altered during run-time. Seven key patterns are explored, each addressing specific structural complexities. The Adapter pattern, also known as a Wrapper, resolves incompatibilities between two existing interfaces, allowing otherwise unrelated classes, like a general graphics interface and a specific text view, to collaborate. The Bridge pattern is designed to prevent class proliferation by decoupling an abstraction from its implementation, ensuring that both can be independently extended via subclassing, which is crucial for building portable applications where the implementation may need to be selected or switched at run-time. The Composite pattern standardizes the treatment of individual objects (Leaves) and groupings of objects (Composites) by clients, making it possible to represent complex, recursive part-whole hierarchies uniformly through a common interface, such as organizing graphics components into complex diagrams. The Decorator pattern offers a dynamic and flexible alternative to static inheritance for adding responsibilities to objects, where decorator objects enclose and forward requests to their component while adding functionality like borders or scrolling, allowing for open-ended, recursive enhancements. The Facade pattern simplifies the interface to a complex or evolving subsystem, providing a high-level, unified entry point that promotes weak coupling and better system layering. The Flyweight pattern supports the efficient use of a massive number of fine-grained objects by sharing them; this is accomplished by distinguishing intrinsic state (sharable, context-independent) stored in the flyweight from extrinsic state (context-dependent) which clients must pass in when needed. Finally, the Proxy pattern provides a stand-in or surrogate for another object to control access, enabling functions such as virtual proxies that defer the costly creation of large objects until they are actually referenced, or remote proxies that manage communication across address spaces. Although structural patterns often share implementation mechanisms rooted in composition, their intents—whether for adaptation, decoupling, hierarchy representation, dynamic enhancement, simplification, sharing, or access control—remain distinct.