UML Question
-
When you document a class using the UML you can show the visibility of the various member functions and variables through the use of -, # and + to indicate private, protected and public visibility. However, when you use graphical methods to show aggregation or association what is the implied visibility here - private? How would you indicate any other type of visibility - through the use of stereotypes? If so, is there a standard method for doing this? This is something my UML books seem to gloss over. Phil
-
When you document a class using the UML you can show the visibility of the various member functions and variables through the use of -, # and + to indicate private, protected and public visibility. However, when you use graphical methods to show aggregation or association what is the implied visibility here - private? How would you indicate any other type of visibility - through the use of stereotypes? If so, is there a standard method for doing this? This is something my UML books seem to gloss over. Phil
http://www.omg.org/ OMG Unified Modeling Language Specification, Version 1.4 September 2001 3.43 Association End 3.43.2.9 visibility
"Specified by a visibility indicator (‘+’, ‘#’, ‘-’ or explicit
property name such as {public}) in front of the rolename. Specifies the
visibility of the association traversing in the direction toward the
given rolename. See Section 3.25, “Attribute,” on page 3-41 for details
of visibility specification. Other properties can be specified for
association ends, but there is no graphical syntax for them. To specify
such properties, use the constraint syntax near the end of the
association path (a text string in braces). Examples of other properties
include mutability." -
http://www.omg.org/ OMG Unified Modeling Language Specification, Version 1.4 September 2001 3.43 Association End 3.43.2.9 visibility
"Specified by a visibility indicator (‘+’, ‘#’, ‘-’ or explicit
property name such as {public}) in front of the rolename. Specifies the
visibility of the association traversing in the direction toward the
given rolename. See Section 3.25, “Attribute,” on page 3-41 for details
of visibility specification. Other properties can be specified for
association ends, but there is no graphical syntax for them. To specify
such properties, use the constraint syntax near the end of the
association path (a text string in braces). Examples of other properties
include mutability."Excellent - thanks very much! Having the actual spec to hand is a good idea - thanks for the link. Phil