Hello to all,
I am about to embark on a little crusade out here that should prove
to be informative to me. I have already worked in the Business Rules and
Constraint Programming environment three times within the last year
and I was totally "underwhelmed" by the (very well-paid) "experts"
that I encountered. I NEVER saw any type of defined "process" in any
of the projects. Ironically, I never claimed to have any expertise
in the Business Rules area but I was able to discover 3 colossal design
flaws in a business rules system (for which I was promptly let go).
My goal for this little crusade will be to develop a technique using
KADS (for Enterprise task analysis),an Object-Oriented representation of
Requirements,(David Harel's) StateCharts, EPC (Event-driven Process
Chain
Modeling from SAP),and (Jacobson) Use Cases to get to the point where a
Rule Set may be constructed. The technique will provide for traceability
all the way from Requirements and Business Policy to the rules
themselves.
It will also provide for modeling the side-effects between rules and
facts.
Jess (v50) will be the target inference engine.
While this is simply a brief description of my little crusade, I will
also
be using the "GUIDE" rules document and Ron Ross's method documentation
as a source of questions and answers.
Should I sign this e-mail as the "Don Quixote of Business Rules", i.e.,
has anybody been there and seen the same problems that I encountered out
there amongst the Rules Swamis ?
Rich Halsey
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list. List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
