[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: XMI reality check
Yes the alphaWorks technology. The work was last touched around 6/2000. The biggest problem we had was the size of the XMI. The UML model was 40 Meg and the resultant XMI was over 100 Meg. As you can imagine this was a stress test for the parsers and XSLT. Exchanging XMI with different tools, I didn't personally, but this was an action item for others on the team. Mega said they would be able to but I never heard back. Someone was to try with GDPro but I don't recall the results. The OAG team had chosen Rational (they had to choose one) as their development tool and left it up to other tools to import XMI or RoseMDL. As I recall XMI's stuff preserved the model graphics perfectly. ________________________________________________________________ Kurt Kanaskie Lucent Technologies kkanaskie@lucent.com (610) 712-3096 -----Original Message----- From: Bob Haugen [mailto:linkage@interaccess.com] Sent: Friday, March 16, 2001 2:08 PM To: Kanaskie, Kurt A (Kurt); 'Jim Clark'; Welsh, David Cc: Race Bannon; 'ebXML-BP@llists.ebxml.org'; 'ebXML-CCBP-Analysis (E-mail)' Subject: RE: XMI reality check Kurt, Thanks a lot. I assume this was IBM's alphaworks XMI toolkit? http://www.alphaworks.ibm.com/tech/xmitoolkit Did you try exchanging XMI models between different UML tools? >IBM's toolkit was also better at preserving the model graphics when imported. Did that mean, preserving model graphics thru XMI was not very good even with the IBM toolkit? -Bob Haugen -----Original Message----- From: Kanaskie, Kurt A (Kurt) [SMTP:kkanaskie@lucent.com] Sent: Friday, March 16, 2001 12:26 PM To: 'Jim Clark'; Welsh, David Cc: Race Bannon; 'Bob Haugen'; 'ebXML-BP@llists.ebxml.org'; 'ebXML-CCBP-Analysis (E-mail)' Subject: RE: XMI reality check All, I have had some experience with XMI (Unisys's plug in for Rational and IBM's XMI toolkit). I agree XMI is ugly but it was intended for machine to machine exchange of models, not human readability. I have found IBM's version to be more complete that Unisys's for what I was trying to do. IBM's toolkit was also better at preserving the model graphics when imported. I successfully used XSLT on the XMI from a UML model, based on Booch's meta-model for XML Schema, to generate a human readable XML DTD. This approach is being finalized by OAG as their method of generating DTDs from a UML model of all of their BODs (170+). Thus I believe that XMI can be used to generate XML instances of business processes modeled in UML. However, this approach will require some consistency changes to the UML version of the Spec Schema. Another benefit of XMI is to generate meta-model instance DTDs that can be used to check model instance UML models. The stock tools to generate these DTDs are also quite ugly and not human friendly, but serve the purpose. Regards, ________________________________________________________________ Kurt Kanaskie Lucent Technologies kkanaskie@lucent.com (610) 712-3096
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC