Rational Software Modeler Version 7.5 Releases: New Features and Enhancements

Product documentation


Abstract

IBM Rational Software Modeler Version 7.5.x releases contain cumulative fixes, enhancements, and new features, meaning that they include all new features or enhancements, as well as additional fixes to Eclipse, from earlier releases.

Content

Version 7.5.5.5
Version 7.5.5.4
Version 7.5.5.3
Version 7.5.5.2
Version 7.5.5.1
Version 7.5.5
Version 7.5.4
Version 7.5.3
Version 7.5.2
Version 7.5.1
Version 7.5


Version 7.5.5.5
Download Version 7.5.5.5

This release of Rational Software Modeler contains enhancements in the following area:
  • Updates to supported web browsers
  • Additional Eclipse patches and fixes




  • Updates to supported web browsers
    Beginning with version 7.5.5.5, the following additional web browser versions are supported:
    • Mozilla Firefox 5.0, 6.0, and 7.0

    Back to top



    Additional Eclipse patches and fixes
    The following additional Eclipse 3.4.2.8 patches and fixes are included in this release:
    Back to top

    Version 7.5.5.4
    Download Version 7.5.5.4

    This release of Rational Software Modeler contains enhancements in the following area:
    • Updates to supported operating systems
    • IBM Runtime Environment for Java Technology updates
    • Updates to supported web browsers
    • Additional Eclipse patches and fixes




    • Updates to supported operating systems
      Beginning with version 7.5.5.4, the following additional operating system versions are supported:
      • Microsoft Windows 7 Service Pack 1
      • Microsoft Windows Server 2008 Release 2 Service Pack 1
      • Red Hat Enterprise Linux 5 Update 6
      • Red Hat Enterprise Linux 4 Update 9
      • SUSE Linux Enterprise Server 10 Service Pack 4
      • SUSE Linux Enterprise Desktop 10 Service Pack 4

      Back to top



      IBM Runtime Environment for Java Technology updates
      IBM Runtime Environment for Java Technology is updated to the following versions:
      • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 Service Release 9 plus Fix Pack 001 and interim fix
      • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 Service Release 9 plus Fix Pack 001 and interim fix

      Back to top



      Updates to supported web browsers
      Beginning with version 7.5.5.4, the following additional web browser version is supported:
      • Mozilla Firefox 4.0
      • Microsoft Internet Explorer 9

      Back to top



      Additional Eclipse patches and fixes
      The following additonal Eclipse 3.4.2 patches and fixes are included in this release:
      Back to top

      Version 7.5.5.3
      Download Version 7.5.5.3

      This release of Rational Software Modeler contains enhancements in the following area:


      Additional Eclipse patches and fixes
      The following additonal Eclipse 3.4.2 patches and fixes are included in this release:
      Back to top



      UML-to-XSD and UML-to-WSDL transformations
      You can now specify whether the UML-to-WSDL and UML-to-XSD transformations generate output by using customized output information, such as namespace and resource location information, that you provide in the transformation configuration: On the Output Options page of a transformation configuration, select the Customize the output according to the entries in the following table check box. When you run the transformation, it uses the information in the corresponding table to generate output. By default, this option is selected.

      If you disable this option, the transformation ignores the information in the table and uses only the information in the source model to generate output. Although the information in the table is refreshed, the transformation ignores it.

      Back to top



      Version 7.5.5.2
      Download Version 7.5.5.2

      This release of Rational Software Modeler contains enhancements in the following area:


      Eclipse platform updates
      The following additional Eclipse 3.4.2 patches and fixes are included in this release:
      • Eclipse platform: Bugzilla fixes 304277, 305998, 316514
      • Eclipse platform, UML: Bugzilla fix 278385
      • Eclipse Equinox p2: Bugzilla fixes 259946, 303936, 314939
      • Eclipse Modeling Framework (EMF): Bugzilla fixes 254621290555
      • Rich Client Platform (RCP): Bugzilla fix 303499
      • Remote System Explorer (RSE) framework: Bugzilla fix 286122
      • Test and Performance Tools Platform (TPTP) Project: Bugzilla fix 319898


      IBM Runtime Environment for Java Technology updates
      IBM Runtime Environment for Java Technology is updated to the following versions for Windows and Linux operating systems:
      • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 8
      • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 8

      Back to top



      Service modeling - SoaML profile & tools
      In earlier releases, the SoaML 1.0 specification was supported only at a draft level. Now the final SoaML 1.0 specification is supported. Models that use the SoaML profile from earlier versions of the product are automatically migrated to the new profile version when they are opened.

      Back to top

      Version 7.5.5.1
      Download Version 7.5.5.1

      This release of Rational Software Modeler contains enhancements in the following area:
      • Additional Eclipse patches and fixes
      • Updates to supported Web browsers
      • IBM Runtime Environment for Java Technology updates
      • Rational Rose model import
      • UML Profile-based Integrated Architecture (UPIA) (IAM2)




      • Additional Eclipse patches and fixes
        The following additional Eclipse 3.4.2 patches and fixes are included in this release:
        Back to top



        Updates to supported Web browsers
        Beginning with version 7.5.5.1, the following additional Web browser version is supported:
        • Mozilla Firefox 3.6

        Back to top



        IBM Runtime Environment for Java Technology updates
        IBM Runtime Environment for Java Technology is updated to the following versions for Windows and Linux operating systems:
        • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 7 plus interim fix 001
        • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 7

        Back to top



        Rational Rose model import
        You can now save the the subunit conversion options in a file which has .xml as the file name extension on the Subunit Conversion page of the Rational Rose Model Importer wizard.

        When you need to import the same sets of subunits (with count in order of hundreds or thousands) multiple times with the same conversion pattern, you can use this feature to load and reapply the .xml file for subsequent imports.

        Back to top



        UML Profile-based Integrated Architecture (UPIA) (IAM2)
        The UML Profile-based Integrated Architecture (UPIA) feature has been upgraded to further support DoDAF 2.0 and to improve usability. For detailed information, see the Rational support document, "Changes to the IBM Rational UML Profile-based Integrated Architecture (UPIA) feature in V7.5.5.1," at http://www.ibm.com/support/docview.wss?rs=3539&uid=swg27017935.

        Back to top

        Version 7.5.5
        Download Version 7.5.5

        This release of Rational Software Modeler contains enhancements in the following area:
        • Eclipse platform updates
        • Updates to supported operating systems
        • IBM Runtime Environment for Java Technology updates
        • UML modeler
        • Rational Asset Manager integration
        • Rational Requirements Composer integration transformation
        • UML Profile tooling
        • Rational Rose model import




        • Eclipse platform updates
          The following Eclipse 3.4.2 patches and fixes are included in this release:
          Back to top



          Updates to supported operating systems
          Beginning with version 7.5.5, the following additional operating system versions are supported:
          • Microsoft Windows Server 2008 Release 2
          • Microsoft Windows 7

          Back to top



          IBM Runtime Environment for Java Technology updates
          IBM Runtime Environment for Java Technology is updated to the following versions for Windows and Linux operating systems:
          • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 6 plus interim fix
          • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 6 plus interim fix

          Back to top



          UML modeler
          • New preference to set the search scope options for models, new option when setting the search scope to exclude non-imported UML libraries.
          • The following new functions have been introduced to sequence diagrams:
          • Asynchronous messages can be created without a Behavior Execution Specification.
          • Behavior Execution Specification for asynchronous message can be deleted.

          Back to top



          Rational Asset Manager integration
          The publish asset wizard can now handle custom attribute fields.

          Back to top



          Rational Requirements Composer integration transformation
          The Rational Requirements Composer integration transformation now supports archives from Rational Requirements Composer Version 2.0, or later.
          To import archives from Rational Requirements Composer Version 2.0, or later, you must use Rational Software Modeler Version 7.5.5 with Interim Fix 002, or later. For more information, see http://www.ibm.com/support/docview.wss?uid=swg21415580.

          Back to top



          UML Profile tooling
          • By default, when you re-generate tooling code, files such as plugin.xml, plugin.properties, and the template model are overwritten. However, you can now specify preferences that determine whether these key files are overwritten. In addition, these preferences also allow you to create backup copies of these files. For details on how to specify the new preferences, see the profile tooling online help.
          • It is now possible to specify an image and indent status for property tabs generated as part of profile tooling. For details on using images in profile tooling, see the profile tooling online help.

          Back to top



          Rational Rose model import
          You can use the new Map Rose User Types page of the Rational Rose Import wizard to map user-defined types of a Rational Rose model to a new custom model library, or map user-defined types to existing model libraries, and set this configuration for subsequent imports.
          There is also an option in the same page to import Rational Rose user-defined types as primitive or class types. Previously this option was only available through application parameters in the eclipse.ini file.

          Back to top

          Version 7.5.4
          Download Version 7.5.4

          This release of Rational Software Modeler contains enhancements in the following area:
          • Eclipse platform updates
          • Updates to supported operating systems
          • Updates to supported Web browsers
          • IBM Runtime Environment for Java Technology updates
          • Service modeling with SoaML
          • Service profile migration
          • BPMN modeling
          • UML Profile-based Integrated Architecture (UPIA) (IAM2)
          • Patterns and transformations
          • Profile tooling generator
          • Rational RequisitePro integration
          • Rational Rose model import
          • Rational System Architect integration
          • Rational Team Concert Client integration
          • Traceability
          • UML model analysis and metrics
          • UML modeler
          • UML compare and merge
          • Web publishing




          • Eclipse platform updates
            The following Eclipse 3.4.2 patches and fixes are included in this release:
            Back to top



            Updates to supported operating systems
            Beginning with version 7.5.4, the following additional operating system versions are supported:
            • Microsoft® Windows® XP Service Pack 3
            • Microsoft Windows Vista Service Pack 2
            • Microsoft Windows Server 2008
            • Red Hat Enterprise Linux® 5 Update 4
            • Red Hat Enterprise Linux 4 Update 8

            Back to top



            Updates to supported Web browsers
            Beginning with version 7.5.4, the following additional Web browser versions are supported:
            • Mozilla Firefox 3.5.2
            • Microsoft Internet Explorer 8

            Back to top



            IBM Runtime Environment for Java Technology updates
            IBM Runtime Environment for Java Technology is updated to the following versions for Windows and Linux operating systems:
            • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 5 plus interim fix
            • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 5 plus interim fix

            Back to top



            Service modeling with SoaML
            • In this release, comprehensive support is added to service modeling based on the forthcoming new Service Oriented Architecture Modeling Language (SoaML ) standard from OMG :
              • The new services modeling tools and related enhancements reflect SOA development process best practices documented by RUP SOMA 2.9 to guide you to success with business-driven, robust, scalable SOA development.
                A new Services Design Model template can automatically create the recommended model and package structure and includes reusable building blocks that let you build robust service designs more quickly.
              • The services modeling tools are integrated with the new Business Process Modeling Notation (BPMN) 2.0-based business process modeling tools. This includes automatic creation of traceability links from service model elements back to the business process model elements from which they were derived. This enables you to have better change governance and do more accurate impact analysis on SOA projects.
                For example, given a high-level BPMN 2.0 business process model, an IT architect doing up front candidate service identification can select an appropriate business process model element and easily create a corresponding service model capability (representing a candidate service) in a service model (including a traceability link). These Capabilities can then be refined and refactored as needed, becoming input into subsequent process steps, such as service identification.
              • The services modeling editor and related tools focus heavily on usability and keeping simple things simple. This enables even those who are new to UML and SOA to successfully and effectively build detailed services models as part of an overall SOA process. However, the expressiveness of full UML is also always available.
              • When editing a Services Model, the UML editor provides context menu and palette drawer items specifically tailored to be convenient and useful for services modeling.
                • Various "accelerators" provide quick ways to perform common multi-step operations in a single step.
                • A Service tab added to the Properties view is selection-sensitive and lets you view and modify those properties of selected elements that are of most interest to services modelers.
              • You can migrate existing services models that are based on the (now-deprecated) Software Services profile to the new standard SoaML profile from OMG.
              • Samples and a tutorial help you get up to speed by using the new Services Modeling and related tools.
            • A new transformation named BPMN-to-Service-Model is available for generating service models based on the information in Business Process Modeling Notation (BPMN) models.
            • UML-to-SOA transformations (WSDL/XSD, BPEL, and SCDL) have been updated to work with SoaML.
            • A new UML-to-SOA transformation is provided: UML-to-Open SCA.

            Back to top



            Service profile migration
            A new tool to migrate from the Software Services Profile to the SoaML profile is provided. The new Migrate to SoaML Profile menu will pop up when the model contains "Software Services" profile. The tool applies SoaML profile stereotypes when it finds matching SoftwareServices profile stereotypes on UML elements in the model.

            Back to top



            BPMN modeling
            • New support for the creation and management of semantic models and diagrams based on Business Process Modeling Notation (BPMN) version 2.0.
            • Integrated with UML modeling:
              • Link and navigate to BPMN elements from UML elements (by creating URL links using Add UML > URL Link and Navigate >To URL Link pop-up menus)
              • Use the Service Modeling (SoaML) tool palette to complete the following tasks:
                • Create SoaML <<Capability>>Classes from existing BPMN elements (also works with UML Activities as the source elements).
                • Create SoaML <<ServiceInterface>Interface/Class from existing BPMN element.

            Back to top



            UML Profile-based Integrated Architecture (UPIA) (IAM2)
            The UML Profile-based Integrated Architecture (UPIA) feature has been upgraded to support DoDAF 2.0 and to improve usability. In addition, the UPIA explore tools on the diagram palette now support custom queries for populating diagrams. For detailed information, see the Rational support document, "Changes to the IBM Rational UML Profile-based Integrated Architecture (UPIA) feature in V7.5.4," at http://www.ibm.com/support/docview.wss?rs=3539&amp;uid=swg27016194.

            Back to top



            Patterns and transformations
            • Public API for transformation configurations has been expanded: You can now create and validate transformation configurations by using new methods in the utility class named com.ibm.xtools.transform.core.config.TransformConfigUtil. The new method for creating a transformation configuration requires an IFile parameter that represents the workspace file for the transformation configuration.
              The methods in this class that create transformation configurations no longer validate the transformation configurations automatically; you must use the validateConfiguration method to do so.
            • Transformations can now update the progress bar that the progress dialog box shows when a transformation runs. To do this, you can add the new rule named com.ibm.xtools.transform.core.UpdateProgressMonitorRule to the transformation source code. This feature provides you with more accurate information about how much work the transformation must complete.
            • The transformation configuration editor has been converted to a form-based editor that supports both form-based and non-form-based pages. The editor now displays non-form-based pages on a white background to provide a consistent look with the form-based pages.
              Transformation authors can now contribute form-based pages by using a new class named com.ibm.xtools.transform.ui.AbstractTransformConfigFormPage in the public API.
            • You can now specify the location of log files that are used for debugging transformations.
              To configure this preference, complete the following steps:
              1. Click Window > Preferences.
              2. In the Preferences window, expand Modeling; then click Transformations.
              3. In the Location of debug logs field, specify a folder on the file system.
              Each time a transformation runs, a log file is generated in the location that the preference specifies.
              To open a log file, in the transformation configuration editor, click the corresponding icon that is located in the shared header of the transformation configuration editor.
            • When debugging a transformation, transformation authors can now view the sorted contents of a transformation context.A logical structure has been provided for transformation contexts:
              • The context is now shown as a flat, alphabetical list of property identifiers and values, instead of using the structure of a HashMap.
              • When you debug a transformation, in the Variables view, click Show Logical Structure. When you expand a variable that represents a transformation context, the context is displayed by using the logical structure.
            • Authors of transformations or transformation extensions can determine whether a property is available for use by the current transformation configuration by using methods from a new utility class named com.ibm.xtools.transform.core.extension.TransformExtensionUtil. The property is available if it is defined by the transformation or by an extension that is enabled in the transformation configuration.

            Back to top



            Profile tooling generator
            When you execute the Generate Tooling Code command, you are now presented with a number of dialog boxes, asking if you want to overwrite each of the following files: plugin.xml, plugin.properties, and the template model. The purpose of the warnings is to inform you that these files are about to be overwritten, in case you manually modified these files and want to maintain their customization. There is an issue with accidentally overwriting the plugin.properties files. For more information, see http://www.ibm.com/support/docview.wss?uid=swg21403692.

            Back to top



            Rational RequisitePro integration
            The process for opening a Rational RequisitePro® project has been improved to optimize the loading speed of projects, including complex package structured projects.
            The Rational RequisitePro linking performance has also been improved to reduce the time to link and unlink requirements and domain elements

            Back to top



            Rational Rose model import
            • To avoid model validation error IRJA0232E, you can select the Add create keyword to the trigger for the transitions originating from Start State option in the Rose Model Import wizard preferences page. This option adds a create keyword for the trigger that is linked with the transitions originating from the initial node.
            • To avoid model validation error IRJA0131W, the Rational Rose Model Import adds events to the triggers to the imported model based on the following rules:
              • Events in Rose with name equals to When are converted to a Change Event. The parameter of the events is copied to the associated opaque expression.
              • Events in Rose with name equals to After or At are converted to a time event. The parameter of the events is copied to the associated time expression.
              • Any event other than When, After, or At cannot be termed as any specific event. In this case, you can select the option from the Convert unmapped State Machine Transition Events to menu in the Rose Model Import wizard preference page and convert the event.
            • The Rose Model Import wizard now supports the pathmap-based profiles for the custom properties in the imported Rose model. The enhancement covers the following changes:
              • To import Rose custom property set or custom stereotype as profile, you can now use any pathmap variable defined in the preferences page (Window > Preferences > Model > Path Maps).
              • You can also reference available pathmap-based profile. The Rose Model Import wizard allows mapping of Rose custom property set or the Rose stereotype to the compatible deployed profile using pathmap.
            • The Browse for Profile dialog box has been enhanced so you can navigate to the deployed profile and reference the profile through pathmap.

            Back to top



            Rational System Architect integration
            The Rational System Architect import and export wizards have been enhanced to support both the predefined system architect multiplicity names (as before) and the general UML multiplicity format "N..M", such as "1..5". These import and export wizards are available only on Windows systems.

            Back to top



            Rational Team Concert Client integration
            Beginning with version 7.5.4, the product is updated to support the following versions of Rational Team Concert Client:
            • Rational Team Concert Client 2.0.0.1
            • Rational Team Concert Client 1.0.1.1 iFix001
            The product continues to package Rational Team Concert Client 1.0.1.1 iFix001 as an installable feature.

            Back to top



            Traceability
            Traceability now supports tracing to Rational Team Concert work items and Rational Requirements Composer requirement specifications through a new type known as a URL link. A client can create a URL link via the product UI (pop-up menus and the tool palette) much like a URL. In traceability, URL links are treated as specifications. URLs are treated as suppliers in traceability queries and analysis rules.

            Back to top



            UML model analysis and metrics
            • There are several new UML model metrics in the Coupling category:
              • Abstractness: Use this metric to calculate the ratio of abstract and interface classes to the total number of classes in a package and its subpackages.
              • Afferent coupling: Use this metric to count the number of classifiers that a classifier references; that is, the afferent coupling. This metric examines the following outgoing relationships: inheritance, dependency, attributes type, and operation return and parameters type. The parent nodes show the average of the results for the child nodes.
              • Efferent coupling: Use this metric to count the number of classifiers that reference a classifier; that is, the efferent coupling. This metric examines the following incoming relationships: inheritance, dependency, attributes type, and operation return and parameters type. The parent nodes show the average of the results for the child nodes.
              • Instability: Use this metric to calculate the ratio of efferent coupling to the total coupling (afferent plus efferent). Greater the package dependencies, more instable the package is, that is more likely it is to change when one of its dependencies change.
              • Normal distance: Use this metric to calculate the normalized distance to the main sequence. The main sequence is where abstractness and instability are balanced. This means that a totally concrete package should have a few dependents while a totally abstract package should have many, or incoming dependencies should be proportional to the abstractness of the package. The parent nodes show the average between its own result and the child nodes results.
            • Several changes had been made to the UML model metrics in the Sizing category:
              • The rolling-up of all the rules starting by Number has been changed to sum instead of average.
              • All the rules have been duplicated into a new set starting by Average where the rolling-up is now average.
            • There is a new rule in the Completeness category:
              • Orphaned Elements: Use this rule to identify elements without relationships to other elements. Elements that are flagged as orphaned might be good candidates to delete from the model.
            • There is a new Coupling review category with two rules:
              • Cross-Model Dependency: Use this rule to identify the classifiers in a logical model that reference classifiers in a different logical model (model or package).
              • Cross-Package Dependency: Use this rule to identify the classifiers in a package that reference classifiers in a different package. Select No in the Include Sub Packages section to exclude subpackage dependencies from being flagged.

            Back to top



            UML modeler
            • URL and URL links can now have a display name. If set, display names are used by default throughout the product UI (the Project Explorer view and diagrams). If not set, the URL expression is used instead, as in prior product versions.
              As part of this feature, URLs and URL link properties, like their display name, can now be edited on the Properties view on the General page. In addition, URL and URL links have icons which can be edited from the Properties view.
            • URLs and URL links can now be linked to individual elements in a workspace.
              You can browse the workspace and create or edit URL and URL links to individual elements in the workspace, including model elements through a new Select Element dialog box launched from either the Create URL/URL link dialog box or the URL/URL link properties view. URL and URL links referencing model elements are non-semantic references.
            • Added tooling for detecting and resolving cases where duplicate GUIDs are found in the same logical model. A validation constraint checks for duplicate GUIDs for logical content in a given selection, and a new action has been added to the Modeling context menu that can allow the user to resolve the conflict through a dialog box launched from this action.
            • It is now possible to obtain modeling references to multiple modeling elements. Previously, you could only obtain modeling references to single modeling elements, for example by right-clicking on a single element and choosing Modeling references from the pop-up menu. The new functionality allows you to select multiple elements and obtain references to them.
            • Attributes from stereotypes can now be show or hidden on the diagram elements.
              In addition to controlling the visibility of these stereotype attributes per instance shape, the user can also set the default visibility behavior through modeling preferences.
            • When adding a Stereotyped class in a class diagram, you can use the pop up list to select from applicable stereotypes that are now in alphabetic order. In addition, you can also sort the Stereotype and Profile columns in the Apply Stereotype dialog box. By default, elements in this dialog box are sorted by the Stereotype column.
            • The visualization of return messages on sequences diagrams has been improved: they can now clearly be identified as dotted on display and on print.
            • You can now attach documentation in rich text to UML diagrams just as how they would attach documentation to other modeling elements.
            • You can now visualize Java binary classes that are related UML modeling elements, using the Show Related Elements functionality.Now you can localize your UML models by using an automated and simplified process.
            • The process of localizing UML models can now be done in three simplified steps:
              1. Localization export functionality exports localizable strings from a model into a .properties file.
              2. Translators translate the .properties file into another language.
              3. Localization import functionality imports the translated .properties file back into the model to be localized.
            • The XML Metadata Interchange (XMI) import feature has been enhanced to better support real-world XMI serializations of UML 2.1 models produced by other tools. It is more forgiving of nonstandard XMI extensions created through the export capabilities of other products. For example, it better handles models exported by Sparx Systems Enterprise Architect, No Magic MagicDraw, and IBM Rational Rhapsody®, including models with nested and external profiles. Problem reporting and robustness is improved when dealing with unrecognized or malformed content.

            Back to top



            UML compare and merge
            • A new conflict detection strategy for Opaque elements like Opaque Expressions, Opaque Behaviors, and Opaque Actions is introduced for Opaque elements with the same signature. This support is also extended to add deltas of classes, interfaces, class operations, and class attributes. In addition, merge as text for opaque element's body is also introduced.
            • Text sub merge compare viewer is added in the bottom half of the Compare editor for opaque elements with language body conflicts that can be toggled from Visualization of Structural changes pane, and provides enhanced sub merge usability such as swapping left and right text panes and committing or discarding sub merge results by using the new buttons added to the Text sub merge compare viewer.

            Back to top



            Web publishing
            • You can now specify the navigation style of the published model by using the documented ANT task com.ibm.xtools.publish.CLModelPublish. Previously, the default navigation style was of type Javadoc, but you can now publish models by using Interactive Tree layout with the ANT task.
            • Web published models now show the multiplicity of operation parameters. Previously, if an operation had parameters with a defined multiplicity, there would be no way to show these in web published models.
            • URL display names are now published in URL hyperlinks when publishing a model containing URLs with display names and the Create Links option selected. If no display name is set, the URL expression itself is hyperlinked. If the Create Links option is cleared, only the non-hyperlinked URL expression is published instead.
            • The new type URL link is now published in Modeling Web Publish output. They are published under the same table as URLs and their display names are published in hyperlinks if they contain display names and the Create Links option is enabled. If neither a display name is set or Create Links option is enabled, the URL expression of the URL link is published.

            Back to top

            Version 7.5.3
            Download Version 7.5.3

            This release of Rational Software Modeler contains enhancements in the following area:
            • Eclipse platform updates
            • IBM Runtime Environment for Java Technology updates
            • Patterns and transformations





            • Eclipse platform updates
              The following Eclipse 3.4.2 patches and fixes are included in this release:
              Back to top



              IBM Runtime Environment for Java Technology updates
              IBM Runtime Environment for Java Technology is updated to the following versions for Windows ® and Linux operating systems:
              • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 5
              • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 5

              Back to top



              Patterns and transformations
              The following enhancements have been made to transformation configuration:
              • For transformation configuration inheritance there is a new API for getting and setting values in the inheriting transformation configurations.
              • You can now write pages that display in the transformation configuration editor or wizard and support inheritance.

              Back to top

              Version 7.5.2
              Download Version 7.5.2


              This release of Rational Software Modeler contains new features and enhancements in the following areas:
              • Additonal Eclipse patches and fixes
              • Updates to supported operating systems
              • Updates to supported Web browsers
              • IBM Runtime Environment for Java Technology updates
              • Rational Requirements Composer integration
              • Rational Team Concert Client integration
              • Rational Rose model import
              • Transformation core
              • UML Profile-based Integrated Architecture (UPIA)
              • UML modeler: activity diagram





              • Additional Eclipse patches and fixes
                • Eclipse platform: Bugzilla fix 266538
                • Graphical Modeling Framework (GMF): Bugzilla fixes 243187, 266004, 266025
                • Test and Performance Tools Platform (TPTP) Project: Bugzilla fixes 135710, 244203, 262975, 265987
                • Equinox Project: Bugzilla fixes 265340, 267141, 267518
                • Patch for Java Development Kit (JDK): Bugzilla fix 263094
                • BIRT Chart Runtime and Report Runtime Environments: Bugzilla fix 266914

                Back to top



                Updates to supported operating systems
                Beginning with version 7.5.2, the following additional operating system version is supported:
                • Red Hat Enterprise Linux® 5 Update 3

                Back to top



                Updates to supported Web browsers
                Beginning with version 7.5.2, the following additional Web browser version is supported:
                • Mozilla Firefox 3.0 with updates

                Back to top



                IBM Runtime Environment for Java Technology updates
                IBM Runtime Environment for Java Technology is updated to the following versions for Windows ® and Linux operating systems:
                • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 4
                • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 4

                Back to top



                Rational Requirements Composer integration
                Now links attached to Rational Requirements Composer elements are transformed to UML comments with a Link stereotype applied. The Link stereotype adds two attributes: title, an optional alternative link title, and relation, an optional relationship type of the given link. Information from Rational Requirements Composer is preserved in these attributes.

                Each BPMN Collaboration participant is transformed into UML as follows:
                • A UML collaboration role attribute is created per participant.
                • A UML interface is created per BPMN process and participant pair. This interface will be the type of the respective role in UML collaboration.
                • Each such interface will contain a UML operation per BPMN task on the respective BPMN process.
                • Each such UML operation will have in or out parameters, if respective BPMN task was connected to or from a data association leading to a Data Object

                In this release for each Data Object, the transformation will create a class, and place it into the Common Classifiers folder under the root model. This class will be used to type the input and output pins created on connected activity nodes, as well as UML operation parameters for the interface which represents the UML activity.

                A new Navigate to Requirements Composer pop-up menu is available in the Project Explorer view for the UML elements transformed from composer artifacts, such as actors, use cases, and BPMN artifacts. This action opens the Rational Requirements Composer client and displays the original artifact.

                Back to top



                Rational Team Concert client integration
                It is now possible to create Rational Team Concert work items from modeling markers. The work item descriptions are initially populated with information pertaining to the selected markers. The descriptions also include hyper links to the modeling elements in the workspace to support easy navigability. In addition, it is possible to drag and drop modeling elements from the Project Explorer view into the work item description to create additional hyper links.

                This functionality is enabled by default when the Rational Team Concert Client feature is installed by IBM Installation Manager. You can create work items from the pop-up menu of a modeling reminder in the Tasks view or a modeling validation error or warning in the Problems view.

                Back to top



                Rational Rose model import
                • The Rational Rose® Model import model sharing feature is enhanced to support the following capabilities:
                  • Nested Rose subunits whose parent subunit is imported as new model, can now be shared with existing models.
                  • Rose subunits can now be shared with models from multiple modeling projects.
                  • The Rose Model Import wizard now automatically finds out and marks the subunits that can be shared during import. If you do not want to share any of the shared subunits, you can change to desired conversion choices.
                  • When a subunit is shared with existing models/packages, all the nested subunits are disabled as that is implicitly taken care of by the mapped shared model for the top level subunit.
                • The Rational Rose Model import subunits conversion feature is enhanced to support the following capabilities:
                  • Rose subunits can be shared with existing top root leRose subunits can be imported as top level root package.
                  • Rose subunits can be shared with existing top root level package from multiple modeling projects.

                Back to top



                Transformation core
                Transformation configurations can now inherit values of properties from each other. If multiple transformation configurations share the value of a specific property, you can set the value in the parent transformation configuration, and the updated value propagates automatically to the child transformation configurations.

                Back to top



                UML Profile-based Integrated Architecture (UPIA)
                The UML Profile-based Integrated Architecture (UPIA) (IAM2) feature has been upgraded to improve usability. In addition to some minor profile and tooling changes, all of the UPIA constraints were examined and updated with descriptive messages.

                Back to top



                UML modeler: activity diagram
                The expansion region and expansion node elements are now supported in activity diagrams. The Expansion Region creation tool is found in the Structured Activity Node palette stack in the Actions palette while the Expansion Node tool is in the Object Node stack in the Activity palette.

                Back to top

                Version 7.5.1
                Download Version 7.5.1


                This release of Rational Software Modeler contains new features and enhancements in the following areas:
                • IBM Runtime Environment for Java Technology updates
                • Additonal Eclipse patches and fixes
                • New splash screen
                • IBM Telelogic System Architect integration
                • Rational Requirements Composer integration
                • Rational Asset Manager integration
                • Rational Asset Manager Client
                • WebSphere Business Modeler integration
                • InfoSphere Data Architect integration
                • Transformation core
                • UML modeling
                • User assistance





                • IBM Runtime Environment for Java Technology updates
                  IBM Runtime Environment for Java Technology is updated to the following versions for Windows ® and Linux ® operating systems:
                  • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 3
                  • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 3

                  Back to top



                  Additional Eclipse patches and fixes
                  The following Eclipse 3.4.1 patches and fixes are included in this release:
                  Back to top



                  New splash screen
                  A progress bar was added to the common splash screen that displays when an Eclipse 3.4 based product is being started.

                  Back to top



                  IBM Telelogic System Architect integration
                  You can import a subset of the diagrams and content from UML models developed in IBM Telelogic ® System Architect into a UML model in the Rational modeling products, such as Rational Software Modeler. Typically such models would be expressions of software architecture best-practice patterns that have been articulated as part of the Enterprise Architecture definition that resides in Telelogic System Architect. After the model is imported to the Rational modeling products, you can use such a model as the basis for designing a specific software solution that adheres to the best practice.

                  Back to top



                  Rational Requirements Composer integration
                  You can import use case and process sketch diagrams that were used to capture business requirements in Rational Requirements Composer, and use the rich UML modeling capabilities to elaborate them into solution designs that fulfill the business requirements. Linkages between the Composer sketches and Rational RequisitePro ® requirements records are propagated to the UML modeling tool.

                  Back to top



                  Rational Asset Manager integration
                  You can now share plug-in assets using Rational Asset Manager. Plug-ins require special handling when treated as reusable assets; they must first be installed into your local workbench before you use them. Examples of typical plug-in assets would be patterns, transformations, and tooling plug-ins for custom UML profiles. With the introduction of this new integration feature, you can not only publish plug-in assets to Rational Asset Manager and use Rational Asset Manager to govern search them, but also you can search and discover assets that you want to use and have them installed in your workbench environment.

                  Back to top



                  Rational Asset Manager Client
                  Categorization and tagging of assets is now supported in the asset publishing dialog. The new Categories tab lists all the possible subcategories than can be assigned to an asset. Note that some categories can be restricted to particular asset communities by the server. You can use the Tags tab to insert or remove tags set for the asset.

                  Back to top



                  WebSphere Business Modeler integration
                  • WebSphere Business Modeler integration now supports models created with version 6.2 of WebSphere Business Modeler.
                  • WebSphere Business Modeler integration now supports adding the implementation type of the local tasks in WebSphere Business Modeler models such as Dynamic Assembler and Human task in the form of keywords in the associated UML elements CallOperationActions/CallBehaviorActions.
                  • WebSphere Business Modeler integration now supports generating CallOperationAction actions when the local human task is associated with a role in the WebSphere Business Modeler model.

                  Back to top



                  InfoSphere Data Architect integration
                  IBM InfoSphere Data Architect is the new name for Rational Data Architect. This product includes a feature to transform a Logical Data Model into a UML class model. This complements the transformation that is packaged with the Rational UML modeling products that creates a Logical Data Model based on a UML class model. By integrating InfoSphere Data Architect with the product, you can transform a UML class model into a logical data model as supported by InfoSphere Data Architect.

                  Back to top



                  Transformation core
                  • In a transformation configuration, you can specify that the transformation use the workspace as either the source or target. You can configure this option on the Source and Target page of the New Transformation Configuration wizard and the transformation configuration editor.
                  • The transformation debug log now contains time stamps that indicate when each transformation element runs.

                  Back to top



                  UML modeler
                • Support for an active language has now been added.
                  To modify the active language default settings, complete the following steps:
                  1. Click Window > Preferences.
                  2. In the Preferences window, expand Modeling and click Active Language.

                  In addition, you can add multiple languages to a constraint from the Properties view.
                • You can change the line width for connectors in the diagram editor.
                  To change connector line width, in the diagram editor, right-click a connector; then click Format > Line Width and select the appropriate size.

                  To change the line width from the Properties view, select the connector, open the Appearance tab and click the Line Width button.
                • An Open All Sub-Fragments option was added to the pop-up menu of fragments in the Project Explorer view.
                  To open all sub-fragments, in the Project Explorer view, right-click a fragment that contains other fragments and click Open All Sub-Fragments.
                • Public API was added for Redefinition support (com.ibm.xtools.uml.redefinition).
                • A preference was added to control expanding the message to the length of the message to display the full method signature's text.
                  To modify this preference, complete the following steps:
                  1. Click Window > Preferences.
                  2. In the Preferences window, expand Modeling and UML Diagrams; then click Sequence and Communication.
                  3. Select Set initial message label width to distance between source and target lifelines.
                • You can now upgrade a model and all the fragments that it owns to the latest version of the product at the same time, instead of individually.
                  Upgrading a model and its owned fragments at the same time saves time and memory resources because the model and fragments do not have to go through the silent migration process each time that you load the model.

                  To upgrade a model and its owned fragments at the same time, complete the following steps:
                  1. Open the model to upgrade and ensure that you have both read and write access to all the owned fragments.
                  2. After the model fully loads, in the Model Editor view, click the Details tab.
                  3. Under Model Operations, click Upgrade. The Upgrade Model window opens and warns that the product might appear unresponsive for an unknown length of time, and that you should not interrupt the process until the migration is complete.
                  4. To upgrade the model and its related fragments, click Yes.
                • In communication diagrams, you can choose from a list of operations when you assign operations to messages. This is consistent with sequence diagram behavior.
                • A preference was added to specify whether colors of stereotype images are preserved.

                  To modify this preference, complete the following steps:
                  1. Click Window > Preferences.
                  2. In the Preferences window, expand Modeling and Appearance; then click Shapes and select Retain original colors of stereotype images.
                • Event management has been improved:
                  • A validation rule has been developed to find unreferenced events in models. This rule initially only examines in-memory models. To search all models in the workspace, open the Quick Fix dialog box from a problem corresponding to this rule. You will then be given the option to search for all unreferenced events for all models in the workspace. You can also use the Quick Fix dialog box to delete the unreferenced Events.
                  • The Refactor or Delete operation for collaboration elements, interaction elements, and other sequence diagram elements now verifies if events will become unreferenced after a Delete operation. Events which will become unreferenced are listed in the Preview page of the Refactor wizard. You can clear the check boxes corresponding to the events you want to keep. Also, the Refactor or Delete action can now be started from the sequence diagram in addition to the Project Explorer view.
                  • You can now reuse events. The Properties view for message elements now contains a new section that lists associated events for the selected message. From this section, you can select applicable events for the message.
                  • Refactor and Move operations are now supported for collaboration and interaction elements.
                • When you add a state to an object node typed by a classifier, you can now select only valid states.
                • The operations property tab contains a column that displays the owner of the operation.
                  You can use this column to determine which operations are local and which are inherited.
                • Show Related Elements, Show/Hide Relationships, and topic diagrams now support link relationships.
                • Memory optimizations have been implemented to assist with loading and validating larger models.
                  To take advantage of these optimizations, you can add one or both of these parameters to the eclipse.ini configuration file:
                  • Dcom.ibm.xtools.trimResourceIdToEObjectMap=1
                  Adding this parameter will only populate the entries of the map on demand (i.e. when something is requested from the map). It assumes no clients are requesting the map directly.
                  • Dcom.ibm.xtools.modeler.disableAdapterMapsDuringFragmentLoad=1
                  Adding this parameter will free up the adapter maps before loading, then repopulate them after the loading is complete. This results in more available memory during the load and validation.
                • The Format > Snap Back command is now supported on state machine diagrams.
                  This command "snaps" the name back to the diagram element that it is associated with.
                • The Navigate > Show in > Project Explorer command from the diagram editor now takes context into account.
                  This command now locates the corresponding element under the nearest imported element in scope, using the diagram as the context.
                • State invariant elements are now supported in sequence diagrams.
                  To add a state invariant, in the Sequence Palette, click State Invariant and then click an existing lifeline in the sequence diagram.

                  Back to top



                  User assistance
                  • A tutorial, Create a BIRT report design for a UML model, was added to the documentation. The tutorial shows how to use the Business Intelligence and Reporting Tools (BIRT) to design a report for UML models. The tutorial provides information about creating data sources and data sets to supply report content, and about using the BIRT user interface to format reports. Also read new articles on IBM developerWorks® on topics related to using BIRT to report against UML models and RequisitePro requirements.

                  Back to top

                  Version 7.5
                  Download Version 7.5


                  This release of Rational Software Modeler contains new features and enhancements in the following areas:
                  • Extensibility and pattern-based engineering
                  • Model-based analytics and compliance
                  • UML usability and model management
                  • UML modeling
                  • Compare and merge
                  • Transformations




                  • Extensibility and pattern-based engineering
                  • Model-to-model transformation authoring
                    The mapping metamodel was extended to include a new mapping type: custom submap. This new mapping type enables you to invoke another transformation from within the code that is associated with a custom mapping.

                    You can now change the path to referenced source or target files when a transformation is created.

                    Transformation source code can be generated in a customized transformation framework. The model-to-model transformation framework was improved to support transform outputs other than existing model files. Transformation authors can set default workspace and project-specific code generation properties.
                  • Model-to-text transformation authoring
                    Markers on replaceable text are now more visible. They have clearly worded descriptions, and can be easily distinguished from other markers in the Problem view. In the Package Explorer and the Project Explorer views, markers, and any containing folders, are decorated with an icon that indicates the presence of replaceable text. In the JET authoring editor, actions are decorated with an icon if the corresponding templates contain markers.

                    You can integrate JET with model-to-model or profile tooling using the new "UML Interface to a JET transformation wizard, which steps you through the generation of a “front-end” model-to-model transformation. You can automatically generate an EMF project, model, and Java code, generate a UML profile project, or create a model-to-model project in which the appropriate input and output metamodels are configured and the corresponding JET invocation code generated.
                  • Patterns
                    The design pattern content library now uses the specialized pattern framework, which handles read-only models better by ensuring that only elements in the pattern instance model of interest receive writes. Traceability support and keyword functionality for roles is now built-in to the specialized framework.

                    UML profile support at authoring and application time now supports profile enumerations to be used as pattern parameters. This means that you can bind a type in a custom pattern to a type in a custom stereotype.
                  • UML profiles and profiles tooling
                    You can visualize stereotypes, profiles, stereotype applications, and profile applications in modeling diagrams. You can also query these types of elements in diagrams by using the Explore palette.

                    The Tooling Model profile was updated to include elements that enable you to model custom properties view contributions and templates were added to support the generation of the Properties view code.

                    You can now repair or remove broken profile applications from the Model Editor. In particular, the Remove button is now enabled for unresolved profiles and the Repair button is added for unresolved profiles.
                  • Query
                    The topic diagram wizard was updated to enable you to create new query files from registered query types. You can create custom queries as topic artifacts and preview the results in the Topic diagram.

                    A new “Queries” virtual folder was added to the Project Explorer view to display all of the .tpx files as query objects that you can drag and drop on to a diagram.
                    Back to top


                    Model-based analytics and compliance
                  • Rational Asset Manager integration
                    You can integrate the Rational modeling products and deployment architecture tools with Rational Asset Manager to publish, search, and import modeling artifacts and to publish reusable topology assets.

                    When models are published using Rational Asset Manager, the references are relative to the Web server.
                  • Traceability analysis
                    You can create dependency and traceability relationships between model elements, or their contained Operations, attributes, or parameters, directly in the Project Explorer view, without having to create diagrams.

                    A Relations tab was added to the Properties view, which displays a list of all the relationships That an element is involved in. You can create, delete, or navigate to these relationships from the Properties view.
                  • Model reporting
                    • Improved the EMF/UML ODA datasource and dataset dialog boxes by enhancing the performance (on-demand browsing of models), the layout (resizable sections), and usability (browser contents based on model type, context sensitive xpath proposals, more xpath APIs, better xpath syntax checking.)
                    • Added support for parameterized dataset for EMF/UML ODA driver. You can define parameters for a dataset, used in the xpath expressions of row and column mapping and then bound to values at runtime.
                    • Removed the report generation functionality from the Report Explorer view and added a new Report Configuration Wizard. You can use the wizard to create multiple configurations with specifying report templates, source instance models, report parameters, and optional model transformations.
                  • Printing
                    The Print Preview functionality now takes the Scaling and Fit to page settings into account. You can change the scale factor and print to a page from the Print Preview dialog box.

                    Back to top


                    UML usability and model management
                  • Top-level packages
                    The most commonly used root element for reusable model constructs is a simple package. To support this convention, you can now define top-level UML packages as the root element, rather than Models. You can import or merge them into any number of logical models.

                    You can convert a root package into a model and a model into a root package by using the Refactor popup menu in the Project Explorer view.
                  • Expand in place
                    The Project Explorer view and Select Element dialog box now display the imported elements for element imports and package imports. This permits you to view a collection of UML models in a hierarchical view. You can browse and work with these imported elements (including models and packages) in the importing model. You can also browse shared resources.
                  • Refactoring
                    When refactoring, you are now identify the resources that will be affected by pressing the Preview button. You are can also deselect closed resources to prevent them from being updated (for example, if you only have read only access to those files).
                  • Expanding closed models and fragments from the Project Explorer view
                    You can open closed models and fragments by expanding them in Project Explorer view. This will open the model, allowing you to browse the model elements without opening the model's main diagram or Model Editor.
                  • Modeling working sets
                    You can use modeling working sets to reduce the modeling content in the Project Explorer view. You specify the working sets that you want to use when you create a new model or a new profile. You can also add new or existing models to modeling working set.
                  • Content filtering viewpoints
                    As with the palettes and popup menus, action bars and connector flyouts reflect the capabilities that you have enabled. The Viewpoint preferences page has been updated to include Content Filter options that enable you to select the set of filters that match the viewpoint. When you change the viewpoint in the workbench, all elements in the Project Explorer view that are not included in the selected filter set are not displayed.
                  • Automatic reporting and repair of unresolved references
                    A new broken references dialog replaces the missing resources dialog. You can choose to repair, mark problems, or ignore the broken references. Some unresolved references shown in the Problems view can be corrected by using the Quickfix menu item.
                  • Group/ungroup support
                    Modeling elements can be grouped together and operations such as cut, copy, move, and delete can be performed on them.
                  • Preferences
                    The preferences have been rearranged in more logical groups. In addition, several new preferences have been added to control the display of compartments and titles, name and roles, multiplicity, and class shapes on use-case diagrams.

                    Back to top


                    UML modeling
                  • Freeform diagrams
                    You can now use arrowheads to show connections between the geometric shapes, and you can choose the style of line to use.
                  • Activity diagrams
                    Flow creation has been simplified. The Flow tool, which replaces the Control Flow and Object Flow, automatically creates the correct flow type. In addition, flow re-orienting between object nodes, control nodes and actions is now supported by automatically completing the context, such as adding pins, or morphing object flows and control flows where required. (You may re-enable the previous two flow tools by enabling the UML Activity 4 capability under UML Element Building Blocks from the General, Capabilities preference page and clicking the Advanced button.)

                    To reduce the complexity of the diagram, you can hide pins on actions inside activity diagrams. You can connect flows to existing hidden pins and toggle whether pins should be hidden or shown on individual activity diagrams.all Behavior Actions and Call Operation Action names can now be kept in sync with the referenced Behavior or Operation. This will work automatically when the Call Action has a blank name. If the Call Action's name is not blank, it is reported in the Problems view.
                  • Sequence diagrams
                    You can now copy and paste sequence diagram elements within and between sequence diagrams, and copy and paste interactions within the Project Explorer view. The paste operation is now context aware and will reuse existing lifelines and elements when possible.

                    You can refactor sections of a sequence diagram into a new sequence diagram, and the new sequence diagram can be referenced through an InteractionUse.

                    Non-integer types are supported for guard conditions. Support has also been added to specify Boolean expressions in the guard condition of a loop combined fragment and to specify opaque expressions for minimum integer and maximum integer in the guard condition of a loop combined fragment.

                    Message argument values can be specified using the Properties view for a message. You can add and delete argument values, change the argument type, change the argument value, reorder existing argument values, and populate argument values for all message arguments.

                    Back to top


                    Compare and merge
                  • For a large model with many fragments, full context (logical model) merging can take a significant amount of time. Sparse model merge speeds this up significantly, as only those fragments that actually changed are loaded, along with their parent containers up to the root of the logical model. However, there are side-effects, particularly the appearance of broken references where fragments are missing. This does not affect the merge result.

                    The new Text view allows you to see the full contents of multi-line text fields.

                    The top level model object can be converted to UML package. Thus, we provided the ability of comparing and merging objects of these two Meta model classes.

                    In activity diagrams, a control flow can be converted to an object flow and vice versa. You can compare and merge objects of these two Meta model classes.

                    You can use the "-modelAlignment" option in an existing "logdeltas" command line for comparing model files with different root model ids. The logdeltas command line is used to compare two model files and output the differences in XML format. You can open and review the XML log file by using the Model Delta annotation viewer.

                    You can select the base and the contributor when comparing two models. This option is on the Preference page, under General > Compare/Patch > Modeling Compare/Merge > EMF Compare/Merge.

                    You can set the visibility of panes in the Combine Model dialog box to persist automatically. This option is on the Preference page, under General > Compare/Patch > Modeling Compare/Merge > Combine Models Merge.

                    You can integrate the Rational modeling products with Rational Team Concert.

                    Back to top


                    Transformations
                  • Transformation core
                    Authors of transformation extensions can now contribute pages to the transformation wizard and editor. New extensions can also participate in validation.

                    You can now enable or disable transformation extensions on a per transformation configuration basis. A new Extensions page has been added to the transformation configuration wizard; it displays the available forward and reverse transformations, making you aware of the extensions and allow you to choose when to use them.

                    When an error or a warning occurs while a transformation is running, an entry is made in the error log. An error reporting tool has been added to the transformation framework that opens a dialog box in which the errors and warnings are displayed. Errors and warnings that are associated with a transformation configuration can become stale. You can run validation to refresh the messages.
                    Users are adopting the Design Contract Management Protocols, DCMPs (formally known as theories of operations). Three of the five DCMPs are applicable for transformations: conceptual, mixed and reconciled. They are included in the new transformation configuration wizard and the transformation configuration editor, allowing you to choose which DCMP you want to use.

                    The transformation mapping utility now uses a workspace path to refer to the mapping model, rather than a file system path. When you use a transformation configuration from an earlier release, it will automatically be converted to a workspace path.
                    Collections and Maps are supported transformation property values.

                    Back to top


                  • Rate this page:

                    (0 users)Average rating

                    Document information


                    More support for:

                    Rational Software Modeler
                    General Information

                    Software version:

                    7.5, 7.5.1, 7.5.2, 7.5.3, 7.5.4, 7.5.5, 7.5.5.1, 7.5.5.2, 7.5.5.3, 7.5.5.4, 7.5.5.5

                    Operating system(s):

                    Linux, Windows

                    Reference #:

                    7014041

                    Modified date:

                    2011-06-29

                    Translate my page

                    Machine Translation

                    Content navigation