ReqXChanger – The Gearwheel between Requirements and Modeling

The Willert ReqXChanger offers an interface between requirements management and modeling tools, providing synchronisation of requirements and related information. It supports common requirements management tools, such as DOORS and Polarion, and the leading UML / SysML modeling solution – IBM Rational Rhapsody. Further, it supports the widely established UML tool Enterprise Architect from Sparx Systems.
By using the ReqXChanger, you are able to make a complete traceability and impact analysis for your requirements and your model elements.

You will need an installed Java Version 8 or higher to run ReqXChanger. Ensure that you have installed the appropriate Java architecture (32bit/64bit) for the downloaded ReqXChanger version. Download Java 8

New and noteworthy in ReqXChanger 1.3.1

  • Requirements with ReqIF.ForeignDeleted=true are marked as deleted now in the target tool.
  • On export, ignore specifications and requirements which were formerly created by ReqXChanger during roundtrip.
    Note: some requirement tools, e.g. DOORS remove the ReqXChanger type information from ReqIF so that this feature cannot work properly.
  • Modified behavior when exporting specifications with empty root package name:
    Create always top-level packages for specifications instead of storing requirements in a default top-level package. If now specification package name is explicitly configured, the specification LongName will be used.
    Note: If you want to enforce the previous behavior, configure the formerly used default root package name explicitly: For Rhapsody: “Default”, for EA: “Requirements”.
  • New option: Export only specifications which are configured with Specification Package Name.
    This allows you to use ReqIF files with multiple documents and export it only partially to the target tool. You can use this feature also to avoid export of formerly roundtrip specifications which cannot be detected due to the issue mentioned above.
  • New option: Roundtrip test results of linked test cases.
    The content of the test result will be stored as description of the corresponding test result element.
  • New option: On roundtrip, create separate dependency groups for each dependency type.
    This results in separate Link modules when importing the roundtrip ReqIF into DOORS.
  • New option: On roundtrip, use the requirements root package as identifier for the roundtripped ReqIF specification.
    This causes target tool element representations to be stored in different ReqIF Specifications of roundtrip ReqIF for different Requirements root packages in the target tool. This is useful to store target tool element representations in different modules/documents when importing the roundtrip ReqIF into the requirement tool.
  • New option: Set custom name for the ReqIF specification which contains the roundtripped elements from target tool.
  • Fixed bug: On roundtrip, all contents in model root package are considered now, not only packages.
  • ReqXChanger is now available for 32bit and 64bit architecture
    You can select the version for download after the checkout.
    Note: You also need the appropriate Java version installed. If you only have Java 32bit installed, then you can also only use the 32bit version of ReqXChanger.

Known Issues

  • If you do not have installed the correct Java version, you will get an error when starting the application.
  • When using multiple documents, ensure, that the ReqIF-ID is unique when exporting multiple documents into one Root Package. For DOORS: Use separate root packages for each ReqIF document from DOORS.
  • For roundtripped descriptions of UML artifacts, line breaks cannot be considered currently.
  • DOORS cannot handle the default XHTML format for formatted text in ReqIF, so that roundtripped test results will not be displayed properly.

Upgrade from previous version

If you are upgrading from an already licensed previous ReqXChanger version 1.3.0 or above, you can use this upgrade instantly.

If you are upgrading from an already licensed previous ReqXChanger version 1.2.9 or before, you need to request a new license key. Please send us the data which are provided by the license dialog when starting the application to get a free upgrade of your license key which is valid for ReqXChanger 1.3.0 and above.

Evaluation of ReqXChanger

This version of the ReqXChanger requires a valid license, but includes an evaluation mode. If you do not have a valid license key, the ReqXChanger will start in Demo mode, which has the following limitations:

Demo mode

  • Only ReqIF files can be used, which do not contain more than 200 elements
  • Requirements in UML tools will have a postfix “DEMO” in their name
  • Roundtrip of linked model elements to the ReqIF File (and RM tools) is not supported
  • The description of requirements in UML tools is not set