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.

New and noteworthy in ReqXChanger 1.3.0

  • More default Stereotypes for considering Dependencies during Roundtrip (trace;satisfy;verify)
  • No more Validation Errors in Global Options, if a Jar File for Enterprise Architect or Rhapsody is not set
  • In Mapping Expressions “\n” can be entered for creating newline
  • Improved Compatibility with DOORS: There is a Roundtrip Option now called “DOORS Compatibility Mode”. By setting this option, a TOOL-EXTENSION will be added to the ReqIF when roundtripping in order to get MERGE in DOORS to work.
  • DOORS compatibility: support for indirect links by dependencies to software components which are linked to requirements
  • Rhapsody: Option to select a project file for exchanging requirements
  • Identifier of Rhapsody Requirements is set to Options Value of Requirements Identification
  • Specification Mapping is now available for Rhapsody Requirements
  • When roundtripping, only consider requirements in UML which also exist in ReqIF. Before, a Warning was logged, because a relation could not be created in ReqIF, if the requirement is not in ReqIF.
  • If Links/Dependencies with special stereotypes are considered for roundtrip, set as description for created relations the stereotype that was relevant for roundtripping
  • Roundtrip: Consider multiple Dependencies between the same Model elements and Requirements with different Stereotypes
  • Rhapsody: When exporting requirements into a root package, the package is marked as external, if it does not already exist
  • License Key is not depending on Mac Address anymore; added detailed license status at startup if the license is not valid for the current product
  • Labels for import, export and roundtrip buttons are more descriptive now
  • Improved labels and tool tip description for preset options (formerly named “Mode”)
  • Improved support for command line based execution: waits for finishing all import/export actions before return/exit

Known Issues

When using DOORS, you have to be carefully when exporting ReqIF once you have reimported a ReqIF from roundtrip. The ReqIF-Definition must not contain any modules which were added by ReqXChanger. We recommend to create a new ReqIF-Definition each time you want to export a new ReqIF after you imported a ReqIF with roundtrip data from ReqXChanger.

Upgrade from previous version

If you are upgrading from an already licensed previous version of ReqXChanger, 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.

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