ReqXChanger2.0.2

Select

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 2.0.2:

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

  • EA roundtrip: Now Interaction Occurrences will also be respected as diagrams for roundtrip.
    This helps with the issue that EA always creates Interaction Occurrences instead of Diagram Reference when dragging a Sequence Diagram to a diagram for creating trace links.

New and noteworthy in ReqXChanger 2.0.1:

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

  • Fixed bug that old links between requirements are not deleted correctly when exporting requirements to EA

New and noteworthy in ReqXChanger 2.0.0:

  • DOORS Compability: Improved roundtrip compability with DOORS. Now allows for using a ReqIF Specification in DOORS again and again and when merging, deleted UML elements will be marked as deleted.
  • Bugfix: EA Roundtrip: Catch Exception when EA API is unable to get element for ID from connector end.
  • Bugfix: <identifier> could not be used as a requirement identifier correctly
  • Rhapsody: Handle enum literal names “new” and “default” and add postfix, as Rhapsody does not allow for enum literals with these names
  • Bugfix: improve reliability for creating visualization stereotype on roundtrip
  • EA Roundtrip: extended error message when inspecting invalid trace dependencies (EA Connectors)
  • EA: EA Repository Option: Fixed that ODBC Connection strings were not shown if they were set as option value. Any String is considered as a valid value now.

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. You may also now use the new feature for custom roundtrip ID to ensure a unique roundtrip document ID to merge the document in your RM tool.
  • 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
  • EA sequence diagrams needs to be used as Diagram Frame in order to roundtrip them properly. Reason: For Sequence Diagrams EA creates an InteractionOccurrence instead of a Diagram Reference when dragging it into a diagram for link it with a Requirement.

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
Select