Tool Mentor: Incorporating Existing Design Elements Using Rational XDE Developer
This tool mentor describes how to perform Incorporating Existing Design Elements with Rational XDE Developer.
Tool: Rational XDE Developer
Relationships
Main Description

Overview 

This tool mentor supports Incorporating Existing Design Elements with Rational XDE Developer - Java Platform Edition.

Identify Reuse Opportunities

Look for existing subsystems or components that offer similar interfaces. Some assets may have been packaged for intentional reuse using the Reusable Asset Specification (RAS). If created with Rational XDE, such assets can be browsed and loaded in XDE. See helpbook icon Getting Started with RAS Assets .

Reverse-Engineer Components and Databases

For assets that do not include an XDE model, it may be useful to reverse engineer a model to better understand the design. If the asset proves to be usable, the XDE model then becomes part of your overall Design Model. See helpbook icon Reverse Engineering .

For an asset that your company controls, there may be opportunities to make minor changes to a candidate interface which will improve its conformance to the desired interface. For assets that your company does not control, you can create adapter or bridge design elements that map your desired interface onto interfaces provided by the assets reused. See Tool Mentor: Identify Design Elements for guidelines on creating and modifying interfaces and classes.

Update the Organization of the Design Model

Reorganize the design elements into packages as necessary. See helpbook icon Grouping Model Elements in Packages . Also see the white paper Rational XDE Model Structure Guidelines.

Update the Logical View

If there is a separate logical view, it needs to be maintained. See the white paper Rational XDE Model Structure Guidelines.