Two or more association ends are associated with each association (see Section 16.5, “Association”), although for ArgoUML, the number of ends can only be two.
Within the UML metamodel, AssociationEnd is a
sub-class of ModelElement.
The association end has no direct access on any diagram, although its stereotype, name and multiplicity is shown at the relevant end of the parent association (see Figure 16.1, “Possible artifacts on a use case diagram.”). Where shared or composite aggregation is selected for one association end, the opposite end is shown as a solid diamond (composite aggregation) or hollow diamond (shared aggregation).
![[Tip]](images/tip.png) | Tip |
|---|---|
Although you can change attributes of association ends when creating a use case model, this is often not necessary. Many of the properties of an association end relate to its use in class diagrams, and are of limited relevance to use cases. The most useful attributes to consider altering are the name (used as the role name) and the multiplicity. | |
![[Note]](images/note.png) | Note |
|---|---|
ArgoUML does not currently support qualifiers, as described in the UML 1.3 standard. | |
The details tabs that are active for associations are as follows.
ToDoItemStandard tab.
PropertiesSee Section 17.12.2, “Association End Property Toolbar” and Section 17.12.3, “Property Fields For Association End” below.
DocumentationStandard tab. See Section 12.5, “Documentation Tab”.
SourceStandard tab. This tab contains a declaration for the association end as an instance of the artifact to which it is connected.
ConstraintsStandard tab. ArgoUML only supports constraints on Classes and Features (Attributes, Operations, Receptions, and Methods), so this tab is grayed out.
Tagged ValuesStandard tab. In the UML metamodel,
AssociationEndhas the following standard tagged values defined.derived(from the superclass,ModelElement). Valuestrue, meaning the association end is redundant—it can be formally derived from other elements, orfalsemeaning it cannot.Tip Derived association ends still have their value in analysis to introduce useful names or concepts, and in design to avoid re-computation. However the tag only makes sense for an association end if it is also applied to the parent association.
Note The UML
Elementmetaclass from which all other artifacts are derived includes the tagged elementdocumentationwhich is handled by the documentation tab under ArgoUML
Go upNavigate up to the association to which this end belongs.
Go to other endThis navigates to the other end of the association.
NameText box. The name of the association end, which provides a role name for this end of the association. This role name can be used for navigation, and in an implementation context, provides a name by which the source end of an association can reference the target end.
Note ArgoUML does not enforce any naming convention for association ends.
StereotypeDrop down selector. Association end is provided by default with the UML standard stereotypes for AssociationEnd (
association,global,local,parameter,self). However ArgoUML does not provide any of these by default. Only the stereotypeimplicitis present.Navigate Stereotype
icon. If a
stereotype has been selected, this will navigate to the
stereotype property panel (see Section 15.4, “Stereotype”).AssociationText box. Records the parent association for this association end. Button 1 double click on this entry will navigate to that association.
TypeDrop down selector providing access to all standard UML types provided by ArgoUML and all new classes created within the current model.
This is the type of the entity attached to this end of the association.
Tip By default ArgoUML will select the class of the artifact to which the linkend is connected. However, an association can be moved to another class by selecting another entry here.
MultiplicityDrop down menu with edit box. The value can be chosen from the drop down box, or a new one can be edited in the text box. Records the multiplicity of this association end (with respect to the other end), i.e. how many instances of this end may be associated with an instance of the other end. The multiplicity is shown on the diagram at that end of the association.
ModifiersThere are 3 modifiers:
navigable,orderedandstatic. All 3 are checkboxes.navigable. Indicates that this end can be navigated to from the other end.Note The UML 1.3 standard provides a number of options for how navigation is displayed on an association end. ArgoUML uses option 3, which means that arrow heads are shown at the end of an association, when navigation is enabled at only one end, to indicate the direction in which navigation is possible. This means that the default, with both ends navigable has no arrows.
orderedWhen placed on one end, specifies whether the set of links from the other instance to this instance is ordered. The ordering must be determined and maintained by Operations that add links. It represents additional information not inherent in the objects or links themselves. Possibilities for the checkbox are: Unchecked - The links form a set with no inherent ordering. Checked - A set of ordered links can be scanned in order.Static(To be written)
SpecificationList. Designates zero or more Classifiers that specify the Operations that may be applied to an Instance accessed by the AssociationEnd across the Association. These determine the minimum interface that must be realized by the actual Classifier attached to the end to support the intent of the Association. May be an Interface or another Classifier. The type of classifier is indicated by an icon.
Button 1 double click navigates to the selected classifier, button 2 click brings a pop up menu with one entry.
AggregationRadio box, with three entries
composite,noneandaggregate. Indicates whether the relationship with the far end represents some type of loose whole-part relationship (aggregation) or tight whole-part relationship (composite).Shared aggregation is shown by a hollow diamond at the “whole” end of the association. Composite aggregation is shown by a solid diamond.
Note You may not have aggregation at both ends of an association. ArgoUML does not enforce this constraint.
The “whole” end of a composite aggregation should have a multiplicity of one. ArgoUML does not enforce this constraint.
ChangeabilityRadio box, with three entries
changeable,add onlyandfrozen. Indicates whether instances of this end of the attributed may be: i) created and deleted by the source after the target instance is created; ii) created but not deleted after the target instance is created; or iii) not created or deleted by the source after the target instance is created.VisibilityRadio box, with three entries
public,privateandprotected. Indicates whether navigation to this end may be by: i) any classifier; ii) only by the source classifier; or iii) only the source classifier and its children.
