Hmmm...Data Driven Business Rule Implementation

The problem:  Complex object hierarchy, many complex business rules

The bigger problem:  Rules change all the time, and they are different depending on how/where the app is run.

A bigger problem:  There exist multiple levels of rules - that may or may not conflict.

So, how would we do this - well, there are many possibilities - some of which I know have already been implemented.   But, from what I have seen, I think I have a better way. 

On that note, I think I'm going to create a complete Business Rules Application Block that would allow you to segment your business rules from the rest of your application.  It will also allow you to data drive when and how they fire and what happens rule exceptions occur.  Of course, it needs to be service oriented and scaleable - ready for the enterprise – good for web or larger smart client applications.  I need to make sure that we can consume virtually any object hierarchy - probably through some abstraction of the object and XML.  Plug this baby in, create some rules - and away you go.  Couple this with a Visual Studio.NET Add-In that would help facilitate the creation and maintenance of the rules – and you have a kick ass utility.

This is a problem I’m solving in another area of my life… but the way I see it, this is a big problem and I think there needs to be a big, generic, and re-usable solution – which may not be the end result of how I’m trying to solve the same problem in my day job.

Now, where should I start – well, a model of course… away I go…I’m inspired…check back with me in a couple of weeks…I may have something. 

(Lately, I’ve had a crap load of “block” ideas…)