Hi Binoy:

What is your current view of:

$DEMETER_HOME/demeter-method/uml-syntax-discussion           

What happens to a cardinality 3..4?

More below.

-- Karl

>From binoy@ccs.neu.edu Wed Sep 17 22:10:28 1997
>From: Binoy Samuel <binoy@ccs.neu.edu>
>CC: dem@ccs.neu.edu
>Subject: Re: UML and cds in AP Studio
>
>Karl Lieberherr wrote:
>> 
>> We want to be able to represent any kind of Demeter/Java cd
>> as a UML class diagram: you describe below how to do that.
>> 
>> On the other hand, we want to provide support for "most" features
>> of the UML class diagram notation. How does the translation
>> look in the other direction? For example, we could inherit
>> from a non-abstract class in UML.
>An inheritance from a non-abstract class would be achieved using an
>"extends" edge in ApStudio. This would translate to something like
>	A = .. *extends* B.  (B is the non-abstract class).

Are the traversals working through such edges?

>
>> Or we can have undirected edges in UML.
>The UML diagrams that ApStudio supports is only what a demjava class
>dictionary handles. So there would be _no_ undirected edges in the
>subset of UML understood by ApStudio.
>

Ok.

>> 
>> How well debugged is the translation from cds to UML at this point?
>> This is certainly the more important direction.
>The cd-uml part is pretty well tested. 
> 
>> Which features do we currently want to exclude from UML so that
>> if we draw a UML picture with AP Studio, we create the cd
>> and we read the cd back in, we get a graph which is isomorphic
>> to the original one?
>Right now we are going bottom-up ;-) Include those features that are
>used in a class dictionary.
>
It is important that we support standards like UML in there generality
in the long run. Otherwise people think that we have only a toy OO model.

>> 
>> -- Karl
>
>-binoy
>