Release 1.3.0
Improvements
- 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.
- DOORS Compatibility
- New Roundtrip Option 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.
- 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 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.
- 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.
- Labels for import, export and roundtrip buttons are more descriptive now.
- Roundtrip
- 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.