Child pages
  • UML Diagrams
Skip to end of metadata
Go to start of metadata

This page is a draft at this point. Its goal is to hold all info about diagramming, that we think is valuable for our customers. Subscribe to the page if you want to stay in the loop.

We want to build a page about diagramming, that contains all relevant info for customers that we can come up with. This should be a content base for a lot of simple and straight forward guest blog posts for Atlassian partners and also ourselves.

This research page may contain unfinished or unconfirmed info!

This is a research page. Seibert Media uses research pages to prepare relevant topics and gather information about stories we want to run. Such research pages often evolve over a long period of time without quality assurance and cross-checking from our business experts. While all web content should be consumed cautiously, this page may still contain unconfirmed or unfinished information. Please use the live chat or a contact form on this page to help us improve it. Please ask us if you're unsure. We're happy to help if we can. Your interaction also helps us gauge interest in this research page, so don't hesitate to contact us.

Keywords: Diagramming, Diagrams in UML, Information visualization

UML Diagrams


UML Diagrams (Unified Modeling Language) is a way to visually represent the architecture, design, and implementation of complex software systems. The complexity of writing codes and keeping track of relationships and hierarchies within a software system is difficult. UML diagrams divide the software systems into components and subcomponents making it easier to organize and showcase engineering requirements. There are 14 types of UML diagrams, which are divided into two groups. 

Structural UML Diagrams
Show the static relationship between components in the system.
Behavioral UML Diagrams
Show how the components in the system react to each other, how the system captures changes, and in some diagrams how it changes overtime.


Types of UML Diagrams



UML communication diagrams (also known as collaboration diagrams) focuses on the message passed between objects. The notion used in the UML communication diagram is the same as the UML sequence diagram, although much simpler. More information about the different UML diagrams and how to create them are available through draw.io such as the UML usecase diagram, UML state diagram, and UML class diagram



Example of UML Diagrams

UML communication diagram
UML sequence diagram
UML use case diagram
UML interactive diagram
UML activity diagram
UML state diagram
UML class diagram

UML communication diagram source: draw.io blog

UML sequence diagram source: draw.io blog

















UML use case diagram source: draw.io blog

UML interactive diagram source: draw.io blog

UML activity diagram source: draw.io blog

UML state diagram source: draw.io blog

UML class diagram source: draw.io blog


UML Diagram Symbols & Relationships

As listed above there are many different types of UML diagrams and each has a slightly symbol set. The UML class diagram is perhaps one of the most common UML diagrams used, and the symbols used are centered around defining attributes of a class. A class symbol can be divided to show a class' attributes, operations, and overall responsibilities.  


visual notions - source: smartdraw


lines are very important when it comes to understanding the relationship between components, Generalisation and Inheritance are denoted with empty arrowheads. Composition is a filled diamond. Aggregation is an empty diamond. Dependencies are dashed-lines and <<>> indicate properties of that dependency. Multiplicity is shown with a number and * at opposite ends of a line. 

line notions - source: smartdraw


Resourceful Videos

Draw.io Template Manager
Draw.io Learn How
Draw.io Custom Library
Draw.io Make a Flow Chart
Draw.io Org Chart


Resourceful Links

See also

  • No labels
This page was last edited on 04/14/2021.