PUBLIC MARKS from amyrussell with tag "business rules"

The Fourth Commandment was best summarized by Scott W. Ambler in Agile Modeling. He hit every nail quite nicely. Business Rules are: Written and explicit. Written in plain language. Are built on facts, and facts should build on concepts as represented by terms. Guide and influence behavior in desired ways. Are accessible to authorized parties (e.g. collective ownership must be single sourced (no links, no dependencies, no references, etc) .Are specified directly by those people who have relevant knowledge (e.g. active stakeholder participation.) Have to be managed.

In explaining this pattern, I wanted to take a step back and explain where and how OO and BRE's intersect. To start with, this excellent post over at Mark Proctor's blog makes the following statement:

While JBoss Rules 3.0.x has been a great step from its predecessor (the unfortunately named Drools) -- providing a rule editing environment, universal and existential quantifiers (the "not" A is the same as "for all" ~A), and Domain Specific Languages (DSL's) -- there were still a few things missing. I've watched the progress on 3.1 with barely contained excitement and impatience, but the result has been worth the wait. The 3.1 M1 drop contains operations on collections: