View source

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in the group: Users.
• You must confirm your e-mail address before editing pages. Please set and validate your e-mail address through your user preferences.

You can view and copy the source of this page:

The strategy pattern is useful when there is a need to separate the implementation of a process from the class that uses it. There are several reasons that this can be useful. * There are several different versions of the algorithm to implement. * The algorithms are used in more than one place. [[Once and only once]] * There is a need to create an encapsulation boundary around the algorithm to hide implementation details. * The class using the strategy implements many different behaviours choosing which behaviour to use with ''if'' statements. Each choice can be represented as a strategy instead simplifying code and making the intent explicit. [[Image:Strategy pattern.jpg|frame| The strategy pattern]]

Return to Strategy pattern.