Tactical Design Patterns in .NET: Managing Responsibilities

Textbooks and courses explain a design pattern by highlighting a situation, then providing a convenient solution: the pattern. There is nothing wrong with this when documenting a design pattern. The problem comes when the same sequence of steps is applied to recognize the design pattern directly from the requirements. The request is then captured in terms of a well-known design pattern.