Name 

Description 

Annotating a Diagram 

 

Creating a Diagram 

When you create a new diagram, the Diagram View presents an empty background. You place the various model elements on the background and draw relationship links between them according to the requirements of your model. 

Exporting a Diagram to an Image 

 

Printing a Diagram 

You can print diagrams separately or as a group, or print all diagrams in the project. 

Changing Diagram Notation 

 

Using Grid and Other Appearance Options 

You can optionally display or hide a design grid on the diagram background and have elements “snap” to the nearest grid coordinate when you place or move them. The grid is configured in the Diagram Appearance options dialog window. 

Using the UML in Color Profile 

 

Aligning Model Elements 

You can automatically rearrange all or selected model elements on a diagram. 

Changing Type of a Link 

 

Closing a Diagram 

 

Copying and Pasting Model Elements 

The move and copy operations are performed by drag-and-drop, context menu commands, or keyboard shortcut keys.  

Deleting a Diagram 

 

Hyperlinking Diagrams 

Select Hyperlinks from the diagram context menu to create, view, remove, and browse hyperlinks. 

Laying Out a Diagram Automatically 

 

Moving Model Elements 

Create your own layout by selecting and moving single or multiple diagram elements.
You can:

• Select a single element and drag it to a new position.
• Select multiple elements and change their location.
• Manually reroute links.

, the diagram automatically scrolls to follow the dragging.  

Renaming a Diagram 

 

Rerouting a Link 

 

Resizing Model Elements 

Diagram elements can be resized automatically or manually. When new items are added to an element that has never been manually resized, the element automatically grows to enclose the new items. 

Selecting Model Elements 

Most manipulations with diagram elements and links involve dragging the mouse or executing context menu commands on the selected elements. 

Assigning an Element Stereotype 

You can assign a stereotype in the diagram by using the in-place editor, or by using the Object Inspector. 

Using Drag-and-Drop 

Drag-and-drop applies to the members as well as to the node elements. You can move or copy members (methods, fields, properties, and so on) by using drag-and-drop in the Diagram View or in the Model View.
Drag-and-drop functionality from the Model View to the Diagram View and within the Model View works as follows:

• Selecting an element in the Model View and using drag-and-drop to place the element onto the diagram creates a shortcut.
• Using drag-and-drop while pressing the SHIFT key moves the element to the selected container.
• Using drag-and-drop while pressing the CTRL key copies the element to... more 

Working with User Properties 

User properties are created by means of the User Properties command. The User Properties command is available on the context menus of the diagrams and diagram elements both in the Diagram View and the Model View. Once created, the user properties can be viewed and edited in the Object Inspector under the User Properties category. 

Creating a Link with Bending Points 

If your diagram is densely populated, you can draw bent links between the source and target elements to avoid other elements that are in the way. 

Creating Multiple Elements 

You can place several elements of the same type on a diagram without returning to the Tool Palette or by using the diagram context menu. Each element will have a default name that can be edited with the in-place editor or in the Object Inspector. 

Creating a Shortcut 

You can create a shortcut to a model element on the diagram background by using three methods:

• By opening Add Shortcuts dialog box from the Diagram View
• By copying and pasting a shortcut from the Model View
• By choosing Add Shortcuts on the Model View context menu

 

Creating a Simple Link 

In a design project, you can create a link to another node, or a shortcut of an element of the same or another design project (these projects must be of the same UML version).
In an implementation project, you can create a link to another node or a shortcut of an element of the same project. 

Creating a Single Model Element 

 

Searching Diagrams 

Together enables you to use the Find and Replace facilities provided by RAD Studio to locate model elements on model diagrams. 

Searching Source Code for Usages 

In addition to the diagram search facility, Together enables you to track how an element or member is used in a source-code project. The Search for Usages dialog box enables you to find the references to, and overrides of, the elements and members in implementation projects.
The Search for usages command is available on the context menu of an element in a diagram or in the Model View. Note that Search for usages is not available for the design projects. 

Creating an Activity for a State 

 

Designing a UML 1.5 Activity Diagram 

Use the following tips and techniques when you design a UML 1.5 Activity Diagram. 

Instantiating a Classifier 

In a UML 1.5 design project, you can create an object that instantiates a class or interface from the same or another UML 1.5 design project or any implementation project in the same project group. In an implementation project, you can create an object that instantiates a class or interface from the same project or some UML 1.5 design project or a referenced project. You can create such links by using the Object Inspector or by using Dependency links to shortcuts. 

Designing a UML 1.5 Component Diagram 

Following are tips and techniques that you can use when working with UML 1.5 Component Diagrams. It can be convenient to start creation of a model with Component Diagrams if you are modeling a large system. For example, a distributed, client-server software system, with numerous interconnected modules. You use Component Diagrams for modeling a logical structure of your system, while you use Deployment Diagrams for modeling a physical structure. 

Designing a UML 1.5 Deployment Diagram 

Use the following tips and techniques when you design a UML 1.5 Deployment Diagram. It can be convenient to start creation of a model with Deployment Diagrams if you are modeling a large system that is comprised of multiple modules, especially if these modules reside on different computers. You use Deployment Diagrams for modeling a physical structure of your system, while you use Component Diagrams for modeling a logical structure. 

Adding a Conditional Block 

.  

Associating an Object with a Classifier 

In the sequence or collaboration diagram you can create associations between objects (located on an interaction diagram) and classifiers (located on some class diagram). Instantiated classes for an object can be selected from the model, or the classes can be created and added to the model.
Note that an object can instantiate classifiers that belong to the various source-code projects within a single project group, when such projects are referenced from the project in question.
The range of available classifiers depends on the project type.

• Design projects: classes, interfaces
• C# implementation projects: classes, interfaces, structures

 

Branching Message Links 

Branching messages that start from the same location on the lifeline. 

Converting Between UML 1.5 Sequence and Collaboration Diagrams 

You can convert between sequence and collaboration diagrams. However, when you create a new diagram, you must specify that it is either a sequence diagram or a collaboration diagram. 

Working with a UML 1.5 Message 

This section describes techniques for working with messages in Sequence and Collaboration diagrams. Although the two diagram types are equivalent, the techniques for dealing with messages differ.
In a Collaboration diagram, all messages between the two objects are displayed as a generic link line, and a list of messages is created above it. The link line is present as long as there is at least one message between the objects. Messages display in time-ordered sequence from top to bottom of the messages list. In addition to the message links, you can add links that show association and aggregation relationships. These... more 

Designing a UML 1.5 Statechart Diagram 

Following are tips and techniques that you can use when working with UML 1.5 Statechart Diagram. 

Creating a Pin 

 

Designing a UML 2.0 Activity Diagram 

Use the following tips and techniques when you design a UML 2.0 Activity Diagram. Usually you create Activity Diagrams after State Machine Diagrams. 

Grouping Actions into an Activity 

 

Working with an Object Flow or a Control Flow 

You can create control flow or object flow as an ordinary link between the two node elements. The valid nodes are highlighted when the link is established.
You can scroll to the target element if it is out of direct reach, or you can use the context menu command to avoid scrolling.
There are certain limitations stipulated by UML 2.0 specifications:

• Object flow link must have an object at least on one of its ends.
• It is impossible to connect two actions with an object flow except through an output pin on the source action.
• Control flow link may not... more 

Designing a UML 2.0 Component Diagram 

Following are tips and techniques that you can use when working with UML 2.0 Component Diagrams. It can be convenient to start creation of a model with Component Diagrams if you are modeling a large system. For example, a distributed, client-server software system, with numerous interconnected modules. You use Component Diagrams for modeling a logical structure of your system, while you use Deployment Diagrams for modeling a physical structure. 

Creating a Delegation Connector 

 

Creating an Internal Structure for a Node 

 

Creating a Referenced Part 

 

Creating a Port 

 

Working with a Collaboration Use 

 

Designing a UML 2.0 Deployment Diagram 

Use the following tips and techniques when you design a UML 2.0 Deployment Diagram. It can be convenient to start creation of a model with Deployment Diagrams if you are modeling a large system that is comprised of multiple modules, especially if these modules reside on different computers. You use Deployment Diagrams for modeling a physical structure of your system, while you use Component Diagrams for modeling a logical structure. 

Associating a Lifeline with a Classifier 

 

Copying and Pasting an Execution or Invocation Specification 

Clipboard operations are supported for the execution and invocation specifications. 

Creating a Sequence or Communication Diagram from an Interaction 

 

Creating a State Invariant 

 

Designing a UML 2.0 Sequence or Communication Diagram 

Use the following tips and techniques when you design a UML 2.0 Sequence or Communication Diagrams. Usually you create Interaction Diagrams after Class Diagrams.
Whenever an interaction diagram is created, the corresponding interaction is added to the project. Interactions are represented as nodes in the Model View. depends on the view type defined in the Model View options on the default or project group levels. If model-centric mode is selected, an interaction is shown both under its package node and diagram node. If diagram-centric mode is selected, an interaction is... more 

Linking Another Interaction from an Interaction Diagram 

 

Working with a UML 2.0 Message 

This section describes techniques for working with messages in sequence and communication diagrams. Although the two diagram types are equivalent, the techniques for dealing with messages differ. 

Working with a Combined Fragment 

 

Working with a Tie Frame 

 

Associating a Transition or a State with an Activity 

You can associate an activity (created on some UML 2.0 Activity Diagram) with a state (on entering the state, while doing the state activity, and on exiting the state), or with a transition between states. 

Creating a Guard Condition for a Transition 

 

Creating a History Element 

 

Creating a Member for a State 

 

Creating a State 

 

Designing a UML 2.0 State Machine Diagram 

Following are tips and techniques that you can use when working with UML 2.0 State Machine Diagram. 

Browsing a Diagram with Overview Pane 

 

Hiding and Showing Model Elements 

You can control the visibility of elements on a diagram by using the Hide command (available on the context menu for individual diagram elements), and the Show/Hide command (available on the diagram context menu). 

Using View Filters 

For global control over the diagram view, you can use the filters in the Options dialog window. 

Zooming a Diagram 

Use the diagram context menu to obtain the required magnification in the Diagram View. 

Working with a Complex State 

The techniques in this section pertain to models of particularly complex composite states and substates.
You can resize the main state. You can also create a substate by drawing a state diagram within another state diagram and indicating start, end, and history states as well as transitions.
Create a composite state by nesting one or more levels of states within one state. You can also place start/end states and a history state inside of a state, and draw transitions among the contained substates. 

Creating a Deferred Event 

You can add a deferred event to a state element. 

Creating an Internal Transition 

 

Creating a Multiple Transition 

 

Creating a Self-Transition 

 

Specifying Entry and Exit Actions 

You can create entry and exit actions as nodes, or as stereotyped internal transitions. 

Working with an Instance Specification 

You can instantiate a classifier using the Object InspectorProperties Window or the in-place editor. 

Working with a Provided or Required Interface 

 

Creating an Association Class 

 

Creating an Inner Classifier 

This section includes instructions for adding inner classifiers to classes (including Windows classes, such as Windows forms, Inherited forms, User Controls and so on), structures, and modules (collectively, containers) in implementation projects.
You can add inner classifiers to class diagram elements (containers) using the respective context menu for the diagram element in the Diagram or Model Views. You can also select a classifier in the Tool PaletteToolbox and click the container element in the Diagram View to add the inner classifier to the container element. Structure elements are available for... more 

Using a Class Diagram as a View 

Class diagrams can also be used to create subviews of the project. 

Working with an Interface 

This topic describes how to create and hide an interface on a class diagram. 

Working with a Relationship 

You can change the type of an association link. 

Adding a Member to a Container 

You can add members to class diagram elements (containers) by using the respective context menu for the diagram element in the Diagram or Model Views or available shortcut keys to add members to a class diagram container element. 

Changing Appearance of Compartments 

You can collapse or expand compartments for the different members of class, interface, namespace, module (Visual Basic projects only), enum, and structure (C# projects only) elements. By default, the compartments for these elements are displayed on the diagram as a straight line. You can use the Options dialog window to set viewing preferences for compartment controls. Adding compartment controls is particularly useful when you have large container elements with content that does not need to be visible at all times. 

Changing Appearance of Interfaces 

 

Working with a Constructor 

You can create as many constructors in a class as needed.
In design projects, a constructor is created as an operation with the <<constructor>> stereotype.
In implementation projects, each new constructor is created with its unique set of parameters. In addition to creating parameters automatically, you can define the custom set of parameters, using the Object InspectorProperties Window.  

Working with a Field 

This topic applies to implementation projects only.
In the source code, it is possible to declare several fields in one line. This notation is represented in diagram as a number of separate entries in the Fields section if a class icon. However, you can rename the fields, change modifiers, set initial values and so on, all modifications being applied to the respective field in the diagram icon. Also you can copy and move such fields in diagram (using context menu commands or drag-and-drop), and the pasted field appears in the target container separately. 

Associating a Message Link with a Method 

Message links can be associated with the methods of the recipient class. The methods can be selected from the list of existing ones or can be created. This is done by two commands provided by the message context menu: Add and Choose method.
You can use the Operation field in the Object InspectorProperties Window to rename the method. A dialog box appears asking if you want to create a new method or rename the old one. 

Generating an Incremental Sequence Diagram 

You can generate incremental sequence diagrams from a previously-generated sequence diagram. In some cases, you can have generated a sequence diagram with a low nesting value such as 3 or 5. The nesting value limits how deep the parser traverses the source code calling sequence. 

Creating a Browse-Through Sequence of Diagrams 

You can link entire diagrams at one level of detail to the next diagram up or down in a sequence of increasing granularity, or you can link from key use cases or actors to the next diagram. 

Creating an Extension Point 

 

Designing Use Case Hierarchy 

Use case diagrams typically represent the context of a system and system requirements.