[Modeling] Modeling an Agent Class- register your opinion
Fri, 20 Jun 2003 11:09:52 +0200
> 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.