[Modeling] Comments on interaction diagram modeling doc

Lin Padgham linpa@goanna.cs.rmit.edu.au
Thu, 20 Mar 2003 10:04:06 +1100

Actually we mostly have used the term "functionality" rather than
role. But it seems fairly close to what other methodologies call role,
so we have sometimes (earlier) used that and have been considering
whether to go back to that for consistency with others.

What does seem to be becoming clear though is that there isn't a
notion of "agent type" in AUML. Certainly we use this heavily. I'm not
really sure whether your notion of role is essentially
equivalent. Possibly it is and its just a metter of terminology...


> On 3/19/03 8:06 AM, "Lin Padgham" indited:
> > What seems to be missing here, which is what we use most, is to give
> > the agent type - not the instance name of an agent, but a type of
> > agent. So we might have a "shop assistant" agent type, with roles that
> > include "sales transaction", "customer welcoming", "product queries",
> > etc. These roles are deliberately quite small and specific (and relate
> > to particular goals and functionalities), whereas things like
> > "employee" are more like what we would have as agent types. I don't
> > think we have evenr found a need to use specific agent instance
> > identifiers, though sometimes we do indicate that there *are* multiple
> > instances and separate these out in some way in the diagrams.
> Hmmm.  We might have a difference in our definitions of "role", then.  In
> UML, the role would be "shop assistant" -- and in order to play that role,
> the agents must be able to perform various services, such as  "sales
> transaction", "customer welcoming", "product queries", etc.   Having said
> that, there is no reason that you could not refer to  "customer welcoming"
> as class with a set of interactive behavior that supports such a role --
> even if it were a single-behavior role.  In this case, you would declaring
> that the shop assistant is an aggregate of other "small and specific" roles
> you mention.  Such aggregation is important in role formation.   Does that
> work?
> Regards,
> Jim
> _______________________________________________
> Modeling mailing list
> Modeling@www.fipa.org
> http://fipa.org/mailman/listinfo/modeling