TG5

Reuse:

• The goal of inheritance is only to achieve interface specification

• White box reuse could be achieved using inheritance

• Delegation reuses implemented functionality in the superclass

Generalisation vs. Specialisation:

• Generalisation usually leads to model transformation

• Refactoring means restructuring the UML model to fill in the gap between object design and system design

• In specialisation Inheritance we first discover the subclass then the superclass

Composite Pattern:

• Composite pattern is used when we need to choose between multiple strategies during runtime

• Composite pattern is a Creational pattern

• The composite pattern lets a Client treat an individual class called Leaf and Compositions of Leaf classes uniformly

Bridge Pattern:

• The bridge pattern provides a bridge between the concrete implementation and the solution domain

• The degenerated bridge pattern has no application domain taxonomy

• The bridge pattern allows to bind the interface and its subclass before startup time of the system

Proxy Pattern:

• The proxy pattern allows to defer object creation and object initialization to the time the object is needed

• During access control the proxy object acts as a stand-in for an object which is expensive to create

• The implementation of request() in Proxy uses inheritance to access request() in RealSubject