Overview

This tool mentor supports performing Class Design with Rational XDE Developer - Java Platform Edition.

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

• The steps in this tool mentor match those in the corresponding task.
• Links to topics in XDE online Help are marked with .
• 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.

Additional information on using patterns:

• Applying Patterns

Create Initial Design Classes

1. Add a class diagram to the model. See Adding Diagrams .
2. Add design classes to the class diagram. See Adding Shapes to Diagrams .
3. Document each class. See Documenting Model Elements .

Reference: Working with Class Diagrams .

Identify Persistent Classes

A class can be marked as persistent. Reference: Specifying Persistence .

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.

Reference: Specifying Visibility .

Define Operations

1. Add operations to each class. See Adding Operations to Classifiers .
2. Add parameters to operations. See Adding Parameters to Operations .
3. Specify visibility of operations. See Specifying Visibility .

Reference: Adding and Modifying Attributes and Operations in Classifiers .

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 Documenting Model Elements .

Reference: Working with Interaction (Sequence) Diagrams .

Define States

A state machine might optionally be used.

Reference: Working with Statechart Diagrams .

Define Attributes

1. Define attributes. See Attributes .
2. Add attributes to classifiers. See Adding Attributes to Classifiers .
3. Specify visibility. See Specifying Visibility .

Define Dependencies

Reference: Adding Dependency Relationships .

Define Associations

1. Add association relationships. See Adding Association Relationships .
2. Specify the kind of each association. See Specifying Kinds of Association Relationships .

Define Generalizations

Reference: Adding Generalization Relationships .

Resolve Use-Case Collisions

Reference: Specifying the Type of Concurrency for Operations .

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

Reference:

• J2EE Pattern-Driven Development
• Applying Patterns

Evaluate the Results

There is no Rational XDE specific guidance for this step.