Dear all! I hope you are doing well! Thanks for this new version! Here are some thoughts and question... Why have an attribute "sourceAnchor" in "Entity", why not use a Decorator to add such "external" data? The role/concept of the entity named "Association" is confusing with respect to "traditional" UML where an association is a relationship between two or more entities, why not categorise the sub-concepts of "Invocation", "Access", "Reference" as "MethodConstituent" or "BehaviouralEntityConstituent"? The attribute "candidates" seems to me very much Smalltalk oriented :-) I agree it is more general but... ;-) Why are modifiers in "NamedEntity" represented as String*, why not use classes? I understand the rationale for putting back references, such as "belongsTo" in "ScopableEntity" but it feels to me more an implementation choice to ease navigating the models rather than a true concept that must be represented in the models. (Also, it may make it harder to build models.) Why is there a "GlobalVariable" entity? Why don't the "BehaviouralEntity" have a "returnType"? Cheers! Yann-Gael Adrian Kuhn wrote: -- Yann-Gaël Guéhéneuc Ph.D. et ing. jr. / Ph.D. and jr. eng. Professeur adjoint / Assistant professor DIRO, Université de Montréal 1-514-343-6782 (Téléphone / Phone) C.P. 6128, succursale Centre-Ville 1-514-343-5834 (Télécopie / Fax) Montréal, QC, H3C 3J7, Canada www.ptidej.net

Adrian Kuhn wrote: What is the point of above/below in Association? The only thing I can think of is an extra abstraction for all those different types of "from/to" in the subclasses, but in that case the type and opposite seems very strange so I guess it's something else?