Title: RE: JESS: Re: Start on Knowledge Based System
Someone asked, so here's a link to the most current ASL spec i could find.  According to a gentleman and KC, it is the most recent.  There are efforts underway to create an Executable UML, which is akin to ASL.  That is happening through OMG, i believe.
 
Cheers,
mark
 
http://www.kc.com/html/download.html
 
PS - i hope this isn't too far off topic.
-----Original Message-----
From: Scott Lewis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 13, 2001 10:34 AM
To: 'Mark Lilly'
Subject: RE: JESS: Re: Start on Knowledge Based System

I would be interested in the links about ASL. Thanks, Mark.
-----Original Message-----
From: Mark Lilly [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 13, 2001 1:15 PM
To: 'Rich Halsey'; Jess
Subject: RE: JESS: Re: Start on Knowledge Based System

Hi Rich et al, 

I saw some of your earlier posts, and you've mentioned KADS a number of times.  I looked into it.

<cut>

I need rules (to answer your first question), b/c i have to deal with a lot of raw data (on customers, on system availability, on billing history, on real-time usage etc.) and i want to act upon that data in an informed and knowledgable way.

<cut>

> Q2. OK, then how do we start the project ?

> 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.

OK.

<cut>

> 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.

So, here's what i found on KADS:
Three levels of analysis are distinguished:
1. The Process Level has a Process Model, which identifies tasks and data flows in the domain.
2. The System Level has the Co-operation Model, which describes how the system interacts with external 'agents' and how internal 'agents' interact with each other.

3. The Expertise Level has the Expertise Model with four sub-layers:
--Domain Layer - static domain knowledge.
--Inference Layer - what inferences can be made from the domain knowledge.
--Task Later - how to apply the knowledge in the above layers to problem-solving.
--Strategic Layer - how to select appropriate problem-solving tasks during execution.

It seems that one can use UML for much of this, but what is the best way to model all the models that need modeling?  Does one start with the Process Level and work down?  How should all this correalate with other modeling efforts, say for non-rules based Object and Information Models?

Fun discussion.  Another beer please.... :-)

mark

http://issco-www.unige.ch/ewg95/node103.html

PS - has anyone looked at the Action Semantic Language?  It's a modeling language based on UML that gives one a much richer set of obejcts and grammar to model with.  It is nearly a full fledged prototypic programming language.  I have references in anyone is interested.


> 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]
> ---------------------------------------------------------------------
>

Reply via email to