#Bouml aggregation code
#Bouml aggregation series

In principle, however, an actor can not only be “User”, “Stakehoder” or “External System”. In the practice of modeling it is recommended to define the role unambiguously with stereotypes – e.g. As a model element, it can be an abstract person (e.g. In UML, an actor is a model element that interacts with a system. And also in IT, the term is used both in requirements management and in the course of Unified Modeling Language (UML) in the modeling of use cases. Indirectly, the actor also exists in business administration in the modelling of business processes and workflows.

#Bouml aggregation series

In films, series or on theatre stages he is an performer, in sociology a socially acting person or organisation. Mostly, he is an originator of an action. So, while 'directional' is perfectly valid, the term 'unidrectional' may be a better an less ambiguous option.The term actor is used in many fields. ' These diagrams (.) may show navigability (by an open arrowhead) or nonnavigability (by an X) either always, only for unidirectional associations (oneWay), or never' (section B.3.2 about structure diagrams).Only shown for one-way navigable associations, this probably signifies bidirectional navigability' Nevertheless, in many places, the standard uses explicitely 'unidirectional' and 'bidrectional': ' has no directional significance' (in section 20.1.4 about another kind of diagram).' Associations with navigability in both directions'.

' The arrow indicates that the Association is to be read as associating the end away from the direction of the arrow with the end to which the arrow is pointing'.The following wordings support the term 'directional': If an end is not navigable, access from the other ends may or may notīe possible, and if it is, it might not be efficient. The precise mechanismīy which such efficient access is achieved is implementation specific. Instances at the other ends of the Association. (instances of an Association) can be accessed efficiently from Navigability means that instances participating in links at runtime The UML standard v2.5 from OMG defines in section 11.5.Associations the principle of navigability: Does this means that 'directional' is a bad choice and it would be preferable to replace 'directional' by 'unidirectional' ?Įdit: some additional elements about terminolgy for the records Object *parent // you can navigate back (Element knows about parent)Ĭhristophe is right. Vector> element // ownnership by unique pointerīidirectional composition could then be something like: class Object Vector element // own by value for example

The unidirectional aggregation could therefore be for example: class Member // Elemetn doesn't know parent (=> unidirectional) For comparison, in MSVC2015 you find the notion of direction in the 'Is Navigable' property of the association. This 'directional' term refers hence to navigation possibility between the related objects. This kind of relation may considered to be a shortcut to define Generators will produce two attributes whose names are the roles's

#Bouml aggregation code

According to the wording used by the site of the BOUML UML toolbox, 'directional' has to be understood as 'unidirectional' (opposed to 'bidirectional') :Īggregation : to define a bi-directional aggregation, the code