UML: Basic Diagram Types
Last updated
Last updated
The Unified Modeling Language (UML) is a family of graphical notations, backed by single metamodel, that help in describing and designing software systems, particularly software systems built using the object-oriented (OO) style.
Class Diagram
Component Diagram
Deployment Diagram
Object Diagram
Package Diagram
Profile Diagram
Composite Structure Diagram
Use Case Diagram
Activity Diagram
State Machine Diagram
Interaction Diagram
Sequence Diagram
Communication Diagram
Interaction Overview Diagram
Timing Diagram
Describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects.
It does not describe the functionality of the system but it describes the components used to make those functionalities.
Represents the deployment view of a system. It consists of nodes. Nodes are nothing but physical hardware used to deploy the application.
Object diagrams represent an instance of a class diagram. Object diagrams also represent the static view of a system but this static view is a snapshot of the system at a particular moment.
Describes the dependencies between the packages that make up a model.
Operates at the metamodel level to show stereotypes as classes with the «stereotype» stereotype, and profiles as packages with the «profile» stereotype.
Shows the internal structure of a class and the collaborations that this structure makes possible.
A representation of a user's interaction with the system that shows the relationship between the user and the different use cases in which the user is involved.
Graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency.
Describes the behavior of system. This behavior is analyzed and represented as a series of events that can occur in one or more possible states.
Shows object interactions arranged in time sequence. It depicts the objects and classes involved in the scenario and the sequence of messages exchanged between the objects needed to carry out the functionality of the scenario.
Models the interactions between objects or parts in terms of sequenced messages. Communication diagrams represent a combination of information taken from Class, Sequence, and Use Case Diagrams describing both the static structure and dynamic behavior of a system.
It's similar to the activity diagram, in that both visualize a sequence of activities. The difference is that, for an interaction overview, each individual activity is pictured as a frame which can contain a nested interaction diagram.
Changes from one state to another are represented by a change in the level of the lifeline. For the period of time when the object is a given state, the timeline runs parallel to that state.
Alternative notation:
