Scribd
Upload
48 views4 pages

UML Part 4

The document discusses the differences between object diagrams and class diagrams in UML. It states that object diagrams represent instances of classes at a specific time, while class diagrams provide an abstract view of a system. The document also provides examples of a class diagram with two classes and an object diagram showing instances of those classes.

Uploaded by

Luckysingh Negi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
48 views4 pages

UML Part 4

The document discusses the differences between object diagrams and class diagrams in UML. It states that object diagrams represent instances of classes at a specific time, while class diagrams provide an abstract view of a system. The document also provides examples of a class diagram with two classes and an object diagram showing instances of those classes.

Uploaded by

Luckysingh Negi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Object Diagram

Object diagrams are dependent on the class diagram as they are derived from the class diagram.

It represents an instance of a class diagram. The objects help in portraying a static view of an object-oriented system at a specific instant.

Both the object and class diagram are similar to some extent; the only difference is that the class diagram provides an abstract view of a
system. It helps in visualizing a particular functionality of a system.

Some people may find it difficult to understand the difference between a UML Class Diagram and a UML Object Diagram as they both
comprise of named "rectangle blocks", with attributes in them, and with linkages in between, which make the two UML diagrams look
similar.
Some people may even think they are the same because in the UML tool they use both the notations for Class Diagram and Object Diagram
are put inside the same diagram editor - Class Diagram.
But in fact, Class Diagram and Object Diagram represent two different aspects of a code base.

Class Diagram Example

The following Class Diagram example represents two classes - User and Attachment.

A user can upload multiple attachment so the two classes are connected with an association, with 0..* as multiplicity on the Attachment side.
Object Diagram Example

The following Object Diagram example shows you how the object instances of User and Attachment class "look like" at the moment
Peter (i.e. the user) is trying to upload two attachments.

So there are two Instance Specification for the two attachment objects to be uploaded.
Use Case Diagram

A use case diagram is used to represent the dynamic behavior of a system.

It encapsulates the system's functionality by incorporating use cases, actors, and their relationships.

It models the tasks, services, and functions required by a system/subsystem of an application. It depicts the high-level functionality of a
system and also tells how the user handles a system.

Use cases enable you to relate what you need from a system to how the system delivers on those needs.
Think of a use-case model as a menu, much like the menu you'd find in a restaurant.
By looking at the menu, you know what's available to you, the individual dishes as well as their prices.
You also know what kind of cuisine the restaurant serves: Italian, Mexican, Chinese, and so on. By looking at the menu, you get an overall
impression of the dining experience that awaits you in that restaurant.
The menu, in effect, "models" the restaurant's behavior.
Because it is a very powerful planning instrument, the use-case model is generally used in all phases of the development cycle by all team
members.

You might also like