Gardient/behavioral-patterns
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge branch 'master' of https://github.com/MihaiTheCoder/BehavioralPatterns.git

Browse Source
This commit is contained in:
Petrutiu Mihai
2016-07-18 11:50:38 +03:00
parent 07b8236615 1548beb8f6
commit 7192d9e9ce
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@@ -415,6 +415,17 @@ The strategy pattern defines a family of algorithms, encapsulates each algorithm
In software engineering, the template method pattern is a behavioral design pattern that defines the program skeleton of an algorithm in an operation, In software engineering, the template method pattern is a behavioral design pattern that defines the program skeleton of an algorithm in an operation,
defering some steps to subclasses. It lets one redefine certain steps of an algorithm without changing the algorithm's structure. defering some steps to subclasses. It lets one redefine certain steps of an algorithm without changing the algorithm's structure.
Template pattern works using 'the Hollywood principle' from the base class point of view: 'Don't call us, we'll call you' Template pattern works using 'the Hollywood principle' from the base class point of view: 'Don't call us, we'll call you'
Class diagram:
legend:
* \# is for protected method
* Italic is for abstract method
![alt text](https://github.com/MihaiTheCoder/BehavioralPatterns/blob/master/BehavioralPatternsDiagrams/TemplateMethodPattern/TemplateMethodPatternClassDiagram.PNG "Template method pattern class diagram")
Sequence diagram:
![alt text](https://github.com/MihaiTheCoder/BehavioralPatterns/blob/master/BehavioralPatternsDiagrams/TemplateMethodPattern/TemplateMethodPatternSequenceDiagram.PNG "Template method pattern sequence diagram")
### b. When to use Template method pattern ### b. When to use Template method pattern
* Let subclasses implement (through method overriding) behavior that can vary. * Let subclasses implement (through method overriding) behavior that can vary.
* Avoid duplication in the code: the general workflow structure is implemented once in the abstract class's algorithm, and necessary variations are implemented in each of the subclasses. * Avoid duplication in the code: the general workflow structure is implemented once in the abstract class's algorithm, and necessary variations are implemented in each of the subclasses.