The responsibility of this method is to apply the business rule (specification) on the object in question and return a boolean result. This method is the engine of specification pattern. Each segregated business rule is called Specification.Įach specification inherits the abstract CompositeSpecification class which defines one abstract method called IsSatisfiedBy. To put it simply, business rules are segregated based on the Single responsibility principle (SRP) and chained or composed using boolean operands (AND, OR or NOT) to achieve the desired result. Specification pattern as per the definition from Wikipedia, is a particular software design pattern, whereby business rules can be recombined by chaining the business rules together using boolean logic. Major benefits of the specification patterns include reusability, maintainability, loose coupling of business rules from the business objects, readability and easy testing. This article will also help beginners in understanding the specification pattern and how to implement it in practice.
In this article, we are going to explore the classic specification pattern and implement it in order to compose the LINQ queries, and also non-LINQ queries.
