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.
MDT-UML2-Tool-Compatibility
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 | |
| AgileJ StructureViews | Yes | No | No | Commercial | 1.7.7 | reverse engineered class diagrams only | |
| 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) |
| Cloudfier | Yes | Yes* | Yes** | EPL/AGPL | - | 5.0 | *Uses a textual notation; **Supports both codegen and model interpretation |
| Eclipse UML2 Tools | Yes | Yes | No | EPL | |||
| Enterprise Architect | No | Yes | Yes | Commercial | |||
| GenMyModel | Yes | Yes | Yes | Commercial | - | 4.0 | |
| IBM RSM/RSA | No | Yes | Yes | Commercial | |||
| MagicDraw UML | No | Yes | Yes | Commercial | |||
| MDT Papyrus | Yes | Yes | Yes | EPL | |||
| Mia-Studio | Yes | No | Yes | Commercial | |||
| MOSKitt | Yes | Yes | No | EPL | |||
| openArchitectureWare | Yes | No | Yes | EPL | metamodel-driven, not UML specific | ||
| Soyatec eUML2 | Yes | Yes | Yes | Commercial | |||
| Taylor MDA | Yes | Yes | Yes | LGPL | |||
| TextUML Toolkit | Yes | Yes* | No | EPL | 2.5 | 5.0 | Uses a textual notation |
| TOPCASED UML | Yes | Yes | Yes | EPL | |||
| UML Designer | Yes | Yes | No | EPL | 7.1 | 2.5 | Customizable, as it is based on Eclipse Sirius |
| UML Lab | Yes | Yes | Yes | Commercial | adaptable Round-Trip-Engineering with Xpand Templates |
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.