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.5.2:

This is a bugfix release. It does contain all the features from ReqXChanger 1.5.0 and 1.5.1 including the following improvements and bug fixes to already existing features.

  • EA Roundtip: Fixed roundtrip handling of root packages which have specific meta types applied by stereotypes
  • EA Connection: Improved error handling when connecting to EA repository
  • Fixed basic ReqIF XHTML type handling for some specific ReqIF content

New and noteworthy in ReqXChanger 1.5.1:

This is a bugfix release. It does contain all the features from ReqXChanger 1.5.0 including the following improvements and bug fixes to already existing features.

  • Improved mechanism to delete temp directories which are created for ReqIFz files to avoid keeping unneeded directories in system temp directory.
  • Fixed bug that content of multiple ReqIF files is not shown correctly in model browser when using compatibility option Separate Roundtrip ReqIF.
  • Enterprise Architect 14 Roundtrip: Fixed that trace relations were not considered for finding model elements related to requirements.
  • Rhapsody: Fixed bug that empty/white diagram images were saved when roundtripping diagram images.
  • Fixed bug that ignored separation of packages with “.” for specification subpackages
  • rpyx files will be available when selecting rhapsody project for connection to project

New and noteworthy in ReqXChanger 1.5.0:

  • Roundtrip: New attribute for storing stereotype (names) that are applied to model elements
  • Rhapsody Roundtrip: Option to use NewTerm Stereotype names like “Block” in SysML for Type attribute values instead of MetaClass names (Mode->Advanced->Roundtrip Model Elements->Model Element Types->Use New Term Stereotype Names…)
  • Allows to create separate ReqIF file for Roundtrip document with model elements (for instance for using Atego Exerpt)
  • Mode/Preset with recommended Options for working with EXERPT 2
  • Mechanism (Helper) for rhapsody to apply stereotypes to requirements after export
  • Allow to roundtrip model elements that are in relation with requirements like this: Requirement <– model element 1 –> model element 2
  • Option to make Requirements Package in EA/Rhapsody read only after export (Packages->Make Requirements Package Read Only)
    • Rhapsody: ReqXChangerTypes Package will also be made read only
  • Added Rhapsody Helper for creating diagrams for certain elements. The diagrams will visualize the element, in order to get a graphical illustration of the element into the RM tool when roundtripping.
  • License System extended to allow to consider restricted licenses

Known Issues

  • When using multiple documents, ensure, that the used Identifier 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.
  • DOORS will show UML diagram images as a shortcut symbol, which you must select in order to see the diagram picture

Upgrade from previous version

Upgrade from version 1.4.1:

  • Just extract and start the new version

If you are upgrading from an already licensed previous ReqXChanger version 1.3.0 – 1.4.0:

  • If you have unsaved configuration in your ReqXChanger, before upgrading, save the configuration into a file. After upgrading, load the file with the new version of the ReqXChanger again.
  • You have to re-enter your license key.

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 Evaluation mode, which has the following limitations:

Evaluation mode

  • Allowed only for using for evaluation purposes. No commercial usage allowed.
  • Dialog at startup, which informs about being in evaluation mode
  • Appends an evaluation postfix to the name of requirements in UML tools