Tool Mentor: Incorporating
Existing Design Elements Using Rational XDE Developer - .NET Edition
Purpose
This section provides links to additional information related to this tool mentor.
The steps in this tool mentor match those in the activity. Links to topics in XDE online help are marked with 
.
Overview
The following steps are performed in this tool mentor:
- Identify Reuse Opportunities
- Reverse-Engineer Components and Databases
- Update the Organization of the Design Model
- Update the Logical View
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 in XDE online Help.
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 in XDE online Help.
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 in XDE online Help. 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.
