Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "MDT-UML2-Tool-Compatibility"
(→List of UML2-compatible UML Tools) |
|||
Line 61: | Line 61: | ||
| No | | No | ||
| EPL | | EPL | ||
+ | |[http://www.mia-software.com/produits/mia-studio/ Mia-Studio] | ||
+ | | Yes | ||
+ | | No | ||
+ | | Yes | ||
+ | | Commercial | ||
|- | |- | ||
|[http://www.moskitt.org/eng/ MOSKitt] | |[http://www.moskitt.org/eng/ MOSKitt] |
Revision as of 04:11, 2 May 2011
This topic is a place to gather information about UML2 compatibility in open source and commercial UML/MDA products.
List of UML2-compatible UML Tools
Tool | Native | Modeling | Code Generation | License | Tool Version | UML2 Version | Notes | ||
---|---|---|---|---|---|---|---|---|---|
Acceleo | Yes | No | Yes | EPL | 3.0 | metamodel-driven, not UML specific | |||
AndroMDA | Yes | No | Yes | BSD | 3.4-SNAPSHOT | 3.1.0 | maven based MDA tool | ||
ArgoUML | Yes | Yes | Yes | EPL | 0.32 | 3.1.1 | prereleases yet (stable for UML1.4 only) | ||
Eclipse UML2 Tools | Yes | Yes | No | EPL | |||||
Enterprise Architect | No | Yes | Yes | Commercial | |||||
IBM RSM/RSA | No | Yes | Yes | Commercial | |||||
MagicDraw UML | No | Yes | Yes | Commercial | |||||
MDT Papyrus | Yes | Yes | No | EPL | Mia-Studio | Yes | No | Yes | Commercial |
MOSKitt | Yes | Yes | No | EPL | |||||
Omondo EclipseUML | Yes | Yes | Yes | No | Commercial | ||||
openArchitectureWare | Yes | No | Yes | EPL | metamodel-driven, not UML specific | ||||
Papyrus UML | Yes | Yes | Yes | EPL | |||||
Soyatec eUML2 | Yes | Yes | Yes | Commercial | |||||
Taylor MDA | Yes | Yes | Yes | LGPL | |||||
TextUML Toolkit | Yes | Yes* | No | EPL | 1.7 | 2.5 & 3.* | Uses a textual notation | ||
TOPCASED UML | Yes | Yes | Yes | EPL |
Description of table columns
Follows a description of the less obvious column names:
- Native - whether the tool uses UML2 as its native format. If UML2 is not natively supported, that means the user has to perform some sort of conversion step (e.g. import/export) in order for the tool to accept/provide UML2-compatible models.
- Modeling - whether the tool supports modeling.
- Code generation - whether the tool supports code generation.
- Tool version - version of the tool when verified. If the tool has not been verified yet, it will be empty.
- UML2 version - version of UML2 adopted by the tool when verified.
- Notes - any quirks or comments about UML2 support in the tool.