Tool Mentor: Structuring the Implementation Model Using Rational XDE Developer - .NET Edition

Purpose

This section provides links to additional information related to this tool mentor.

• Structure the Implementation Model

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

Overview

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 .
3. Create a package for each Implementation Subsystem. (See .) 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 .

Larger granularity subsystems typically become XDE models containing code models and source code.

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

For more information, refer to .

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 .) 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.

Imports from outside the project are referred to as Reference Models. See .

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 .
3. Add each of the executables and other deployable files (modeled as UML components). See .
4. Organize into packages (as described in Rational XDE Model Structure Guidelines). See .

Note that there is no round-trip engineering support for executables, 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

It can be helpful to publish models to html format. Also note that diagrams can be copied from Rational XDE to Microsoft Word and other programs.

For more information, refer to .

Rational Unified Process