This is the third article in a series on software design patterns, continuing from my articles on the Strategy pattern and the Chain of Responsibility pattern. (http://en.wikipedia.org/wiki/Chain-of-responsibility_pattern).
Previously, we used naively solving whether a number is prime, but that doesn't fit this pattern so well. Instead, we'll be using a simplistic taxation system to illustrate our discussion.