Well it seems that IBM believes in business rules too. I was reading SOMA: A method for developing service-oriented solutions which I found thanks to Eric Roch’s post on IBM’s SOA Methodology anda couple of things struck me:
- Business rules get called out explicitly both in the meta model Eric shows and in the overall flow. Personally I would have liked to see Decision called out but Business Rules and Policies are a good start.
- Rule services (what I call Decision Services) get a mention as a design artifact and a way to collect rules into something implementable
- A rule engine appears in some of the implementation diagrams (like this one)
- An obvious Decision Services (Validate Payment) shows up in the worked example