It is a pattern that is strongly related to the template method pattern.

The Template Method pattern may be used to add immediate present value to the software or with a vision to enhancements in the future.

Sequential coupling can be refactored with the Template method pattern to overcome the problems posed by the usage of this anti-pattern.

The Template Method pattern occurs frequently, at least in its simplest case, where a method calls only one abstract method, with object oriented languages.

The Template Method pattern thus manages the larger picture of task semantics, and more refined implementation details of selection and sequence of methods.

Template method pattern in UML and in LePUS3 (a formal modelling language)

The Template Method pattern implements the Protected Variations GRASP principle, like the Adapter pattern does.

Techniques for designing and implementing algorithm designs are algorithm design patterns, such as template method pattern and decorator pattern, and uses of data structures, and name and sort lists.

In software engineering, the template method pattern is a behavioral design pattern that defines the program skeleton of an algorithm in a method, called template method, which defers some steps to subclasses.

One example is that the template method pattern can be reinterpreted for compile time; so that your main class has a skeleton algorithm, which - at customization points - calls the appropriate functions of some of the policies.

A better approach to solve these issues is instead to use the template method pattern, where the superclass includes a purely abstract method that must be implemented by the subclasses and have the original method call that method:

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...