Kapitel 21. Collaboration Diagram Model Element Reference

Inhaltsverzeichnis

21.1. Introduction
21.1.1. Limitations Concerning Collaboration Diagrams in ArgoUML
21.2. Classifier Role
21.2.1. Classifier Role Details Tabs
21.2.2. Classifier Role Property Toolbar
21.2.3. Property Fields For Classifier Role
21.3. Association Role
21.3.1. Association Role Details Tabs
21.3.2. Association Role Property Toolbar
21.3.3. Property Fields For Association Role
21.4. Association End Role
21.4.1. Association End Role Details Tabs
21.4.2. Association End Role Property Toolbar
21.4.3. Property Fields For Association End Role
21.5. Message
21.5.1. Message Details Tabs
21.5.2. Message Property Toolbar
21.5.3. Property Fields For Message

21.1. Introduction

This chapter describes each model element that can be created within a collaboration diagram. Note that some sub-model elements of model elements on the diagram may not actually themselves appear on the diagram.

There is a close relationship between this material and the properties tab of the details pane (see Abschnitt 13.3, „Das Register Eigenschaften“). That section covers Properties in general, in this chapter they are linked to specific model elements.

[Achtung]Achtung

Collaboration diagrams are not fully developed yet in ArgoUML. Many aspects are not fully implemented, or may not behave as expected. In particular there are some serious problems with layout of the collaboration roles and messages.

Abbildung 21.1, „Possible model elements on a collaboration diagram.“ shows a collaboration diagram with all possible model elements displayed.

Abbildung 21.1. Possible model elements on a collaboration diagram.

Possible model elements on a collaboration diagram.


21.1.1. Limitations Concerning Collaboration Diagrams in ArgoUML

The collaboration diagram is still rather under-developed in ArgoUML. In particular there is no way to show instance collaborations (based on objects and links) rather than specification collaborations.

The biggest difficulties are with the messages. There are problems with the sequencing of the messages and their display on the diagram. The actions behind them are purely textual in implementation and there is no way to link them back to their associated operations or signals.