Good golly Miss Polly
"Watch your phraseology"
(Mayor Shinn in -Music Man)
Rudolph's reply was highly beneficial.
It addresses the use of
Rule Based Systems in the sense of:
Production Logic
-vs-
Procedural Logic.
The current trend of
Business Logic/Rule separation
in enterprise commercial systems
does not imply either production or procedural logic.
It is the -separation/isolation- of the
business logic from program logic.
Most of the business rule systems
that I am aware of use procedural logic
and a COBOLish pseudo code.
e.g.
If account-balance < 10% of Maximum
then withdrawable-amount is 50% of Maximum.
The purpose being:
1.Business rules and logic are exposed-
not hidden/buried in numerous programs.
2.Non-programmers can maintain business logic.
Introduction of production logic into
the "business" environment
brings up the question as to which is easier
to teach/learn...production or procedural.
How would one go about
teaching a Loan Officer
production logic????
It takes 6 months to teach
a procedural programmer OO-programming.
I'm certainly no expert on Jess/Clips programming.
Lurking on the forum....
I do see a lot of LHS/RHS issues.
i.e. procedural logic thinking "mistakes"
My guess would be....procedural is more -intuitive-
On the other hand....did I produce that assertion.....
...enough....back to work(production)
David
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
