Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/Oxygen Work Description/NewFeature/ImportRhapsody"
(→Papyrus Rhapsody Plugins) |
(rewrite the Incoming document, remove many line about QVTo troubles during the dev.) |
||
| (13 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | =Import From Rhapsody Model= | + | This documentation talks about the import of models created with the software '''IBM Rational Rhapsody''' into Papyrus. '''IBM Rational Rhapsody''' is developed by the IBM company. In this documentation, we reference this software as '''Rhapsody'''. |
| + | |||
| + | ==Which Rhapsody version models are supported?== | ||
| + | The migration tool has been developed with IBM Rhapsody 8.0.3. Nevertheless, it should work with previous and next versions. | ||
| + | |||
| + | ==Where are located the Papyrus Intereoperability Rpy plugins?== | ||
| + | All Papyrus Rpy user plugins are stored in the Papyrus git ''org.eclipse.papyrus-interoperability.git'', into the subfolder ''rpy''. | ||
| + | |||
| + | =Import From SysML Rhapsody Model= | ||
The bugs used for this task are: | The bugs used for this task are: | ||
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=496175 bug 496175: Papyrus must provide a tool to import UML Rhapsody model into Papyrus] | *[https://bugs.eclipse.org/bugs/show_bug.cgi?id=496175 bug 496175: Papyrus must provide a tool to import UML Rhapsody model into Papyrus] | ||
| − | + | *[https://bugs.eclipse.org/bugs/show_bug.cgi?id=496176 bug 496176: Papyrus must provide a tool to import Rhapsody SysML Model into Papyrus] | |
| − | *[https://bugs.eclipse.org/bugs/show_bug.cgi?id= | + | ** used to trace the development itself |
| − | ** used to trace the | + | |
| − | + | The documentation is now available in the Eclipse Help Contents. | |
| − | + | This documentation is stored into the git org.eclipse.papyrus-interoperability, at this location: '''rpy\plugins\org.eclipse.papyrus.interoperability.rpy.doc'''. It contains user documentation and developer documentation. | |
| − | + | ||
| − | + | This feature doesn't require to have the IBM Rhapsody software installed on your computer. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | * | + | =Requirements= |
| − | * | + | *Created diagrams must have a specific NamedStyled to identify them as created from Rhapsody diagrams. This NamedStyle will indicate the Rhapsody version of the initial model too. The goal of this information is to allow to target diagrams created by QVTO with DiagramReconcilier in case of bug. |
| − | ** | + | *Created semantic models will have a specific EAnnotation to identify them as created from Rhapsody Model. This EAnnotation will indicate the Rhapsody version of the initial model too. The goal of this information is to allow to target diagrams created by QVTO with DiagramReconcilier in case of bug. |
| + | *Papyrus must provide the import for the Rhapsody SysML Internal Block Diagram. | ||
| + | *Papyrus must provide the import for the Rhapsody SysML Parametric Diagram. | ||
| + | *Papyrus must provide the import for the Rhapsody SysML Block Definition Diagram. | ||
| − | + | =QVTo= | |
| − | + | The migration from Rhapsody model to Papyrus model has been done using QVTo. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | =How does Papyrus Rhapsody Import work ?= | |
| − | + | ||
This import works in 2 steps: | This import works in 2 steps: | ||
| − | #we convert the '''*.rpy''' file into a '''*. | + | #we convert the '''*.rpy''' file into a '''*.umlrpy''' which is the same model described using the EMF Rpy metamodel provided by the plugin '''org.eclipse.papyrus.interoperability.rpy.''' |
| − | #we call the QVTO transformation themselves to import the model described in the '''*. | + | #we call the QVTO transformation themselves to import the model described in the '''*.umlrpy''' file into a Papyrus model (file *.uml, *.notation and *.di) |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 11:20, 24 April 2017
This documentation talks about the import of models created with the software IBM Rational Rhapsody into Papyrus. IBM Rational Rhapsody is developed by the IBM company. In this documentation, we reference this software as Rhapsody.
Contents
Which Rhapsody version models are supported?
The migration tool has been developed with IBM Rhapsody 8.0.3. Nevertheless, it should work with previous and next versions.
Where are located the Papyrus Intereoperability Rpy plugins?
All Papyrus Rpy user plugins are stored in the Papyrus git org.eclipse.papyrus-interoperability.git, into the subfolder rpy.
Import From SysML Rhapsody Model
The bugs used for this task are:
- bug 496175: Papyrus must provide a tool to import UML Rhapsody model into Papyrus
- bug 496176: Papyrus must provide a tool to import Rhapsody SysML Model into Papyrus
- used to trace the development itself
The documentation is now available in the Eclipse Help Contents. This documentation is stored into the git org.eclipse.papyrus-interoperability, at this location: rpy\plugins\org.eclipse.papyrus.interoperability.rpy.doc. It contains user documentation and developer documentation.
This feature doesn't require to have the IBM Rhapsody software installed on your computer.
Requirements
- Created diagrams must have a specific NamedStyled to identify them as created from Rhapsody diagrams. This NamedStyle will indicate the Rhapsody version of the initial model too. The goal of this information is to allow to target diagrams created by QVTO with DiagramReconcilier in case of bug.
- Created semantic models will have a specific EAnnotation to identify them as created from Rhapsody Model. This EAnnotation will indicate the Rhapsody version of the initial model too. The goal of this information is to allow to target diagrams created by QVTO with DiagramReconcilier in case of bug.
- Papyrus must provide the import for the Rhapsody SysML Internal Block Diagram.
- Papyrus must provide the import for the Rhapsody SysML Parametric Diagram.
- Papyrus must provide the import for the Rhapsody SysML Block Definition Diagram.
QVTo
The migration from Rhapsody model to Papyrus model has been done using QVTo.
How does Papyrus Rhapsody Import work ?
This import works in 2 steps:
- we convert the *.rpy file into a *.umlrpy which is the same model described using the EMF Rpy metamodel provided by the plugin org.eclipse.papyrus.interoperability.rpy.
- we call the QVTO transformation themselves to import the model described in the *.umlrpy file into a Papyrus model (file *.uml, *.notation and *.di)