RAD Studio (Common)
ContentsIndex
PreviousUpNext
UML 1.5 Class Diagrams

This section describes the elements of UML 1.5 Class Diagrams.

Name 
Description 
Association classes appear in diagrams as three related elements:
  • Association class itself (represented by a class icon)
  • N-ary association class link (represented by a diamond)
  • Association connector (represented by a link between both)
Association classes can connect to as many association end classes (participants) as required.
The Object InspectorProperties Window of an association class, association link, and connector contain an additional Association tab. This tab contains the only label property, its value being synchronized with the name of the association class. For the association classes and association end links, the Custom node of the Object InspectorProperties Window displays... more 
There are several kinds of relationships:
  • Association: A relationship between instances of the two classes. There is an association between two classes if an instance of one class must know about the other to perform its work. In a diagram, an association is a link connecting two classes. Associations can be directed or undirected. A directed link points to the supplier class (the target). An association has two ends. An end may have a role name to clarify the nature of the association. A navigation arrow on an association shows which direction the association can be traversed or queried.... more 
There are two types of class diagrams used in Together:
  • Package (namespace) diagrams. These diagrams are referred to as package diagrams in design projects, and namespace diagrams in implementation projects. They are stored as XML files in the ModelSupport_%PROJECTNAME%ModelSupport folder of the project groupsolution with the file extension .txvpck.
  • Logical class diagrams. These diagrams are stored as XML files in the ModelSupport_%PROJECTNAME%ModelSupport folder of the project groupsolution with the file extension .txvcls.
Together automatically creates a default namespace diagram for the project and for each subdirectory under the project directory. The default project diagram... more 
The table below lists the diagram container elements along with the inner classifiers that you can add to container elements.
Inner classifiers  
The impact of changing a class, interface, or namespace on a logical class diagram varies according to the kind of change:
  • Changing the name, adding a member, creating a new link, or applying a pattern makes the corresponding change in the actual source code.
  • Choose Delete from View on the context menu of the element to remove the element from a current diagram and keep the element in the namespace (package).
  • Choose Delete on the context menu to completely remove the element from the model.
  • When you press Delete on the keyboard, the Delete from view command is applied, if... more 
Note that the set of available members is different for the design and implementation projects.
The table below lists the diagram elements along with the members that can be added using the context menu of the element. The type of applicable project is specified in square brackets.
Members available  
Using Together, you can create language-neutral class diagrams in design projects, or language-specific class diagrams in implementation projects. For implementation projects, all diagram elements are immediately synchronized with the source code. 
The table below lists the elements of UML 1.5 class diagrams that are available using the Tool PaletteToolbox.
UML 1.5 class diagram elements  
Copyright(C) 2008 CodeGear(TM). All Rights Reserved.
What do you think about this topic? Send feedback!