Content deleted Content added
m remove unecessary comment |
Described a compelling use-case for the specification pattern |
||
Line 5:
A specification pattern outlines a business rule that is combinable with other business rules. In this pattern, a unit of business logic inherits its functionality from the abstract aggregate Composite Specification class. The Composite Specification class has one function called IsSatisfiedBy that returns a boolean value. After instantiation, the specification is "chained" with other specifications, making new specifications easily maintainable, yet highly customizable business logic. Furthermore, upon instantiation the business logic may, through method invocation or [[inversion of control]], have its state altered in order to become a delegate of other classes such as a persistence repository.
As a consequence of performing runtime composition of high-level business/___domain logic, the Specification pattern is a convenient tool for converting ad-hoc user search criteria into low level logic to be processed by repositories. Since a specification is an encapsulation of logic in a reusable form it is very simple to thoroughly unit test, and when used in this context also an implementation of the humble object pattern.
== Code examples ==
| |||