Tool Mentor: Designing Classes Using Rational XDE Developer - Java Platform Edition

Purpose

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

• Class Design

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

Overview

This tool mentor assumes that a structured Design Model has been created as part of Activity: Architectural Analysis following the steps outlined in Tool Mentor: Performing Architectural Analysis Using Rational XDE.

The following steps are performed in this tool mentor:

• Use Design Patterns and Mechanisms
• Create Initial Design Classes
• Identify Persistent Classes
• Define Class Visibility
• Define Operations
• Define Methods
• Define States
• Define Attributes
• Define Dependencies
• Define Associations
• Define Generalizations
• Resolve Use-Case Collisions
• Handle Nonfunctional Requirements in General
• Evaluate the Results

Use Design Patterns and Mechanisms

Incorporating a pattern and/or mechanism is effectively performing many of the subsequent steps in this tool mentor (adding new classes, operations, attributes, and relationships), but in accordance with the rules defined by the pattern or mechanism.

For information on using patterns, refer to:

Create Initial Design Classes

1. Add a class diagram to the model. See .
2. Add design classes to the class diagram. See .
3. Document each class. See .

For more information, refer to .

Identify Persistent Classes

A class can be marked as persistent. Refer to .

In J2EE development, persistency is commonly implemented using entity EJBs. See Tool Mentor: Identifying Design Elements using Rational XDE for details.

Define Class Visibility

For each class, determine the class visibility within the package where it resides.

Refer to .

Define Operations

1. Add operations to each class. See .
2. Add parameters to operations. See .
3. Specify visibility of operations. See .

For more information, refer to .

Define Methods

A description of how an operation is to be implemented might be added to the operation description.

A sequence diagram might optionally be used to describe a method. See the XDE online Help topic .

For more information, refer to .

Define States

A state machine might optionally be used.

For more information, refer to .

Define Attributes

1. Define attributes. See .
2. Add attributes to classifiers. See .
3. Specify visibility. See .

Define Dependencies

Refer to .

Define Associations

1. Add association relationships. See .
2. Specify the kind of each association. See .

Define Generalizations

Refer to .

Resolve Use-Case Collisions

Refer to .

Handle Nonfunctional Requirements in General

Nonfunctional requirements often drive a class to incorporate specific design mechanisms using collaborations and patterns. Often the use of a framework component is sufficient to satisfy a nonfunctional requirement. (See Tool Mentor: Identifying Design Elements Using Rational XDE.)

For more information, refer to:

Evaluate the Results

There is no Rational XDE specific guidance for this step.

Rational Unified Process