[Modeling] Modeling an Agent Class- register your opinion

[Joaquin Peña]

> 
> May I ask why it is not because agent-orientation? Are you 
> suggesting that role modelling is not agent-orientation?
> 

Sure, Role Modelling was first and in AOSE it has been taking as the
basis of the analysis stage.

Joaquin Peña

> Hong
> 
> ----- Original Message ----- 
> From: "Joaquin Peña" <joaquinp@us.es>
> To: "'Dr. Hong Zhu'" <hzhu@brookes.ac.uk>; "'Wagner, G.R.'" 
> <G.R.Wagner@tm.tue.nl>; "'James Odell '" 
> <email@jamesodell.com>; "'ModelingTC '" <modeling@fipa.org>
> Sent: Friday, June 20, 2003 11:28 AM
> Subject: RE: [Modeling] Modeling an Agent Class- register your opinion
> 
> 
> > >
> > > 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.
> >
> > > Hong
> > >
> >
> >
> >
> >
> >
> > > ----- Original Message -----
> > > From: "Joaquin Peña" <joaquinp@us.es>
> > > To: "'Dr. Hong Zhu'" <hzhu@brookes.ac.uk>; "'Wagner, G.R.'"
> > > <G.R.Wagner@tm.tue.nl>; "'James Odell '"
> > > <email@jamesodell.com>; "'ModelingTC '" <modeling@fipa.org>
> > > 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
> > > abstraction
> > > > > 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
> > > >
> > > >
> > >
> >
> >
> >
> 
> _______________________________________________
> Modeling mailing list
> Modeling@www.fipa.org
> http://fipa.org/mailman/listinfo/modeling
>