IBM Support

Rational Software Architect RealTime Edition Version 7.5.x Releases: New Features and Enhancements

Product Documentation


Abstract

IBM® Rational® Software Architect RealTime Edition 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

The following is a summary of enhancements made available in the version 7.5.5.x release.

Table of contents:


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.5.2
Download Version 7.5.5.2


This release of Rational Software Architect RealTime Edition contains contains new features and enhancements in the following areas:


Eclipse platform updates
The following additional 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, Linux, and Solaris operating systems:
  • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 6.0 service release 8
  • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 6.0 service release 8
  • IBM 32-bit Runtime Environment for Solaris, Java Technology Edition, Version 6.0 service release 8

Back to top




Rational Rose RealTime model import
A new option has been added to the Rose RealTime Import wizard to give you the option to preserve the default colors of Rational Rose RealTime models or use the default colors of Rational Software Architect RealTime Edition models during model import.

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 Architect RealTime Edition contains contains new features and enhancements in the following areas:



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 6.0 service release 7 plus interim fix 001
  • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 6.0 service release 7
  • IBM 32-bit Runtime Environment for Solaris, Java Technology Edition, Version 6.0 service release 7

Back to top




RealTime modeling
The following RealTime modeling enhancements are introduced in this release:
  • The selection of a search result from model search now also updates the code view to show the code snippet containing the search result match.
  • Now code view is enhanced to use annotations to highlight match results from a model search.
  • A browse button is added for the multiplicity for ports and capsule parts. Now, the importer creates OpaqueExpressions rather than LiteralStrings for multiplicity to be consistent with the modeler UI.

Back to top




Rational Rose RealTime model import
Rational Rose RealTime model import now creates top region state machine diagrams during import for passive classes that have statemachines.

Back to top




UML-to-RealTime C++ transformation
The ant task, to execute a transformati on configuration and build the related target projects, now has the optional attribute 'markerFailureThreshold' which can be used as shown in the example below.

Possible values for markerFailureThreshold are "info", "warning", and "error". Other values are treated as if the attribute were absent:

<com.ibm.xtools.umldt.buildTransformationConfiguration
markerFailureThreshold = "error"
invokeTargetBuild = "incremental"
transformConfig = "hello/main.tc"/>

In this case if any of the target projects of main.tc or its prerequisites have problem
markers with severity error, the task will fail with the message:

Problems found in project "{target-project-name}"

Back to top




UML-to-XSD and UML-to-WSDL transformations
XSD polymorphism and substitution groups are now supported by an extension to the UML-to-XSD and UML-to-WSDL transformations. When the transformation runs with this extension enabled, the transformation generates global elements that support XSD polymorphism and substitution groups.

To enable this extension, create or open a transformation configuration file for a UML-to-XSD or UML-to-WSDL transformation, and in the transformation configuration editor, on the Extensions page, select the check box for the Support for XSD polymorphism and substitution groups extension.

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.


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&amp;uid=swg27017935.

Back to top



Version 7.5.5
Download Version 7.5.5


This release of Rational Software Architect RealTime Edition contains contains new features and enhancements in the following areas:



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 6.0 service release 6 plus interim fix
  • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 6.0 service release 6 plus interim fix
  • IBM 32-bit Runtime Environment for Solaris, Java Technology Edition, Version 6.0 service release 6 plus interim fix

Back to top




RealTime modeling
  • The search results of the Find Connected Ports action can now traverse relay ports (non-behaviour) to find the behavior ports that actually terminate the event by having its owning classifier's behavior handle it.
  • This enhancement simplifies your work flow by providing quick access to all local, inherited, or redefined outgoing transitions in the Code View drop-down list by simply selecting the choice or junction point directly.

Back to top




C++ domain modeling
The harvest of visualized C++ folders is now governed by new preference options under Visualization of folders in a diagram (for harvest functionality). The default option of this preference is set to Visualize folders only. By default, on harvest and paste of the folder, none of the contained elements within a folder are harvested into the target. If the option Visualize both folders and their contents is selected prior to the visualization of the C++ folder, on harvest and paste of the folder, all of the contained elements within the folder are harvested into the target. For any change made to the preference options to take effect, you must close and reopen the project containing the visualized element.

Back to top




C++-to-UML and UML-to-C++ transformations
  • In the Modeling perspective, on the C++ Properties page for a dependency relationship, you can specify the dependency type (inclusion, forward reference, or none) that the transformation generates in the header and source files.
  • When you run the C++-to-UML transformation, if the source file contains a single classifier and a forward reference to a target type, the transformation generates a dependency relationship between the target type and the classifier.
  • Capsule development projects can now be built in incremental mode to improve build performance. You can use the new Run transformation configurations only when there are Eclipse resource or model changes option, which is available on the UML Development page of the Preferences window.

Back to top




UML-to-CORBA transformation
The UML-to-CORBA transformation now supports the CORBA 2.6 specification and the following keywords: union, truncatable, context, ValueBase, and fixed.

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 Architect RealTime Edition 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 Architect RealTime Edition contains contains new features and enhancements in the following areas:



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, Linux, and Solaris operating systems:
  • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 6.0 service release 5 plus interim fix
  • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 6.0 service release 5 plus interim fix
  • IBM 32-bit Runtime Environment for Solaris, Java Technology Edition, Version 6.0 service release 5 plus interim fix

Back to top




RealTime services and modeling
  • A new operation combo-box is now available in the code view allowing you to select any local or inherited operation in a Class or Capsule. It will also reflect selection changes on the operation tab in the Class Properties View.
  • Syntax highlighting and better code editing capabilities have been integrated into the "RT Properties" code properties such as "Header Preface".
  • There is new navigation back into the Model from the Code View. If you select some code that has a direct mapping into the model, you can navigate to it's declaration in the Project Explorer view or diagram.
  • Interactions are directly owned by the classifier in UML 2 meta-model. Consequently when opening a Class or Capsule with many owned sequence diagrams, it doesn't scale well in the Project Explorer view. Now there is a virtual folder. You can configure the filter in the Preferences window (Window > Preferences > Views > Project Explorer).
  • Native type usability has been improved dramatically. Now native language types can be specified directly in the UML type field on the General tab. The Type field is now editable and supports direct entry of a non UML type, such as int *. This is available for attribute and parameter types.
  • You can now edit the transformation configuration files directly on the diagram. Transformation configuration files can be added, deleted, and have their relationships (pre-requisites and inheritance) modified on the diagram surface instead of having to open the Transformation Configuration editor to do it manually.
  • In editing code for transition effects, entry and exit actions and operations plays a large role in the development of a RealTime model. Consequently when two users modify the same code fragment, the ability to merge these changes in a seamless and efficient way is paramount.

    • The merge of these code fragments, therefore, has been improved dramatically recognizing that these are first class elements in the UML model. Now when code fragments conflict in the CM system, the compare and merge UI will pop-up with the language specific code merge pane open by default.

Back to top




Rational Rose RealTime model import
  • Previously the importer respected the Rational Rose® RealTime controlled unit organization and named and located the imported fragments according to the corresponding controlled unit. But when creating new fragments you would be faced with inconsistent naming and containment paradigms unless you explicitly located the new fragment and overrode the default UML modeler behavior. Now the import wizard supports a mode where you can choose to import the controlled units by using the same flat containment and generic naming that UML modeler uses for its default behavior. In addition, you can specify a subfolder where the fragments are located as opposed to having them created flat in the owning project.
  • In the import wizard there is a new Interaction Settings group which allows for different semantic mappings during import for co-regions and constraints. The default mapping for co-regions is now the true UML 2 semantic mapping to a Parallel Combined Fragment. In addition constraints can be mapping to State Invariant elements which are attached to the lifeline. And, for models that were imported previously, we have provided refactoring commands to do the same semantic change after the import.

Back to top




3GL domain modeling
New pop-up menus are now available from the Package or Project Explorer view and in domain modeling class diagrams. You can now delete domain modeling elements from both a class diagram and the project or from only the diagram.

Back to top




C/C++ Domain modeling
  • Method signature refactor is now supported on visualized C++ methods. Along with the ability to add/delete parameters or change parameter order/name/type, method qualifiers like const, virtual, inline can also be changed on the method.
  • C++ method bodies can now be visualized onto a static method sequence diagram. The visualization is supported to the first level of method calls.
  • Cut, copy, and paste options are now supported on visualized C++ fields and methods. C++ fields and methods can now be copied, cut, and pasted from a class and file container to the same class and file container or a different class and file container in a domain modeling C++ class diagram. Conflicts with the existing elements of same name or signature are also taken care of.
  • C++ include statements can now be added visually between two visualized C++ header and source files by drawing a <<use>> relationship between them.

Back to top




Java domain modeling
  • A new option is added to the Java domain modeling Preferences page and you can now decide to show or hide annotation compartments of Java classifiers in domain modeling class diagrams.
  • A pop-up editor is now available for Java classifiers in domain modeling class diagrams. When you select a Java class or interface in a class diagram, a code editor pops up for you to edit the Java code.
  • Relationships between UML model elements and domain modeling elements are now supported.

    • You can also show relationships between elements from different domains, for example, between WSDL and Java elements in a domain modeling class diagram.
  • A new Preferences option is added for you to filter elements in static method sequence diagrams.
  • The Java domain modeling capabilities are enhanced for you to complete the following tasks:
    • Visualize projects and show project dependencies based on Java class path.
    • Visualize package dependencies.
    • Visualize package and project contents in a new or open diagram from the Project and Package Explorer view.
    • Visualize the contents of a Java project, package, and classifier in a new class diagram by using the pop-up menu from a open class diagram.
  • When you right-click a Java classifier in a class diagram and then click Navigate > Navigate to source, the Java editor opens just below the diagram.

Back to top




C++-to-UML and UML-to-C++ transformations
  • Visualized C++ elements that are generated by a UML-to-C++ transformation that is configured to create trace relationships are now updated automatically to contain the changes in the corresponding model elements when you rerun the UML-to-C++ transformation.
  • When you run a C++-to-UML transformation, the following filters are now available in the Merge window:
  • Primitive type conversions
  • Invalid name conversions
  • Default operation name changes
  • Parameter documentation changes
  • Multiplicity lower upper bound

Back to top




Java transformations
  • A transformation configuration option is now available to generate associations automatically when you run a Java-to-UML-transformation. The transformation generates one directed association for each Java field.

    • To be consistent with existing transformations, by default, this option is not enabled.
    To select this option, on the Main page of the transformation configuration editor, select the Generate a UML association for each Java field check box.
  • For UML-to-Java transformations, an option to link all generated Java code elements to the corresponding UML model elements is now available. This feature is useful when code is added to the generated Java code and the UML model, but there is no link between the added code in these models.

    • When you create or edit a UML-to-Java transformation configuration, to link the generated Java code elements to the corresponding UML elements, in the transformation configuration editor, click Link Java to UML.
  • Several Java interfaces are now available to provide more flexibility for authoring Java transformation extensions.
  • Authors of Java transformation extensions can access or override the following interfaces in the transformation context:
    • com.ibm.xtools.transform.java.common.util.IRootCertifier: Use this interface to redefine the root element of a Java transformation.
    • com.ibm.xtools.transform.uml2.java5.util.ICompilationUnitSerializer: Use this interface to customize how elements are written out.
    • com.ibm.xtools.transform.uml2.java5.util.IMergeUtility: Use this interface to customize how elements are merged.
    • com.ibm.xtools.transform.uml2.java5.util.IUML2JavaAPI: This interface provides functions for creating new compilation units, type references, and for setting the body of a Java method to a string. Transformation extension authors should not override this interface.
    • com.ibm.xtools.transform.java.uml.util.IJavaUMLAPI: This interface provides functions for adding filters to the Java-to-UML transformation merge utility. Transformation extension authors should not override this interface.

Back to top




XSD-to-UML and UML-toXSD transformations
  • Enhanced the XSD-to-UML transformation to become a reverse transformation to the UML-XSD transformation.
  • Enhanced the "Auxiliary sources and target" tab to easily discover the XSD source files' auxiliary files when you click the Discover Auxiliary Sources button.
  • Enhanced the UML-to-XSD transformation to become a reverse transformation to the XSD-UML transformation.

Back to top




XSD profiling
This feature provides a new palette for the profile, providing tools to easily generate the modeling artifacts used by the UML-to-XSD transformation. The palette appears on Class diagrams and free form diagrams. You can enable this palette by enabling the diagram capability "XSD Transformation Profile" in the properties view of the root model node.

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 Architect RealTime Edition contains contains new features and enhancements in the following areas:




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®, Linux, and Solaris operating systems:
  • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 6.0 service release 5
  • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 6.0 service release 5
  • IBM 32-bit Runtime Environment for Solaris, Java Technology Edition, Version 6.0 service release 5

Back to top




Java transformations
The following enhancements have been made to Java transformations:
  • Several profile changes have been made to assist in modeling for UML-to-Java and Java-to-UML transformations:
    • If The <<JavaWildcard>> stereotype may now be applied to a UML class allowing a wildcard to be the type of either a typed element of multiplicity or for a typed element with a <<JavaCollection>> stereotype.
    • The current <<JavaCollection>> stereotype has been deprecated, and a replacement added with the same name that allows the key type property used in Map collection to be a UML type instead of a string. This would allow a <<JavaWildcard>> UML class to be the keytype of a Map.
    • A new stereotype <<JavaRedirect>> has been added that can be applied to any UML type. It has a single property called "redirect" that will redirect to any other UML type. The UML to Java transformation will generate all references to the <<JavaRedirect>> as the redirected type instead. This allows for any type to be specified as a UML template parameter, for the purposes of Java code generation.
  • A new extension has been added to UML-to-Java transformation that can be enabled in a UML-to-Java transformation configuration. This extension generates the names of all getters and setters by using the get/set<field name first letter uppercase> string, rather than following the Java naming conventions. This can result in a difference for getters and setters of boolean fields.

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. Y
  • You can now write pages that display in the transformation configuration editor or wizard and support inheritance.

Back to top




RealTime services and modeling
The following enhancements have been made to RealTime services and modeling:
  • Two new filters have been added to the Project Explorer view to filter out top-level elements under the virtual transformation configurations folder: one to filter out transform configurations that are abstract, and the other to filter out C++ libraries and external libraries. Additionally, a new sub-menu, Toggle Project Explorer Filters, has been added to the virtual folder to toggle these two filters.
  • Various operations have been added and you can now revert and override property values. While viewing a transformation configuration (TC) in the Transformation Configuration Editor, you can find these operations in the pop-up menus of individual properties. These operations are only available for transformation configurations that inherit other configurations.
  • You can now specify the target location by setting OutputDirectory in the component specification C++ Generation tab. This property is available in the product on the Source and Target tab. The property is named Location and operates similarly to the Location property in the New C++ Project window. The default value set for Location is the workspace. A Browse button allows the location to be changed. This option is only relevant when the Generate Target Project check box is selected.
  • Unspecified messages (messages that are not associated with an operation or call event) now support message arguments, which you can define on the Properties tab. The sequence diagram displays the message arguments.

Back to top




UML-to-XSD and XSD-to-UML transformations
UML-to-XSD and XSD-to-UML transformations have been enhanced to support the generation of restrictions for complex types.
  • A change has been made to the behavior of the UML-to-XSD transformation with respect to the handling of generalization relationships between two complex type classes:
    • If a generalization relationship has no stereotype, it is transformed to an XSD "extension".
    • If a generalization relationship has "restriction" stereotype, it is transformed to an XSD "restriction".
  • The XSD-to-UML transformation generates the "restriction" stereotype when processing a restriction relationship, but does not generate any stereotype when processing an extension relationship.

Back to top

[{"Product":{"code":"SS5JSH","label":"Rational Software Architect RealTime Edition"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"General Information","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.5.3;7.5.4;7.5.5;7.5.5.1;7.5.5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2018

UID

swg27015877

Page Feedback