-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Morris Sent: Wednesday, December 29, 2004 2:28 PM To: [email protected] Subject: RE: [Andromda-user] Supported CASE tools
Daniel's compilation is fantastic and, having spent way too many hours myself on trying to figure this all out, I know it represents a lot of work. MDA tool interoperability is a patchwork nightmare and anything that can be done to improve the situation is great. (If anyone knows an OMG member or MDA tool vendor, please give them a swift kick in the, umm, shins for me.) The main reason that people are going to use the list is to see if their favorite modeling tool works or find one that does work, so those should be at the top of the list. Tools that are known not to work should be clearly identified as such and probably be put in a separate section at the bottom. For example, ArgoUML has a little flag saying that UML 1.3 might be an issue, but, as far as I know, the fact that it only does UML 1.3 means it has no chance of working with AndroMDA until one or the other is enhanced. It certainly has never worked in any of my testing. On the other hand, Sparx Enterprise Architect has the little UML 1.3 warning sign, but the comments seem to imply that it supports UML 1.4 and might work with AndroMDA. As Matthias suggested, writeups on how to use any of the modeling tools which work with AndroMDA, other than MagicDraw, would be *very* useful. For example, the matrix seems to imply that Poseidon still works, but when any of the samples are opened with it, the link to the AndroMDA profile is dropped and all attributes silently lose their types. If there's a way to get Poseidon to work with AndroMDA, it'd be great to know. [CB] There are plenty of users that use Poseidon with AndroMDA (search the list archive I'm sure you'll find something). You can import the andromda-profile into Poseidon (or you can create stereotypes, types and tagged values yourself). The samples on the other hand will need to be opened with Magic Draw because of what you say: the types will be lost since Poseidon doesn't have the concept of modules (the diagrams will also be lost as well since Magic Draw does not yet support the UML diagram interchange). Tom p.s. ArgoUML does support stereotypes -- not that it makes any difference in whether it'll work with AndroMDA. [CB] ArgoUML can/will work if someone decides to implement some UML 1.3 metafacades (not that difficult of a task). ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
