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

Update readme

Browse Source
This commit is contained in:
Petrutiu Mihai
2016-07-13 13:42:11 +03:00
parent e5b5fc1a51
commit 7aa555313b
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@@ -309,12 +309,19 @@ If we want to implement this using state pattern, we would need to make a new cl
* AcceptanceTestsPassed - moves user story from state Resolved to state Closed * AcceptanceTestsPassed - moves user story from state Resolved to state Closed
* Motivational example class: ScrumExample.ScrumMotivationalExample * Motivational example class: ScrumExample.ScrumMotivationalExample
8. Strategy pattern 8. Strategy pattern
------------------ ------------------
### a. Pattern description ### a. Pattern description
Strategy pattern (also known as the policy pattern) is a software design pattern that enables an algorithm's behavior to be selected at runtime.
The strategy pattern defines a family of algorithms, encapsulates each algorithm, and makes the algorithms interchangeable within that family.
### b. When to use Strategy pattern ### b. When to use Strategy pattern
* Classical thing to say: Whenever you start to use a switch statement you should ask yourself whether you can use Strategy Pattern instead.
* When you want to externalize part of the algorithm
### c. Actors ### c. Actors
### d. Pitfalls ### d. Pitfalls
### e. Flavors ### e. Flavors
### f. Examples ### f. Examples