Overview

The steps in this tool mentor match those in the task. References to topics in Rational XDE™ online Help are marked with .

This tool mentor assumes that you have defined the top level structure of your Implementation Model as described in the Rational XDE Model Structure Guidelines. The steps in this tool mentor permit this initial structure to be refined.

The following steps are performed in this tool mentor:

• Establish the Implementation Model Structure
• Adjust Implementation Subsystems
• Define Imports for Each Implementation Subsystem
• Decide How to Treat Executables (and Other Derived Objects)
• Decide How to Treat Test Assets
• Update the Implementation View
• Evaluate the Implementation Model

Establish the Implementation Model Structure

As Implementation Subsystems are identified, they can be modeled as packages on component diagrams to show dependencies between the subsystems. These diagrams define the Implementation View. To create this, follow these steps:

1. Navigate to the model and package that will contain the Implementation Subsystems. (In the recommended Rational XDE Model Structure Guidelines, this is the Integration Support Model.)
2. Create a component diagram providing an overview of the Implementation Subsystems. See Adding Diagrams.
3. Create a package for each Implementation Subsystem. (See Adding Shapes to Diagrams.)   Note that there is no specific support in Rational XDE for Implementation Subsystems, so this diagram is just a picture.
4. (optional) If the relationship of these Implementation Subsystems to projects and/or elements in the various code models is not obvious, then a Traceabilty to Design Elements diagram can be created. See Adding Diagrams.

Each project's code model must be structured in accordance with the Rational XDE Model Structure Guidelines. See Grouping Model Elements in Packages.    Alternatively, create directories in the file system and packages in code, and synchronize to create the corresponding packages in the model.

Adjust Implementation Subsystems

There is no Rational XDE specific guidance for this step.

Define Imports for Each Implementation Subsystem

Capture import dependencies on the Implementation View component diagram created previously. See  Adding Dependency Relationships.   Note that these dependencies only provide guidance to developers. There is no enforcement or checking performed by Rational XDE.

Project imports should match these dependencies.

To define or modify imports of JARs from outside the project, click Window on the toolbar, click Preferences, and then click Java, Organize Imports.

Decide How to Treat Executables (and Other Derived Objects)

Executables and other deployable files can be modeled as UML components. See the Deployment Support Model in the Rational XDE Model Structure Guidelines. If you decide to model these files, the following steps apply:

1. Navigate to the model and package which will contain these files. (In the recommended Rational XDE Model Structure Guidelines, this is the Deployment Support Model.)
2. Create a component diagram. See  Adding Diagrams.
3. Add each of the executable programs and other deployable files (modeled as UML components).  See Adding Shapes to Diagrams.
4. Organize into packages (as described in Rational XDE Model Structure Guidelines). See Grouping Model Elements in Packages.

Note that there is no round-trip engineering support for executable programs, so this model must be maintained by hand.

Decide How to Treat Test Assets

There is no Rational XDE specific guidance for this step.

Update the Implementation View

If there is a separate Logical View, it must be maintained. See Rational XDE Model Structure Guidelines.

Evaluate the Implementation Model

There is no Rational XDE specific guidance for this step.