The Mediator pattern is a design pattern that encourages loose coupling between objects. The Mediator pattern keeps objects from referring to each other explicitly, by having a central class that handles the interactions between the other objects.
The command design pattern is a proven solution to the problem of tightly coupled invokers and receivers. The command pattern is a way to encapsulate a request as an object, so that you can parameterize clients with different requests.
The Bridge pattern separates the abstraction from the implementation, so that each can vary independently of the other. This allows us to change the classes in each hierarchy independently of the other classes. The bridge design pattern helps to reduce the risk of breaking any existing code.
The Chain of Responsibility pattern is a behavioural design pattern that is commonly used. This pattern decouples classes by passing a request from one class to another until the request is recognised. The receiving objects are chained, and the request is passed along the chain until a specific object handles it. Each object in the chain is given a chance to handle the request.
The Builder design pattern provides a siple process to construct a complex object. We use the builder pattern when we have a number of mandatory and optional attributes to set when constructing an object.
The Memento design pattern provides an undo mechanism. It makes it possible to restore an object’s internal state without violating encapsulation.
This week we’ll continue our exploration of design patterns and look at another structural pattern, the Façade pattern. The Façade Pattern The Gang of Four book defines the Façade pattern as follows: "Provide a unified interface to a set of interfaces in a subsystem. Façade defines a higher-level interface that makes the
The Observer pattern is another useful design pattern. We can use it when we are interested in the state of an object, and we want to be notified whenever there is a change in its state.
The state pattern is a design pattern hat allows an object to alter its behaviour when its internal state changes.
This week we explore a common structural design pattern: the composite pattern. We can apply the Composite pattern when there is a part-whole hierarchy of objects, and a client needs to deal with objects uniformly regardless of the fact that an object might be a leaf (simple object) or a branch (composite object).
Stay home. Stay safe. Stay informed. Find information at www.sacoronavirus.co.za
Thank you for completing the form. We're excited that you have chosen to contact us about training. We will process the information as soon as we can, and we will do our best to contact you within 1 working day. (Please note that our offices are closed over weekends and public holidays.)
Our privacy policy ensures your data is safe: Incus Data does not sell or otherwise distribute email addresses. We will not divulge your personal information to anyone unless specifically authorised by you.
If you need any further information, please contact us on tel: (27) 12-666-2020 or email info@incusdata.com