[Modeling] Class Diagram Specification

[Wagner, G.R.]

> Marc-Philippe wrote:
> "the first level is the one, we always consider
> knowledge, acquaintances, roles, groups, protocols, etc. and we have a
> second level where we describe those elements in a 
> "computable" manner,
> see the example above, the first level is at design level, the second
> one is at implementation level, and above all, we need to give recipes
> to help designers moving from the first level to the second one."
> 
> and in level 1, we deal with roles, groups, etc. And to this level I 
> have pointed in my previous messages.
> 
> AUML agent diagram is in level 2, because we have implementation 
> consideration.
> 
> I hope it is clear now :)
 
Yes, it's clear, but you should better read my message before 
you reply to it: at both of your levels (and in general, we
distinguish between 3 levels, as in the MDA), we can/should
use UML class diagrams! UML class diagrams are a powerful
language for conceptual modeling of real world domains that
include agents and objects.

Do you really suppose that you can come up with a better 
conceptual modeling language than UML class diagrams (or
some extension of it)? 

-Gerd