Mediator Design Pattern
Duration: 17 minutes
Summary: Design patterns are important because they represent generic solution to a common problem. They are created in a way that solves the common task at hand, but more importantly provide a solution that is easier to maintain and enhance as the application evolves. Please note that the code I am covering in these examples is mostly from the DoFactory web site (not my own). I am covering these patterns to make developers aware of them and encourage everyone to find the pattern that matches his/her needs and apply it to a specific scenario. Please note that not every problem needs a pattern (in other words, do not over use them). Some patterns are similar; with experience you can hand pick the one that mostly suits your needs. In this case, we will cover the Mediator Design Pattern. This pattern defines an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.
Methodology of the development of example: Good coding standard and simplified design.
Technology Used: C# 4.0
Keywords: C#, System, Console, abstract, override, ReadLine, WriteLine, base.