Download Release
April 23, 2019

Design Management

Analysis Design change management Lifecycle traceability

Design Management 4.0.2

Product Release / Trial | March 15, 2013
This is not the most recent version. We recommend Design Management . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

The downloads for this milestone are no longer available.

Rational Design Management 4.0.2 "New and Noteworthy"

Design Management 4.0.2 New & Noteworthy

The Design Management installer enables you to install the Jazz Team Server and several applications and client tools. For new and noteworthy information about parts of the Rational solution for Collaborative Lifecycle Management (CLM), see these pages:

New in Design Management 4.0.2

Design Management Server

Setup and configuration

Design reviews

Configuration Application


IBM Rational Software Architect Extension for Design Management

IBM Rational Rhapsody Extension for Design Management

Design Management Server

When you create Open Services for Lifecycle Collaboration (OSLC) links from a Design Management resource, some of the Jazz applications allow you to select multiple resources. If you select multiple resources, the resource names are displayed in the link creation window. When you click OK, multiple links are created with the same link type and description. Then, when you edit an existing link and change the target resource, only the first resource returned by the Jazz application is used when multiple resources are selected.

Multiple-document loading and saving

When you work with a model resource in a form, you can now edit external documents that are referenced by that resource. The Edit action is now enabled for resource references in collections, as well as for single value references, whenever the reference points to an external document or to the current document. When you select Edit, a window opens in which you can edit the resource unless the resource comes from a read-only configuration. In the window, you can also edit resources that are referenced by the resource and save your changes. When you add new references in collections or single value properties, you can create a new resource if the context permits it.

Diagram shape rich-hover window

To be consistent with the Explorer view and Form view for resources, when you hover over a diagram shape, the rich-hover window opens. This window enables an OSLC provider to display content that is hosted in the diagram context. From the rich-hover window, you can also navigate directly to the editor for the resource.

Searching for a particular resource in a form editor was simplified. The Quick Search function and its capabilities were incorporated into the regular Search tab; however, the Search tab uses the model constraints that the Quick Search function used. In addition, you can choose to search in the current project area or in the project area and all its dependent configurations. When you search for values to add in a collection, you can now select multiple entries in the Search window as opposed to selecting a single item and having to specify the search terms again.

Rich text improvements

You can now link comments to paragraphs in rich-text documents. This functionality makes it easier for reviewers to comment on specific parts of a rich-text document. The new read-only mode also makes the document more consumable for mobile touch-based devices. You can use the swipe action to scroll through the document in this mode. If you lock the document by using the lock icon, an editor can put the document into edit mode and incorporate changes based on comments.

Inserting image and diagram links into rich-text documents is now simpler because the Search window was enhanced. When you insert an image, you can find all the images and select which one to insert. The pinboard is now also available if you previously identified the link or image from another editor.

Setup and configuration

Project creation simplified

In previous releases of Design Management, the process for creating a new project, creating the configuration space, and assigning domains was complex. This process was simplified and you can now specify the relevant information on the Design Management project creation page.

Rename DM context root (/dm)

During the installation of Design Management 4.0.2, you can change the default context root from "dm" to something else. This value affects the root public URLs for Design Management. For example, if you change the root context to "abc", the root URL is displayed as https://fully_qualified_host_name:9443/abc.

Multiple Design Management instances sharing one Jazz Team Server

To address scalability issues, you can register multiple Design Management instances with the same Jazz Team Server. Typically, the instances of Design Management are installed on separate application servers, such as Apache Tomcat or WebSphere Application Server, which run on different server computers. However, to register two instances of Design Management with the same Jazz Team Server, one of the instances must have its context root (/dm) renamed. You can rename the context root when you install Design Management. In 4.0.2, when Design Management is installed, it automatically installs the Configuration Application (/vvc); therefore, both instances of Design Management have an instance of the Configuration Application installed, but only one instance of the Configuration Application can be registered with Jazz Team Server.

When the second instance of Design Management is installed, you can remove the Configuration Application files before you start its application server so that the second instance of the Configuration Application is not running. The resources to remove are as follows: the vvc.war and vvchelp.war files (either in the server/webapps diretory or in the server/tomcat/webapps directory), the server/conf/vvc configuration directory, and the server/upgrade/vvc directory.

Upgrade script automatically copies TRS change logs

The Design Management upgrade script was modified to automatically copy the Tracked Resource Set (TRS) change log hierarchy (server/dm/tdb directory). The manual upgrade step to copy the hierarchy is no longer needed, but if it is performed, the script does not copy the hierarchy again.

Design reviews

New approver role for reviews

In reviews, a new Approver participant role was added. An approver can either approve or reject changes on the resources that are associated with the review.

Multiple resource selection for reviews

When resources are being added to a review, the resource selection window has two options: the search selector and the pinboard. Both resource selectors allow you to select multiple resources to add to the review. In addition, the paging in the search picker was increased from 5 to 100 resources per page.

Configuration Application

New creation wizards

The usability workflow was improved for Design Management users to create workspaces and snapshots. A wizard now guides you through any required steps in the process for creating project areas without requiring you to leave Design Management.

Linking change sets and change requests

You can now associate Design Management change sets with change requests from Change and Configuration Management providers such as Rational Team Concert.

After your Design Management project area has a project association to a Change and Configuration Management project area, when you work in a change set, you can use the new Link to Change Request command on the Configuration Context menu to start associating change requests with the current change set. When you hover over the change set context on the Configuration Context menu, the associated change sets are displayed. When you use the Explore Change Sets command, you can view the associated change requests with all change sets in the current workspace. When you select the change set in the Change Set Explorer view, you can now open a change set editor to provide information about the current state of the change set, which resources are included, as well as provide a way to view, create, and remove associated change requests.

Force an unlock of a resource

When a user has locked a resource, either accidentally or explicitly, and then is not available, other users are prevented from modifying that resource. In 4.0.2, the project administrator or another user with the appropriate permission can unlock the resource. If the resource was locked but not modified, it is unlocked. However, if the resource was locked and modified, it can only be unlocked by deleting the corresponding change set. The user who unlocks the resource must explicitly delete the change set to unlock it. A new option was added in the project area editor; to make this change, go to Design Management > Editing Management > Force the unlock of a design resource.

Automatic documentation generation for ontologies

When you create ontologies for custom domains, it can difficult to understand which resources are persisted and how the properties relate to the class concepts. A new Vocabulary tab is available in the Ontology editor. This tab displays the ontology concepts in a formatted set of tables that you can use to review and understand how instances of the ontology concepts are represented. The description fields from the ontology concepts are displayed in a documentation section of the tables to clearly identify the purpose of the class or property in the vocabulary. In addition, all the references within the tables are linked so that you can open a separate ontology or individual class in the table documented view. If the ontology instances are going to be published through OSLC, you can use the OSLC sub-tab view to test if the published view is consistent with the expected set of properties and concepts that are exposed.

Ontology to Ecore exporter

If you have external tools that rely on an Ecore representation for your model, you can now store your ontologies in Design Management and use an export command that automatically creates an Ecore version of the Design Management ontology. A new menu option is available from the File menu in the Domains project area called Ecore Export. This menu opens a page from which you can select the set of ontologies to export to Ecore format.

IBM Rational Software Architect Extension for Design Management

Move and copy support in the Design Explorer view

In this release of IBM Rational Software Architect Extension for Design Management, you can use the clipboard to drag elements in the Design Explorer view. For example, you might want to move a class from one package to another or create a copy of an operation in another class.

IBM Rational Rhapsody Extension for Design Management

Performance improvements

The amount of time required for the IBM Rational Rhapsody Extension for Design Management to load models has been reduced; diagrams display faster in both the web interface and the extension. For details, see work item 35755.

New options for opening and viewing models

Using the Select view window, there are now new options for opening and viewing models. For details, see work item 37622.

Support for deleting an entire project

You can now delete an imported Rational Rhapsody model on the Design Management Server by using the web UI. For details, see work item 36663.

Support for reviewing shared change sets

You can use the change sets view to review shared change sets from other team members. For details, see work item 37984.

Single sign on

In previous releases, you were prompted to log in to the server each time you selected a different view. In this release, you are only required to log in once. For details, see work item 37984.