Explanation of the UML arrows

by

Here’s some explanations from the Visual Studio 2015 docs:

UML Class Diagrams: Reference: https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2015/modeling/uml-class-diagrams-reference

UML class diagram

5: Association: A relationship between the members of two classifiers.

5a: Aggregation: An association representing a shared ownership relationship. The
Aggregation property of the owner role is set to Shared.

5b: Composition: An association representing a whole-part relationship. The Aggregation
property of the owner role is set to Composite.

9: Generalization: The specific classifier inherits part of its definition from the general
classifier. The general classifier is at the arrow end of the connector. Attributes, associations, and
operations are inherited by the specific classifier. Use the Inheritance tool to create a
generalization between two classifiers.

Package diagram

13: Import: A relationship between packages, indicating that one
package includes all the definitions of another.

14: Dependency: The definition or implementation of the dependent classifier might change if
the classifier at the arrowhead end is changed.

Realization relationship

15: Realization: The class implements the operations and attributes defined by the interface.
Use the Inheritance tool to create a realization between a class and an interface.

16: Realization: An alternative presentation of the same relationship. The label on the
lollipop symbol identifies the interface.

UML Class Diagrams: Guidelines: http://msdn.microsoft.com/library/dd409416%28VS.140%29.aspx

Properties of an Association

Aggregation: This appears as a diamond shape at one end of the connector. You can use it to
indicate that instances at the aggregating role own or contain instances of the other.

Is Navigable: If true for only one role, an arrow appears in the navigable direction. You can use
this to indicate navigability of links and database relations in the software.

Generalization: Generalization means that the specializing or derived type inherits attributes,
operations, and associations of the general or base type. The general type appears at the arrowhead
end of the relationship.

Realization: Realization means that a class implements the attributes and operations specified by
the interface. The interface is at the arrow end of the connector.

Let me know if you have more questions.

More Related Contents:

  1. What is the difference between association, aggregation and composition?
  2. What is the difference between aggregation, composition and dependency? [duplicate]
  3. Interface vs Abstract Class (general OO)
  4. What’s the difference between a method and a function?
  5. Interface vs Base class
  6. What is Inversion of Control?
  7. When to use an interface instead of an abstract class and vice versa?
  8. What does “program to interfaces, not implementations” mean?
  9. Method chaining – why is it a good practice, or not?
  10. What is the difference between an Instance and an Object?
  11. Does functional programming replace GoF design patterns?
  12. Why do we use Interface? Is it only for Standardization? [closed]
  13. What is the use of making constructor private in a class?
  14. Is returning null bad design? [closed]
  15. OOP vs Functional Programming vs Procedural [closed]
  16. Why don’t associated types for protocols use generic type syntax in Swift?
  17. Simple way to understand Encapsulation and Abstraction
  18. When should I use static methods in a class and what are the benefits?
  19. What is an abstract data type in object oriented programming?
  20. What is an example of the Single Responsibility Principle? [closed]
  21. Mediator Vs Observer Object-Oriented Design Patterns
  22. Can’t seem to understand SOLID principles and design patterns [closed]
  23. Why not use instanceof operator in OOP design?
  24. Is it bad practice for a class to have only static fields and methods?
  25. How to create a “single dispatch, object-oriented Class” in julia that behaves like a standard Java Class with public / private fields and methods
  26. What is the difference between Composition and Association relationship?
  27. In SOLID, what is the distinction between SRP and ISP? (Single Responsibility Principle and Interface Segregation Principle)
  28. When to use a Class in VBA?
  29. VBA: how to test for object equality (whether two variables reference the same object)
  30. Overloading functions

Leave a Comment