Software engineering textbooks and research papers describe many software design and programming best practices (or anti-patterns), which are usually geared towards high-level issues (e.g., system decomposition or naming conventions) or towards control and data flow organization for specific types of operations (e.g., design patterns) [1]}, [2]}, [3]}.
In addition, companies and open source communities have their own coding standards, informed by their experiences.
However, there are no such prescribed solutions or best practices when it comes to implementing business rules.
Existing literature offers guidance on how to formulate these rules, but not on how to implement them [4]}, [5]}.
