UML Diagrams Zicomi Systems publishes some UML example diagrams online from the world famous UML dictionary. more...
Version 2.5 Released Zicomi Systems is delighted to announce that version 2.5 of Zicomi Mentor is released. With support for UML 2.0 and all thirteen UML diagrams more...
Zicomi Systems' Director speaks about the UML at Objects by Design - an informative interview more...
Partner Programme Zicom Systems is delighted to announce a new world wide partner programme, become a partner today. more...
OMG Member Zicom Systems is made a member of the OMG!
Permission
A permission is a type of dependency and therefore a directed relationship between one or more clients (tail end) and one or more suppliers (arrowhead end). The relationship signifies that the elements at the tail end (client) require access to the elements at the arrowhead end (supplier) and that this access is granted (permitted). There are no standard stereotypes of a permission defined in the UML.
Explanation
A permission is a type of dependency indicating that one or more model elements needs access to another set of elements and that this other set grants them permission to what they need. The permission may be to all or just part of the other elements. It is most commonly used in its singular form, with one element at the tail end (client) of the relationship and one element at the arrowhead end (supplier). There are no standard stereotypes defined in the UML that give the permission more precise meaning but package and element import relationships can be used or user-defined stereotypes added. We see this concept in our daily lives for example: when we are given a key to access material that would otherwise not be available to us.
A dependency is related to a permission because it is a type of dependency relationship. The permission specializes the more general dependency relationship, conveying that one element is granted rights to view the other element in some way. There are no standard stereotypes defined for a permission, but there are a number of related elements that express aspects of importing and accessing elements between namespaces.
A package import with keyword import is related to a permission because it has similar semantics but defines the accessibility of elements within another namespace. By using the keyword access the elements in the imported package (arrowhead end) are not added to the namespace but can be accessed by unqualified names from within the importing package.
A package import with keyword access is related to a permission because it has similar semantics but defines the accessibility of elements within another namespace. By using the keyword access the elements in the imported package (arrowhead end) are not added to the namespace but can be accessed by unqualified names from within the importing package.
A element import with keyword import is related to a permission because it has similar semantics but defines the accessibility of an element within another namespace. By using the keyword access the elements in the imported package (arrowhead end) are not added to the namespace but can be accessed by unqualified names from within the importing package.
A element import with keyword access is related to a permission because it has similar semantics but defines the accessibility of an element within another namespace. By using the keyword access the elements in the imported package (arrowhead end) are not added to the namespace but can be accessed by unqualified names from within the importing package.
