Hi,
I am copying this to the entire group so that we can get some constructive
feedback. This is intended to simply
to present a beginners point-of-view (I consider myself to be a rules
mechanic). I am going to assume that we are
all in a large meeting where we may freely ask questions.
Q1. Why do we need rules for this project ?
Answer - The application may have several parts operating concurrently (?)
across a network and the data in each
part may have an impact on the control flow of the other parts. If the data
is asserted as facts in the Rete (network),
then any changes made to this data will be observable to conditions that are
testing. This is the advantage of using
JESS.
Q2. OK, then how do we start the project ?
Answer - Assuming that the business case has been made to start the project
and we have some idea of what the
business people want, i.e., how they intend to interact with the system, we
will begin by looking at three fundamental
analysis models: (1) the integrated business/IT system process using O-O
activity diagrams, (2) a data model using
simple E-R diagrams, and (3) a rules matrix to explain how the rules
interact with both the data model and the process
model. The rules matrix is ultimately partitioned across the sub-systems in
the application and layered into increasing
detail (from justification to responsibility to code). The process and the
data models are ultimately combined into
an Object model (the data being encapsulated and the behaviour combined). By
now, this is starting to look like
the classic O-O project except that the rules may be modeled using decision
tables. This gives us the opportunity
to check for completeness. In effect, we have two separate paths of
development: the classic O-O path and the
rules path. Ultimately, these paths must combine for integration, testing,
roll-out, etc., etc..
Q3. Should we hire some rules consultants ?
Answer - I thought that you wanted the pleasure of learning this. Homework
for the next meeting is to find
and investigate KADS (Knowledge Acquisition and Document Structuring) which
has some interesting ideas.
Any questions ? OK - see you at the next meeting !
Rich Halsey
----- Original Message -----
From: "Larry Loh" <[EMAIL PROTECTED]>
To: "Jess" <[EMAIL PROTECTED]>
Sent: Thursday, March 08, 2001 2:15 AM
Subject: JESS: Start on Knowledge Based System
> Hi I am new to Jess. I need to create a new knowledge based system to help
> car buyers make decision advice on the types of car that they would like
> buying by providing advice. Can anyone give me advise on how to start.
>
>
> ---------------------------------------------------------------------
> 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]
> ---------------------------------------------------------------------
>
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
