The Strategy pattern encapsulates an algorithm behind an interface so a class can use different concrete strategies for different contexts. section 7.6.1
A class-based Strategy design has three parts:
- A strategy interface that encapsulates the algorithm. section 7.6.1
- One or more concrete strategy classes, each for a particular context. section 7.6.1
- A class that uses the algorithm through the strategy. section 7.6.1
Bank overdraft policies
A banking application can use an Overdraft interface, concrete policies for different limits and fees, and an Account class that uses the selected policy. section 7.6.1



