Tool Mentor: Identifying Design Mechanisms Using Rational XDE Developer - .NET Edition

Purpose

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

• Identify Design Mechanisms

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

Overview

The following steps are performed in this tool mentor:

• [Categorize Clients of Analysis Mechanisms](#categorize clients)
• [Identify Design Mechanisms for the User-Experience Mechanisms](#Identify Design Mechanisms for the User-Experience Mechanisms)
• [Inventory the Implementation Mechanisms](#inventory impl mechanisms)
• [Map Design Mechanisms to Implementation Mechanisms](#Map Design Mechanisms to Implementation Mechanisms)
• [Document Architectural Mechanisms](#document mechanisms)

Categorize Clients of Analysis Mechanisms

There is no Rational XDE specific guidance for this step.

Identify Design Mechanisms for the User-Experience Mechanisms

There is no Rational XDE specific guidance for this step.

Inventory the Implementation Mechanisms

There is no Rational XDE specific guidance for listing all the available implementation mechanisms.

Map Design Mechanisms to Implementation Mechanisms

There is no Rational XDE specific guidance for this step.

Document Architectural Mechanisms

Mechanisms themselves are Design Model elements (such as Design Package, Design Class, and Design Subsystem) that can be represented in Artifact: Design Model as part of their respective design activities. See Tool Mentor: Identify Design Elements for guidelines on creating Design Model elements. Note that a Rational XDE pattern is particularly well suited to documenting a design and implementation mechanism, because it allows clients of the mechanism to expand the pattern and to generate much of the required design and code.