Roundtrip Stereotyped Model Elements to Polarion
This guide provides instructions for roundtripping Stereotyped Model Elements from Rhapsody to Polarion using ReqXChanger.
In the simplest case, ReqXChanger only roundtrips linked elements to a Requirement.
The option Roundtrip Stereotyped Model Elements allows the roundtrip of stereotyped elements.
Roundtrip a Stereotyped Element
To roundtrip a Stereotyped Element:
- From Rhapsody, select the menu File > Add Profile to Model...
- Select the File
ReqXChanger.sbsx from your ReqXChanger installation.
- From the Rhapsody browser, select a Rhapsody Element to stereotype. In our example, we have selected the Use Case "call elevator".
- Right-click and select the menu ReqXChanger > Add to Roundtrip. The Rhapsody Element is stereotyped <<roundtrip>>.
Note that the Use Case "call elevator" does not have a traceability link to a Requirement.
- From ReqXChanger, select the Rhapsody Options... button.
- Select the menu Mode > Roundtrip Model Elements > Stereotyped Model Elements.
- Select the checkbox Roundtrip Stereotyped Model Elements.
- From ReqXChanger, run the roundtrip.
This roundtrips the Use Case "call elevator":
Note: The menu ReqXChanger > Add to Roundtrip only stereotypes <<roundtrip>>.
It is possible to use another stereotype. If another stereotype is used, the property Mode > Roundtrip Model Elements > Stereotyped Model Elements > Stereotype Names has to be updated.
Roundtrip a Stereotyped Element and its sub-types recursively
To roundtrip a Stereotyped Element and its sub-types recursively:
- From ReqXChanger, select the Rhapsody Options... button.
- Select the menu Mode > Roundtrip Model Elements > Sub-architectural Model Elements.
- Select the checkbox Roundtrip Sub-architectural Model Elements.
- Select the checkbox Roundtrip Recursively.
- Set the checkbox Roundtrip All Types.
Of course, the checkbox Mode > Roundtrip Model Elements > Stereotyped Model Elements > Roundtrip Stereotyped Model Elements is still selected.
This roundtrips the Sub-Elements recursively of the Use Case "call elevator":
