Evaluating Software Design Patterns
— the "Gang of Four" patterns implemented in Java 6

@Pattern(name="Mediator", scope=Object, purpose=Behavioural, participants={"Mediator","ConcreteMediator","Colleague"})

Package dk.rode.thesis.mediator

Implementations and examples of the Mediator design pattern [Gamma95, p.273].


Class Summary
Main Mediator tests.

Package dk.rode.thesis.mediator Description

Implementations and examples of the Mediator design pattern [Gamma95, p.273].


Unfortunately, due to a lack of time, the Mediator pattern has not been implemented. The idea for the pattern implementation was to construct a small "test—framework", where Mediator would play a central role controlling the individual tests and the objects tested as well as the communication between the two. Akin to the Model—View—Controller pattern [Buschmann96, p.125], the Mediator would play the Controller part where sequences could be tested (Model) and the results presented (View). Model and View thus corresponds to what Gamma et al. describe as Colleague Classes.

Gunni Rode / rode.dk

Gunni Rode / rode.dk

Feel free to use and/or modify the Java 6 source code developed for this thesis AT YOUR OWN RISK, but note that the source code comes WITHOUT ANY — and I do mean WITHOUT ANY — form of warranty WHAT SO EVER!

The original thesis and source code are available at rode.dk/thesis.