According to the strategy pattern, the behaviors of a class should not be inherited.

It can be regarded as a special case of the State pattern and the Strategy pattern.

The strategy pattern uses aggregation instead of inheritance.

Formally speaking, the strategy pattern defines a family of algorithms, encapsulates each one, and makes them interchangeable.

Strategy pattern, which is kind of a base for the ECS pattern.

In the strategy pattern behaviors are defined as separate interfaces and specific classes that implement these interfaces.

Algorithm strategy patterns addressing concerns related to high-level strategies describing how to exploit application characteristics on a computing platform.

It has been described as a compile-time variant of the strategy pattern, and has connections with C++ template metaprogramming.

In computer programming, the strategy pattern (also known as the policy pattern) is a software design pattern, whereby an algorithm's behaviour can be selected at runtime.

The OpenXL standard is a design pattern with commonalities with the strategy pattern, and it focuses on the semantics of functions.

Strategy pattern in UML and in LePUS3 (a formal modelling notation)

Many object-oriented design patterns are expressible in functional programming terms: for example, the strategy pattern simply dictates use of a higher-order function, and the visitor pattern roughly corresponds to a catamorphism, or fold.

For instance, a class that performs validation on incoming data may use a strategy pattern to select a validation algorithm based on the type of data, the source of the data, user choice, and/or other discriminating factors.

Behavioral patterns (11): Chain-of-responsibility pattern, Command pattern, Interpreter pattern, Iterator pattern, Mediator pattern, Memento pattern, Observer pattern, State pattern, Strategy pattern, Template method pattern, Visitor pattern...