Purpose

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


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

Overview

The following steps are performed in this tool mentor:

Additional Tool Information

Distribute Subsystem Behavior to Subsystem Elements To top of page

Classes and other subsystems are added within the subsystem to realize the subsystem interfaces.

The collaborations of model elements within the subsystem must be documented using sequence diagrams that show how the subsystem behavior is realized. Each operation on an interface that is realized by the subsystem must have one or more documented sequence diagrams. This diagram, which is owned by the subsystem, is used to design the internal behavior of the subsystem.

  1. Create class diagrams as needed. See Creating and Modifying Class Diagrams .
  2. Add subsystems and classes. See Tool Mentor: Identifying Design Elements Using Rational Software Architect for guidance on adding new subsystems and classes.
  3. Document how each interface operation is realized, as follows:
    • Add a collaboration instance for each interface operation. Name it after the operation. In the Model Explorer, right-click the subsystem and then click New UML > Collaboration.
    • Create an interaction with the same name. In the Model Explorer, right-click the collaboration and then click New UML > Interaction.
    • Create a sequence diagram for this interaction. See Sequence Diagrams .
    • Drag and drop classes and interfaces onto the diagram to create objects for interaction. See Adding Shapes .
    • Add messages or stimuli between objects. See Sequence Diagrams.
    • Assign operations to messages. See Sequence Diagrams.

For more information, refer to the following topics in the RSA online Help:

  • Modeling Static Structure with Class Diagrams
  • Sequence Diagrams

Document Subsystem Elements To top of page

Refer to Documenting Model Elements in the RSA online Help.

Describe Subsystem Dependencies To top of page

When an element contained in a subsystem uses some behavior of an element contained in another subsystem, a dependency is created between the enclosing subsystems. To improve reuse and reduce maintenance dependencies, express this situation in terms of a dependency on a particular interface of the subsystem, not upon the subsystem itself nor upon the element contained in the subsystem.

Refer to Dependency Relationships in the RSA online Help.

Additional Tool InformationTo top of page

Tours:

  • Patterns

Tutorials:

  • Creating a Diagram with RSA
  • Analysis: Create the Sequence Diagram

Samples:

  • Annoted Sequence Diagram

Rational Unified Process   2003.06.15