Rational Systems Developer, Version 7.0.5 Release Information

Content

• About this release
• Cumulative updates
• New in this release
• Fixed APARs contained in this release
• System requirements
• Hardware requirements
• Software requirements
• Installation information
• Installation scenarios
• Installing Rational Systems Developer, Version 7.0.5 as an update from the CDs
• Installing new features in the refresh pack from the CDs
• Installing Rational Systems Developer, Version 7.0.5 from the CDs as a new installation or another instance of it
• Installing Rational Systems Developer, Version 7.0.5 for the first time on Windows Vista
• Installation notes for Windows Vista
• Starting Rational Systems Developer, Version 7.0.5 on a Windows Vista computer
• Uninstalling the refresh pack
• Known limitations, problems, and workarounds
• IBM Rational Software Support
• Trademarks and service marks

---


Cumulative updates
This version includes all fixes, enhancements, and new features from the following fix packs:

• Rational Systems Developer, Version 7.0.0.4


• Rational Systems Developer, Version 7.0.0.3


• Rational Systems Developer, Version 7.0.0.2


• Rational Systems Developer, Version 7.0.0.1



In addition, see the Release Notes for version 7.0 of IBM Rational Systems Developer to learn about its new features and any limitations or problems known at the time of its release.

Back to top



---

New this release

This release of Rational Systems Developer contains new features and enhancements in the following areas:

• Platform, operating system, and utility software support enhancements
• New installable features
• UML usability and model management
• Model-based analytics and compliance
• Code-based modeling and packaged transformations
• C# transformations
• CDT 4.0 - C++ Integrated Development Environment
• Team integrations
• Extensibility and pattern-based engineering
• User assistance



---


Platform, operating system, and utility software support enhancements:
• Microsoft® Windows® XP Professional x64 Edition (running in 32-bit mode on AMD and Intel® processors)
• Citrix Presentation Server on the following operating systems:
• Microsoft Windows Server 2003 Standard Edition
• Microsoft Windows Server 2003 Enterprise Edition
• Sun® Solaris™ 10 (running in 32-bit mode on SPARC processors)

For information about specific issues or problems when running Rational Systems Developer on Solaris, see the technote.
• Eclipse 3.3.1.1

For compatibility with previous releases and known issues, see the Eclipse 3.3.1.1 Project Release Notes.
Important: The upgrade to Eclipse 3.3.1.1 has specific implications if you use other IBM products or third-party plug-ins that are installed in the same Eclipse IDE with the product. For information about known issues with interoperation between Rational Systems Developer, Rational Software Modeler, Version 7.0.5, and other Rational products, see the technote.
• IBM Installation Manager, Version 1.1.0.1

For information about working with Installation Manager, visit the Installation Manager Information Center.

Back to top


---


New installable features
This refresh pack include the following new features that you can add to installed product packages:

Important: New installable product features are not displayed and cannot be added to the installed product packages when you run the Update Packages wizard in IBM Installation Manager. To find and add new installable product features, run the Modify Packages wizard in Installation Manager after you have updated the installed product packages with this refresh pack. For details, see the Installing new features in the refresh pack from the CDs section below.
• UML model analysis and metrics

The products can now generate metrics that cover various aspects of UML modeling including size, nesting, complexity, inheritance, cohesion, and coupling. You can run a UML Metrics analysis configuration on a UML model to collect information about the model and determine whether it follows established best practices.

You can also create custom metrics by adding rule templates under Preferences > Analysis > Custom Rules and Categories.

The results are collected and displayed in a metric results model, with one entry for each metric that captures the elements being analyzed and the computed metric value for each element.

• Model Web publishing and reporting based on XSLT templates

By using the enhancements in this feature, you can publish UML models as HTML documents and generate customized model reports based on the Extensible Stylesheet Language Transformations (XSLT) templates. The XSLT-based reporting approach was introduced in early versions of the modeling products and, while now deprecated, continues to be available for those customers who built customized reports using this technology.

• BIRT-based model reporting

The IBM Rational modeling products extend the Business Intelligence and Reporting Tools (BIRT) component so that you can use the BIRT report-design and production capabilities to create reports based on the contents of EMF and UML models. You can create custom report designs, or apply ready-to-use BIRT-compatible report designs.

With the modeling products' extension of BIRT, you can create data sets based on EMF and UML models. These data sets select model content and organize it for compatibility with BIRT report designs. The data sets support all the features of the models; for example, UML models support UML extensibility features by using profiles and stereotypes.

Back to top


---


UML usability and model management

• Configurable UML menus and palettes

The IBM Rational modeling products provide mechanisms that you can use to configure and simplify the user interface for UML modeling. You can use these tools to enable or disable UML "building blocks." Each building block is predefined in the product and represents either a UML diagram type or a specific collection of UML semantic elements.

When a particular building block is enabled, the elements that it represents appear in the drawing palettes and on the Add UML (or Add Diagram) pop-up menus. When the building block is disabled, those elements no longer appear. You can specify which building blocks are enabled in two ways. Both ways enable you to define a set of capabilities that are relevant to your role, and that filter all unnecessary tools.

One way to configure the available tools is as a set of properties that the root node of a specific model owns. The products now provide several model templates that are preconfigured with certain building block settings. The other way is to configure the set of building blocks that are associated with a "Modeling Viewpoint," which is a new user interface construct that is introduced in this version of the products.

• Extensible new model wizard

The New Model wizard is an extensible wizard framework that provides a centralized means of creating models. You can use the wizard framework to easily contribute model templates, as well as additional wizard pages.

• Rich text editing support

Rich text editing support is available for model, profile, and element documentation, diagram notes, and UML comments.

You can also convert the documentation from rich text to plain text, and plain text to rich text, by specifying a rich text preference and invoking the Refactor pop-up menu in the Project Explorer view. When you convert rich text content to plain text, the HTML tags are removed. This practice is useful when you want to open a model that contains rich text documentation in a previous version of the application. When you convert plain text content to rich text, the line breaks and tabs in the plain text are converted to HTML format.

Note: Rich text editing is only available for modeling products installed on Windows or Linux®; it is not supported on Solaris.

• UML Diagram enhancements

Several improvements were made to UML sequence, object, and deployment diagrams.
• Sequence diagrams

You can control the format of sequence labels for messages by choosing from three options on the Sequence diagrams preference page. You can hide sequence numbers, show the numbers as integers, or show hierarchical numbers with a user-defined number of digits.

When you create a new message in a sequence diagram, if you also create a new operation, you can now choose a destination class or interface for the new operation.

Support for moving and reordering elements was improved. Sequence diagrams now provide two modes: if a message set is selected, it is in reorder mode; otherwise, it is in move mode. You can now drag a message set to any location on the sequence diagram or move message sets into and out of combined fragments or between combined fragments.

• Object diagrams

Structure compartments are now available in component instances and node instances.

Using the Slots and Values page in the Properties view, you can specify multiple values for slots that are typed by attributes whose multiplicity is greater than 1. You can also delete values from the list. When a slot's value is modified, the changes are updated on the diagram. The slot's values are also displayed in the list compartment and the graphical compartment of the slot.

• Deployment diagrams

You can now add deployment relationships between artifacts and properties specified in the internal structure of a node. You can also add dependencies between deployment configurations and artifacts.

• Diagram support in profiles

Class diagrams support profiles and you can now visualize profile structures in class diagrams.

• Support for fragmenting diagrams

You can now save diagrams and topic diagrams as model fragments in the same way as you save packages and classes.

• Ability to disable cross model decorators

You can now disable cross model decorators from model diagrams.

• UML information flow element support

The IBM Rational modeling products now support information flow elements in UML diagrams. An information flow represents the communication of an information item from a source element to a target element, and is used to illustrate the communication of information between entities in a system.

You can add information flows to class, component, composite structure, use-case, deployment, activity, and object diagrams.

Read more about information flows in the latest version of the UML specification on the Object Management Group Web site (www.omg.org).
• Modeling compare and merge enhancement

A new option, Automatically accept resolvable differences for repository merge session, was added to modeling compare and merge. By default, this option is enabled. With this new option, a merge session is initialized with the base model and then all resolvable differences are automatically accepted. The base model is the ancestor model in a three way merge or the right model in a two way merge.

This option is located on the Window > Preferences > General > Compare/Patch > Modeling Compare/Merge page.

Back to top


---


Model-based analytics and compliance

• UML Profile for DoDAF and MODAF (UPDM) modeling

The UML Profile for DoDAF and MODAF (UPDM) specification provides a standard approach for modeling systems and enterprise architectures that supports both the U.S. Department of Defense Architecture Framework (DoDAF) and the UK Ministry of Defence Architecture Framework (MODAF). Using the integrated modeling tools, you can create models to describe the architecture of complex portfolios, enterprises, or systems that comply with UPDM.

UPDM modeling provides the following benefits:
• Improves interoperability of architecture data among architecture modeling tools
• Enhances reuse of architecture data
• Improves communication among DoDAF and MODAF stakeholders
• Supports definition of non-DoDAF/MODAF enterprise architectures
• Compatible with the Model-Driven Software Development (MDSD) methodology
• Traceability and impact analysis

You can use traceability and impact analysis tools to examine elements to discover which elements are related, to clarify their purpose, and to minimize the risk of change.
• Query support

Two separate queries are available to distinguish between impact analysis and refinement traceability in models. You can use traceability queries to discover the specifications and implementations of a context element, to understand why the context element exists, how the element is implemented, and to clarify the purpose of the element.

You can use impact analysis queries to discover the clients and suppliers of a context element that might be impacted by changes, and then visualize them in a diagram.

• Diagrammatic views of traceability and impact analyses

When you perform a traceability query, the results are displayed in a newly created diagram.

The Palette now includes an Explore tab that provides you with easy access to the Traceability and Impact analysis queries.

The results of a query can include an IBM Rational RequisitePro® requirement. A requirement edge can be displayed to represent a traceability link from a UML element to a requirement. A requirement node can be displayed to represent the requirement itself. In the Requirement Explorer view, you can navigate from a requirement node to the requirement record maintained in RequisitePro. If a requirement is renamed, the corresponding requirement node's name is updated.

Back to top


---


Code-based modeling and packaged transformations

• General transformation enhancements

Transformations now recognize Eclipse capabilities, which means that you can define a capability and bind a transformation to it.

If a transformation is bound to a disabled capability, the transformation is not available in the user interface. If you try to run a transformation that is bound to a disabled capability, you are prompted to enable the capability first.

• C++ transformations

When you create transformation configurations and run transformations, you can specify separate output folders for generated source and headers. When you run the transformation, all the header files are generated in the specified folder. The source files are generated in the same hierarchy as in the model, in the specified folder.

You can specify the option to include either the full path or the file name during a transformation. You can also specify that the #include statement is generated with the file name when you run the transform. If you choose this option, the relative path is not generated for the #include statements.

• C++ code modeling

The following enhancements were made to C++ code modeling:
• You can now visualize files that are not part of a project and are listed in the Project Explorer view in the Includes folder. The visualized external files are read-only.
• You can also view the properties for C++ visualized elements in the Properties view; however, the properties are read-only.
• Java transformations

The re-apply and reconciliation functionality for Java transformations has been enhanced to include new and improved merge filters and the use of trace relationships to match renamed or relocated elements in code or models.

The UML-level handling of Java exceptions and collections has been improved. You can now model operation exceptions by using the UML properties dialog box and by adding exceptions on the RaisedException page of the Properties view. The UML-to-Java and Java-to-UML transformations use this list to keep Java method exceptions in synch with the model. By applying the Java Transformation profile to a model or a package, you can use Java transformation stereotypes to accurately define a Java collection or array. These stereotypes can be applied to an attribute or an operation parameter.

Trace relationships are used to improve UML-to-Java and Java-to-UML model and code reconciliation. Specifically, the reconciliation GUI is more intelligent about recognizing when elements are renamed or moved. Trace relationships are generated by selecting "Create trace relationships" on the Common page of the UML-to-Java transformation configuration dialog box. Model identifiers are inserted into the generated Java code as part of the @generated tag in the generated comments for each element. These enhancements to refactoring greatly improve the reconciliation experience.

There are also several general enhancements to the Java transformations:
• For generated Javadoc HTML documentation, <!-- begin-user-doc --> and <!-- end-user-doc --> sections have been replaced with <!-- begin-UML-doc --> and <!-- end-UML-doc -->. These sections are now associated with the model. If the Javadoc documentation is generated from the model by the UML-to-Java transformation, the contents between these sections reflect the UML documentation for the element in the model. Also, when the Java-to-UML transformation runs, then UML documentation is updated to reflect the content between these tags. This behavior is different from previous releases. Prior to version 7.0.5, all content between the <!-- begin-user-doc --> and <!-- end-user-doc --> sections were protected and were not updated when you ran the UML-to-Java transformation. Now that the <!-- begin-UML-doc --> and <!-- end-UML-doc --> sections are linked to model documentation, this section is always updated. If documentation exists inside the <!-- begin-user-doc --> and <!-- end-user-doc --> sections that must be preserved, you can migrate it into the model by running the Java-to-UML transformation before running the UML-to-Java transformation.
• Switching code generation from J2SE 1.4 to J2SE 5.0 and generating UML enumerations using the UML-to-Java transformation correctly converts J2SE 1.4 interfaces to J2SE 5.0 enumerations. When you run the Java-to-UML transformation, a J2SE 1.4 interface that was generated from a UML enumeration is generated back into the model as an enumeration.
• Java qualifiers that do not map to UML properties can be modeled as UML keywords. For example, if the Java-to-UML transformation is run on a Java field that has the volatile qualifier, this information is preserved by adding the keyword "volatile" to the generated UML attribute.
• Several filters, which you can access during model merging, were added or improved for Java-to-UML transformations:
• Filter Parameter Documentation Changes
• Filter Trivial Lower and Upper Bound Changes
• Filter Attribute and Operation Order Changes
• Java code modeling

The Visualize pop-up menu is now available in the Java source editor, which you can use to visualize Java elements in class diagrams directly from the source editor.

Show Related Elements support is available on binary Java types only for the purposes of Inheritance Hierarchy. When you select the Extends (Generalization) relationships in the Show Related Elements dialog box and select Expand indefinitely, the requested inheritance hierarchy is returned for both source and binary Java elements.

A selection of predefined queries are available for Java modeling that you can use to quickly browse through existing Java projects. These queries include Inheritance Hierarchy, Implementors, Associations (incoming and outgoing), Usage (outgoing), and Contained elements.

When you visualize binary Java types in a class diagram, the attribute and operation compartments of the visualized element are collapsed by default. You can view the fields and methods for the binary Java types by clicking the arrows in the respective compartments.

Java elements appear in the Select Existing Element dialog box much faster, so you do not have to wait for all results to be returned before making a selection.

Back to top


---


C# transformations

Re-apply functionality in C# transformations was enhanced to include the use of trace relationships to match renamed or relocated elements in code or models in situations where a UML-to-C# transformation is configured to generate source-to-target relationships. In the absence of source-to-target relationships, the fully qualified names of the elements are used to match existing code elements with model elements, which means that code elements are not properly matched to their UML counterparts subsequent to renaming either a code or UML element.

Back to top


---


CDT 4.0 - C++ Integrated Development Environment

Several enhancements were made to the C/C++ Development Tools (CDT) that make CDT 4.0 a first-class C++ Integrated Development Environment (IDE).
CDT 4.0 is required when you perform C++ code modeling.

Back to top


---


Team integrations
• Rational RequisitePro integration for WebSphere business models

This feature enhances the integration of Rational RequisitePro to provide navigation to requirements across modeling disciplines. Requirements created in Rational RequisitePro and realized by processes and other elements in IBM WebSphere® business models are also visible when the business model is opened in one of the Rational UML modeling products. IT architects are better prepared to create an SOA solution that meets business needs while addressing IT concerns because they can view all the relevant requirements and processes as business service contracts.

Back to top


---


Extensibility and pattern-based engineering
• UML profiles

You can visualize the structure of the profiles in your projects and compose new profile definitions diagrammatically by adding class diagrams to them. The Palette now includes a Profile drawer that provides easy access to the following elements: Stereotype, Metaclass, Class, Enumeration, Extension, Directed Association and Generalization. When you create a class diagram for a selected profile, it is displayed in the profile's Diagram folder in the Project Explorer view, as well as on the Diagrams page of the Profile Editor view.

You can automatically generate an Eclipse plug-in for custom tools from a UML profile. If you create or modify a profile, you can use the new Profile Tooling wizard to add profile elements to pop-up menus and the Palette. The generated Java code defines the element types, Palette entries, menus, and shapes. Models are generated, along with the code, to allow further customization and regeneration. You can also use this feature to deploy a profile in a plug-in.

• Model-to-model transformation authoring
• Mapping model enhancements

You can use a new mapping type, called Inherited Maps, to specify that one mapping declaration inherits from another. The transform generated from an extending mapping declaration extends the transform generated from the inherited mapping declaration. All the individual mappings from the inherited mapping declaration are effectively part of the inheriting mapping declaration. You can override individual mappings and define additional mappings.

You can define mapping declarations with abstract outputs and use them in submap mappings where the output is a by-reference feature. When the transformation runs, the objects to reference are located by searching for objects created by mapping declarations that extend the abstract one.
Many-to-1 and 1-to-many mappings are now supported. When the transformation runs, a generated transform rule can extract an object from a list and insert it into a singleton value feature, or append an object from a singleton valued feature to a list.

• Mapping editor usability improvements

Method signatures for in-line code bodies, as they appear in the generated transformation source code, are displayed in the mapping editor. The editor also supports a specialized invocation of the New Java Class wizard for creating external code bodies.

You can address changes to the location or contents of input and output models by using the mapping editor. Using the mapping editor, you can add or remove models, or change their locations (URI). If a mapped element's definition is changed (for example, it was renamed or moved to a different model) you can recover parts of the existing mapping declaration that are still applicable.

• Transformation authoring runtime

Additional public methods in the transformation runtime simplify the task of customizing generated transformation source code.

A new transform rule was added to the runtime framework. An author can add an instance of the rule to a transformation's post processing rules, which enables the transformation to call another transformation and to use its generated output model as input to the other transformation.
• Model-to-text transformation authoring

You can create model-to-text transformations by using the Java™ Emitter Templates (JET) tool, and then use the transformations to automate the application of design patterns.

The JET model-to-text transformation authoring environment now includes a first-class, JET-aware editor with the following features:
• Color syntax highlighting
• Synchronization of the Outline view
• Editor "folding" around JET tags
• Content assistance for inserting JET tags
• Model-operative pattern features
• Pattern features support integration with some UML profile concepts

When you create a new pattern library, you can choose to associate the library with one or more UML profiles. After the initial association is made to profiles, patterns in that library can draw from the UML stereotypes in those profiles when you assign pattern parameter types. When you apply the pattern, the pattern ensures that only model elements with the appropriate stereotype applied are can bind to those parameters. If you use the default value action bar actions to create default arguments for these parameters, all suitable concrete metatypes are available for creation. If a default value of a pattern parameter with a stereotype is bound to a valid model element, but the owning profile is not yet applied to the model where the pattern instance is persisted, the profile is applied automatically.

• Enhancements to the pattern authoring user interface

After you create pattern libraries, patterns, and pattern parameters, the source code editor enables you to immediately access the code that is generated. The pattern authoring view is sensitive to double-click actions on several elements, such as pattern libraries, patterns, and pattern parameters, which brings the associated source code into focus. The patterns tree in the pattern authoring view now includes parameter type and multiplicity indicators that you can configure through preferences.

• New extensible pattern framework

The pattern framework is no longer hard-coded and assumed to be the only pattern framework that the pattern library implementations extend. The pattern framework that was included in previous versions was renamed "generalized pattern framework." A new product plug-in includes the base pattern framework concepts and pattern framework modularity extension point definitions. Advanced users can create proprietary pattern frameworks that extend from the generalized pattern framework that comes with the product. Using the pattern preferences, you can specify the default pattern framework to use when you create new pattern libraries.

A new pattern framework, called "specialized pattern framework" extends from the "generalized pattern framework" and offers two new pattern parameter-related features to patterns that choose to extend from it when pattern libraries are created. Model elements that bind to pattern parameters now receive a named keyword that is derived from the pattern parameter name. The design pattern content is now made available to user-defined patterns. Only model elements in the same model as the persisted pattern instance are marked up with the keyword to circumvent read-only model issues. Model elements involved as pattern participants become the target of a created UML trace abstraction relationship that originates from the pattern instance. These abstraction relationships are directed in the opposite direction of the design pattern content implementation to minimize modifications to non-local writable models.
• Public API for managing model fragments

Using available public application programming interfaces (APIs), you can now extend the model fragment functionality to suit your purposes.

• Frameworks for model analysis, queries, and modeling reminders
• Model analysis framework

The model analysis framework is based on the static analysis framework in Test and Performance Tools Platform (TPTP) and is implemented at the Eclipse Modeling Framework (EMF) level. The traceability analysis rules were improved to use the same infrastructure as the query framework. These rules now use the identical logic and internal API extensibility.

The traceability analysis rules were moved to the new model analysis rule provider, and the following new model analysis rules were added:
• Element is missing a specification (element has no higher level of abstraction)
• Element is missing an implementation (element has no lower level of abstraction)
• Element is involved in a trace relationship cycle (element has another element that is both a higher and a lower level of abstraction)
• Modeling reminders

The Modeler validation capabilities were extended to support reminders for some of the validation rules. Reminders are hints that help guide you as you work on models and are displayed in the Tasks view. For example, a reminder might inform you that there is an actor in your model that should be associated with at least one use case.

Unlike batch validation, reminders run in real time and, therefore, are updated as you create new issues or resolve existing ones in your models.
• New extensibility capabilities for Eclipse 3.3
• Query framework

The query framework is an extensible framework that provides capabilities to add new queries to the Palette. The traceability and Java modeling features use this framework to contribute queries to the diagram Palette.

• Reminders framework

Built on the Eclipse Modeling Framework Technologies (EMFT) validation framework and model indexing, the reminder service enhances the existing live and batch validation functionality by providing you with interactive validation as you work on your models. You can create reminder rules that are validated against objects upon the notification of specified events. If a reminder rule becomes invalid, a message is added to the Task view that informs you of this change and you must address the problem before the message can be removed from the view. You can customize the view to ignore specific validation rules and to filter results.

Validation results are displayed in the Tasks view as a list of reminders, which are hints to guide you as you work on your model. For example, you might have an actor in a model that should be associated with at least one use case. Reminders are always live, which keeps you informed about any items that are missing from your models, such as best practices or incomplete models. Unlike live validation rules, where you have to implement notification handling code, this framework provides a simple XML-based registration of target-based validation rules.

The Reminder Service also improves the existing live and batch validation support for models by removing problem markers after the validation warning or error is resolved.

Back to top


---


User assistance
There are similar behavior changes to the online help and tutorial and sample galleries. These behavior changes impact all platforms, including Windows, Linux, and Solaris that use either embedded or external browsers.
• Online help and tutorial and sample galleries use the same browser window

With a tutorial or a sample already open, when you open another tutorial or sample from the Tutorial or Sample Gallery by using the Help > Tutorial Gallery or Help > Sample Gallery menu, the tutorial or sample opens in the same window. In earlier versions of the galleries, a new window would open for each repository, including Help, Tutorial Gallery, or Sample Gallery. Now there will be only one window. If you open Help, the Help topic opens in the same window too. This happens whether the browser is embedded (on Windows or Solaris) or external (on Solaris).
• Dynamic Assistance, or Dynamic Help, gallery opens in new windows

Opening search results from the dynamic help view (Help > Dynamic Help) used to display the content in the same window or view that displayed the search results. This is called opening in place as opposed to a new window. It now opens the results in a new window that opens in the edit region of the Eclipse perspective. If the IDE is setup to use an external browser on Solaris, the results display in an external browser window.


Back to top


---



Fixed APARs contained in this release

The following table lists the APARs fixed in this release:


Component	APAR number	Description
C++ modeling and transformation	PK40895	Incorrect display of "Confirm Implicit Deletion" message.
C++ modeling and transformation	PK40995	"Transformation Aborted" error when transforming classes in a class diagram.
C++ modeling and transformation	PK42275	Declaration of nested typedefs generate compiler error in UML to C++ transformation.
C++ modeling and transformation	PK42857	Dependency generates a #include and also a forward declaration.
C++ modeling and transformation	PK45016	String type attributes are always transformed into C++ as constants.
C++ modeling and transformation	PK51033	Source code changes are not reflected in transformed files.
C++ modeling and transformation	PK55283	C++ pointer is lost when transforming C++ code to UML.
C++ modeling and transformation	PK55872	Transformation between UML and C++ does not preserve system header file declarations in .cpp and .h files.
Compare and merge	PK49605	Compare and merge appears on another user screen as it takes first running instance of Eclipse.
Documentation	PK37168	Wind River Workbench integration documentation is not available.
Documentation	PK41206	PiggyBank Basic Flow sequence Diagram is incorrect.
Documentation	PK42927	Section 2.2 in the readme file provides no link to the Installation Guide.
Documentation	PK52260/PK55943	Amabiguous and unactionable error message during visualization.
DoDAF modeling	PK49163	DoDAF feature is not enabled when importing a DoDAF Project.
Java modeling and transformation	PK41008	"Generate JavaDoc with Diagrams from Existing Tags" gives ClassNotFoundException.
Java modeling and transformation	PK45209	Cannot create final type parameter in Java method after transformation from UML model.
Java modeling and transformation	PK45312	Reverse tranformation immediately after forward transformation results in attribute duplicated in model.
Java modeling and transformation	PK46009	Java-to-UML transformation fails with NPE when using generic collection fields with template parameters.
Java modeling and transformation	PK50976	Remove the @uml.annotations tag generated with the UML-to -Java 5.0 transformation, since it’s not used anyway.
Java modeling and transformation	PK52753	Filters > Show Related Elements does not show incoming references when using a collection.
Modeling framework	PK21718	< operation is required in OCL sortedBy().
Modeling framework	PK38275	GDI+ error occurs when using partition in an activity diagram.
Modeling framework	PK40177	Aarranging all elements in component diagrams creates invalid diagrams.
Modeling framework	PK40272	No promt when deleting a state.
Modeling framework	PK41625	No confirmation of deletion despite Window > Preferences setting.
Patterns	PK39079	No confirmation of deletion despite Window > Preferences setting.
Rational Rose model import	PK21725	Object node is not displayed as it is in Rose as an actor shape.
Rational XDE model import	PK27960	Imported XDE diagrams loses structure/orthogonality.
Rational XDE model import	PK39969	Web report: Sequence diagram only shown when clicking All Elements.
Rational XDE model import	PK55467	XDE diagram model definition desciption is imported as a Note in the diagram, not as a property.
UML model reporting	PK02093	Need to provide a more graceful way to handle the errors during the publishing operation.
UML model reporting	PK23512	Publish Report with "Always clean destination folder without asking" does not clean destination folder.
UML model reporting	PK28007	Problem with references to external files.
UML model reporting	PK45311	Usecases under classes documentation is not generated during Web Publish.
UML model reporting	PK47062	The application crashes when web publishing a large model with JPEG image file format.
UML model reporting	PK49140	Not possible to browse diagram elements after Web publishing with SVG image file format.
UML model reporting	PK52550	Web publish by using the JPEG format does not show the diagram image.
UML modeler	PK16646	When selecting all classes in a class diagram, the association class is not selected.
UML modeler	PK24599	OCL autocomplete does not detect all possible roles.
UML modeler	PK32355	Need to make lifeline head resizable.
UML modeler	PK37222	Replace History is not persisted between Find/Replace actions.
UML modeler	PK37411	"Show compartment titles" also shows Source/Target Role Constraints tags.
UML modeler	PK39705	Undo menu is disabled after a diagram deletion.
UML modeler	PK40183	It is possible to create an instance of an abstract class in an object diagram.
UML modeler	PK40502	The application hangs when running sample pluglet on elements with large tree structure.
UML modeler	PK41016	Cannot change the source of a control flow association that resides on a partition by dnd its source end to another element.
UML modeler	PK42828	Association between class and association class appears as two separate associations.
UML modeler	PK42831	Constraint in a diagram sometimes appears unattached to diagram element after moving.
UML modeler	PK43906	Search and Replace fails with flow guard values.
UML modeler	PK44228	In object diagrams, direction of association is created from "Select existing element".
UML modeler	PK44875	Opening activity diagrams in the model and elements have moved form there original positions.
UML modeler	PK45633	Lifeline name does not copy across when DnD existing class/actor to other sequence diagram.
UML modeler	PK46333	Finding reference models stays at 0%.
UML modeler	PK47235	Geometric shapes in sequence diagrams cannot be moved to the front or back.
UML modeler	PK47278	No slash adornment appears for derived an association in diagrams.
UML modeler	PK47407	Find/Replace does not pick up URLs in subfragments.
UML modeler	PK47499	Cannot open fragment by double-clicking or Open pop-up menu.
UML modeler	PK47583	Searching model with Including Simple Text Matches on a search term that exists in the model causes an NPE.
UML modeler	PK48074	Refresh problem applying custom stereotype with shape image.
UML modeler	PK48569	Need to provide ability to sort search view after model search.
UML modeler	PK48600	Need to add a preference specifying whether or not to check the validity of a path in a URL.
UML modeler	PK49050	Moving the seperation line of an alternate combined fragment does not correctly move the corresponding messages.
UML modeler	PK49167	Performing a Modeling Search with only URLs selected produces additional results other than just URLs.
UML modeler	PK50433	Documentation is lost when changing the name of an operation (method).
UML modeler	PK54981	Find/Replace does not locate strings in the documentation of elements that are in fragments.
UML modeler	PK56978	In activity diagrams, adding a control node results in misleading appearance when done inside an activity partition.
UML modeler	PK57024	NullPointerError when drawing control node from stereotyped with shape image decision node.
UML modeling	PK40094	AssociationInstance is not deleted when linked instance is deleted.
UML modeling	PK41422	Difficult to reposition an association class to a desired location on the drawing surface after resizing.
UML modeling and visualization	PK45315	Important steps and information is missing in the Help Doc "Adding Palette Tools to Create Stereotyped Elements".
UML modeling and visualization	PK47581	Searching a File URL contained in a model with a search term ending in \produces no results although the term exists.