[Modeling] Modeling an Agent Class- register your opinion
Fri, 20 Jun 2003 12:28:28 +0200
> Hi, Joaquin,
> It is true that we can implement everything in the OO
> paradigm and model everything in UML, etc. However, in my
> opinion, what is important is how to model and implement the
> model in a better way
I'm completely agree!!
>. Can we model certain systems in an
> agent-oriented approach better than OO approach?
This is the key point. I think so.
But it is not because Agent-Orientation, but because role modelling.
It fits perfectly with Open Systems where the system behaviour
changes over time.
> ----- Original Message -----
> From: "Joaquin Peņa" <firstname.lastname@example.org>
> To: "'Dr. Hong Zhu'" <email@example.com>; "'Wagner, G.R.'"
> <G.R.Wagner@tm.tue.nl>; "'James Odell '"
> <firstname.lastname@example.org>; "'ModelingTC '" <email@example.com>
> Sent: Friday, June 20, 2003 10:09 AM
> Subject: RE: [Modeling] Modeling an Agent Class- register your opinion
> > Hi Hong,
> > >
> > > Traditional object class is weak, and therefore, we need
> to extend
> > > it. So, I introduced the concept of caste (which is called agent
> > > class in this mailing list). Caste has the features of dynamic
> > > classification and multiple classification, and new part-whole
> > > relations. In my caste diagrams, we can specify 'role'
> change paths
> > > to represent the dynamic change of classifications, etc.
> > >
> > > > The solution, as I've commented before, is
> > > > to model such transient relations using design patterns
> > > that allow us
> > > > to decouple classes and interaction between them.
> > > >
> > >
> > > In my opinion, design patterns are at a lower level of
> > > than modelling. Moreover, if we can have a stronger language, we
> > > might be able to solve such implementation problems more
> > > straightforwardly.
> > ight, they are low level because I speak about how to
> implement agents
> > with current programming languages.
> > I don't think we need a modification of OO paradigm (new class
> > diagrams, relations, etc) since we have role modelling.
> Then, when we
> > perform the design stage, we have to translate role models to class
> > diagrams to implement them. If we continue representing roles in oo
> > diagrams, the implementation is going to be difficult using current
> > languages such as JAVA.
> > Joaquin Peņa
> > _______________________________________________
> > Modeling mailing list
> > Modeling@www.fipa.org http://fipa.org/mailman/listinfo/modeling