Profiles eCore <-> UML [message #624923] |
Thu, 20 September 2007 15:02 |
Stefan Kuhn Messages: 355 Registered: July 2009 |
Senior Member |
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi, I was wondering how profiles defined in UML and eCore are connected
or differ from each other.
I noticed 2 major differences when definining a profile:
the profile in UML imports UML.metamodel.uml.
the profile in eCore imports UML.ecore
what are the differences between both metamodels?
Why is an association class needed in the profile definition? When I
compare both serialization:
UML:
<packagedElement xmi:type="uml:Stereotype" xmi:id="(...)**2"
name="Element">
<ownedAttribute xmi:id="(...)**3" name="base_Class"
visibility="private" association="(...)**1">
<type xmi:type="uml:Class"
href="pathmap://UML_METAMODELS/UML.metamodel.uml#Class"/>
</ownedAttribute>
</packagedElement>
And the association class:
<packagedElement xmi:type="uml:Extension" xmi:id="(...)**1" name=""
memberEnd="(...)**4 (...)**3">
<ownedEnd xmi:type="uml:ExtensionEnd" xmi:id="(...)**4"
name="extension_" visibility="private" type="(...)**2"
aggregation="composite" association="(...)**1">
<upperValue xmi:type="uml:LiteralUnlimitedNatural" xmi:id="(...)"
name="" value="1"/>
<lowerValue xmi:type="uml:LiteralInteger" xmi:id="(...)" name=""/>
</ownedEnd>
</packagedElement>
Ecore seems much more readable, and I don't see a benefit of the UML
definition since there's no lose of information in eCore:
<eClassifiers xsi:type="ecore:EClass" name="Element">
<eStructuralFeatures xsi:type="ecore:EReference" name="base_Class"
ordered="false"
lowerBound="1" eType="ecore:EClass
platform:/plugin/org.eclipse.uml2.uml/model/UML.ecore#//Clas s "/>
</eClassifiers>
thanks
- -stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG8otuIYVWjMSpDwwRAmFIAKD1V6SkblABNo2wgabUl65w68JOrQCf djah
A+I6rFVCzIYZ3BC2CqudXj4=
=Ol5Q
-----END PGP SIGNATURE-----
|
|
|
Powered by
FUDForum. Page generated in 0.02791 seconds