To obtain the license information needed, run FlexNet LMTools GUI.
Select the System Settings tab, then Save HOSTID info to a File by clicking the corresponding button.
Provide the generated file to the support team.
ReqXChanger runs with Java (JRE or JDK) 11 or higher - 64 bits.
A OpenJDK 11 version is provided with ReqXChanger. It is programmed by default to start with this version.
It is possible to specify a specific JVM for ReqXChanger to run on. For this you will have to set the -vm
option in the ReqXChanger.ini
File.
For more information on how to set the -vm
option, consult the Specifying the JVM page.
No.
It is possible to create ReqXChanger Rhapsody menus by hand. For more information on how to create them, consult Setting Menus in Rhapsody page.
If nothing happens, this is probably due to an installation problem. For more information on how to create them, consult Setting Menus in Rhapsody page.
Logs are always generated in a file (by default in %TEMP%/Sodius/ReqXChanger
, where TEMP
represents the User Temporary Folder).
The log file location can be configured by adding -logfilelocation option as argument in ReqXChanger.ini file (e.g. -logfilelocation C:/ReqXChanger/Logs
):
To export Requirements from DOORS, you have to create a ReqIF Definition and then export it.
For more information on how to create a ReqIF Definition, consult Exporting Requirements from DOORS.
You can only filter the content of the ReqIF file when exporting from DOORS by using views:
The Include data in view option exports the data (Attributes) defined in the view.
The Views to Include option exports the selected views in the ReqIF File. All Attributes are exported in that case.
To filter the content of the ReqIF file, the option Include data in view must be used.
Yes, you can either export the current version of the Formal Module, either a Baseline of it. For more information on DOORS ReqIF definition creation, consult Creating ReqIF definitions.
The menu ReqXChanger > Update Requirements will synchronize Requirements from DOORS in Rhapsody:
The menu ReqXChanger > Open ReqXChanger > Read Requirements will read the ReqIF File.
If you open the Model Browser tag (in ReqXChanger), you will be able to have a simple view of the Elements in the ReqIF File (Specifications, SpecObject).
Some tools, like ReqIF Studio, view the elements of the ReqIF file:
The navigation from Rhapsody to DOORS is done through the creation of Hyperlinks in Rhapsody.
For more information on how to create the Hyperlinks in Rhapsody, consult Navigation from Rhapsody to DOORS.
Rhapsody weblinks to DOORS elements are not created by default.
For more information on how to create them, consult Navigation from Rhapsody to DOORS.
I have selected the ReqXChanger option Create Weblink during Export however I have a strange “Unloaded” Hyperlink.
When I click on the hyperlink, Rhapsody indicates that “Hyperlink target model element does not exist”:
This happens because the DOORS attribute used for navigation does not exist in DOORS.
For more information on how to navigate from Rhapsody to DOORS, consult Navigation from Rhapsody to DOORS.
Note: A dxl script would create this attribute DOORS_URL automatically. We will ensure to provide such a script in a future release of ReqXChanger.
The visualization of Traceability and Requirements coverage is ensured by Tables in Rhapsody. To date there are three types of tables:
I am working in parallel on two different Rhapsody projects. Both projects uses ReqXChanger for traceability purpose and different DOORS ReqIF Files…
In that case, you will have to load and use different ReqXChanger configurations (each corresponding to the Rhapsody project and the DOORS ReqIF File):
To import Model Elements in DOORS, you have to import the ReqIF Package created by ReqXChanger. Then, you can merge the imported Elements.
For more information on how to import and merge Model Elements, consult Export to DOORS.
The navigation from DOORS to Rhapsody is done through the creation of an Attribute in DOORS.
For more information on how to navigate from DOORS to Rhapsody, consult Navigation from DOORS to Rhapsody.
For more information on differences between Gateway and ReqXChanger, consult Differences between Gateway and ReqXChanger.
Hyperlinks to the DOORS original Object are created during Gateway migration if some options are set: