In EA, the implied types are saved correctly in an XMI extensions element, but other tools are not expected to interpret or use these vendor-specific extensions. If you ALWAYS define every type used in your model, including attribute types such as these, then use the defined type when creating class attributes, we should get a better model. So, when exporting, both of these tools create new data types for these "implicit" names. This looks OK in a diagram, but is an incomplete model. I assume that BOUML (and EA) allow you to simply enter the text name of an attribute data type as part of defining a class. If you look at the bottom of the XMI file from BOUML, you see a list of DataType definitions, e.g. I do not have EA license, so cannot test. I think that both tools and models can be fixed with a simple change to best practice.
EA exports valid XMI, but the UML model is not interoperable with other tools. Most of the EA models that I've looked at in XMI have a similar problem. The better fix would be to change the model, and hopefully avoid this export error from BOUML at the same time. this is invalid, it must be "packagedElement". At the bottom of the file, there is a list of DataTypes contained using the xml element "ownedMember". I was able to make a quick text edit to the file so that it can be imported by both eclipse 3.6 and RSA 8. Thus, I could open your UML 2.1 xmi file in eclipse 3.6 and RSA 8, however UML 2.2 would be preferred.īut there is a technical error in both of these XMI files from BOUML that must be fixed by that vendor. No UML elements recognized (only UML 2.1, 2.1.1, 2.1.2 and 2.2 are supported) Problem loading file openEHR_102_RM_DT_xmi2.3.xmi. So, your posted UML 2.3 model cannot be imported by RSA 8. Here is what he said (I tried to upload the XMI files here, but. Ok, I have more information from an OMG XMI expert who has analysed the BOUML XMI. Note that when you import under Bouml an aggregation/composition through an XMI file exported by EA, Bouml writes the sign on the right side It is very strange but EA draws the aggregation/composition sign on the wrong side on the class diagrams (independently of the fact you imported or not a model to define this aggregation/composition) I see you set the toggle Generate for Eclipse (aggregation set on other relation side) to export with Bouml, don't do that.
To avoid problems when importing under EA you have to not use attributes typed by a class, this means you have to use relations in these casesĪs you can see my XMI2 export has several options to take into account the specificities of the other tools I was able to see, but there are limits, I will not add an option to say the file is exported by EA however, if I modify the file to remove and the xmi:Extension to not say to EA it is a EA file, then I import this modified file, the attribute name of PERSON doesn't have a type.if I import the XMI you sent to me, all is ok and the attribute name of PERSON as the type PERSON_NAME.
#Bouml aggregation trial#
Sorry, I didn't know why but I looked at the extension part, anyway, using my trial version of EA :
0 kommentar(er)
