What is Object Diagram in UML? Learn with Example

By : Amelia Parker Amelia Parker
Hours Updated

⚡ Smart Summary

Object Diagram in UML captures a static snapshot of a system, showing specific object instances, their attribute values, and links at one moment. This resource explains object diagram notation, drawing steps, purpose, and how it differs from a class diagram.

  • 📸 Snapshot View: An object diagram freezes the system at one instant, showing concrete instances rather than general structure.
  • 🏷️ Notation: Object names are underlined, and each object lists its class plus current attribute values.
  • 🖊️ Drawing Steps: Identify objects, clarify their relations and associations, then name and explore each object.
  • 🎯 Purpose: Object diagrams model the static aspect of a system and support forward and reverse engineering.
  • 🔄 Class vs Object: A class diagram shows the abstract blueprint; an object diagram shows one real instance of it.
Read More

What is Object Diagram in UML

Before we learn Object Diagram, let’s understand-

What is Class Diagram?

A class represents things that are put together having common behavior. It is a blueprint of an object-oriented system

Let us consider an exciting example of classes and objects. We all know cars like Ferrari, Volkswagen, Mercedes, and Porsche, etc. These are all cars manufacturing companies. Here, we can consider that a car is a class and Ferrari, Mercedes are the objects

Class Diagram in UML
Class Diagram Notation

What is Object Diagram in UML?

An Object Diagram describes the instance of a class. It visualizes the particular functionality of a system. The difference between the class and object diagram is that the class diagram mainly represents the bird’s eye view of a system which is also referred to as an abstract view.

Objects are the real-world entities whose behavior is defined by the classes. Objects are used to represent the static view of an object-oriented system. We cannot define an object without its class. Object and class diagrams are somewhat similar.

Notation of an Object Diagram

Object Diagram Notation

Object Diagram Notation

Object Diagram Example

Object Diagram Example

Object Diagram Example

The above UML object diagram contains two objects named Ferrari and BMW which belong to a class named as a Car. The objects are nothing but real-world entities that are the instances of a class.

How to Draw Object Diagram

Below are the steps to draw Object Diagram in UML:

  • Step 1) Before drawing an object diagram, one should analyze all the objects inside the system.
  • Step 2) The relations of the object must be known before creating the diagram.
  • Step 3) Association between various objects must be cleared before.
  • Step 4) An object should have a meaningful name that describes its functionality.
  • Step 5) An object must be explored to analyze various functionalities of it.

RELATED ARTICLES

Purpose of Object Diagram

  • It is used to describe the static aspect of a system.
  • It is used to represent an instance of a class.
  • It can be used to perform forward and reverse engineering on systems.
  • It is used to understand the behavior of an object.
  • It can be used to explore the relations of an object and can be used to analyze other connecting objects.

Applications of Object Diagram

Following are the applications of Object Diagram:

  • Object diagrams play an essential role while generating a blueprint of an object-oriented system.
  • Object diagrams provide means of modeling the classes, data and other information as a set or a single unit.
  • It is used for analyzing the online or offline system. The functioning of a system can be visualized using object diagrams.

Class Diagram Vs. Object Diagram

Serial no. Class Object
1 It represents static aspects of a system. It represents the behavior of a system in real time.
2 It doesn’t include dynamic changes. It captures runtime changes of a system.
3 It never includes attributes or data values of an instance. It includes attributes and data values of any instance.
4 Class Diagram manipulates the behavior of objects. Objects are instances of classes.

FAQs

An object diagram shows a static snapshot of objects and their values at one instant. A sequence diagram shows dynamic behavior—the time-ordered messages objects exchange. Object diagrams capture state; sequence diagrams capture interaction over time.

An object diagram is called a snapshot because it freezes the system at one moment, showing specific objects, their attribute values, and links. Unlike a class diagram, it captures a concrete instance rather than the general structure.

You can create many object diagrams from a single class diagram. Each object diagram represents one possible instance of the classes with different objects and values, so one class model can illustrate countless real scenarios.

AI diagram tools can read a class definition or description and generate a sample object diagram with realistic instances and values. This helps beginners see concrete examples, though the generated objects should be checked for accuracy.

Yes. Some AI tools take a class diagram and produce an object diagram by instantiating classes with example data. The result illustrates how the model looks at runtime, but you should verify the values and links.

Summarize this post with: