#1113 Link uml-reverse-mapper created class diagrams to readme, where needed
This commit is contained in:
@ -19,14 +19,6 @@ candidate, from the candidate object that it is matched against. As well as its
|
||||
usefulness in selection, it is also valuable for validation and for building to
|
||||
order.
|
||||
|
||||

|
||||
|
||||
## Applicability
|
||||
Use the Specification pattern when
|
||||
|
||||
* You need to select a subset of objects based on some criteria, and to refresh the selection at various times.
|
||||
* You need to check that only suitable objects are used for a certain role (validation).
|
||||
|
||||
## Explanation
|
||||
|
||||
Real world example
|
||||
@ -190,6 +182,15 @@ Instead, we just create an instance of ``AbstractSelector`` "on the spot", using
|
||||
| Composite Specification | There are a lot of selection criteria that can be combined in multiple ways, hence it is not feasible to create a class for each selector | + Very flexible, without requiring many specialized classes | - Somewhat more difficult to comprehend |
|
||||
| | | + Supports logical operations | - You still need to create the base classes used as leaves |
|
||||
|
||||
## Class diagram
|
||||

|
||||
|
||||
## Applicability
|
||||
Use the Specification pattern when
|
||||
|
||||
* You need to select a subset of objects based on some criteria, and to refresh the selection at various times.
|
||||
* You need to check that only suitable objects are used for a certain role (validation).
|
||||
|
||||
## Related patterns
|
||||
|
||||
* Repository
|
||||
|
Reference in New Issue
Block a user