Object diagrams show classes at the instance level.
Since objects are not on the same conceptual level as classes, although very closely related, they are expressed in separate diagrams. On the other hand, objects are on the same conceptual level as instances of components and instances of nodes. That's why Poseidon for UML combines the functionality for creating Object diagrams, Component diagrams and Deployment diagrams into a single editor; therefore, to create an Object diagram, use the editor for the Component diagram
This may not seem very intuitive at first, but we found it to be very useful. Objects, component instances and node instances can thus be used conjunctively. You can still restrict yourself to use only objects and their links in a deployment diagram.
The diagram elements and toobar options are provided here for quick reference. A much more comprehensive look at the editor is provided in the section on Component diagrams.
Nodes - Nodes represent the hardware elements of the deployment system.
Components - Components stand for software elements that are deployed to the hardware system.
Links - Links are used to connect instances of nodes or objects.
Dependencies - Dependencies exist between components and can be specified by utilizing predefined or user-defined stereotypes.
Associations - Associations are used to display communication relations between nodes. They can be specified by utilizing predefined or user-defined stereotypes.
Instance Specifications, Classes, Interfaces - Components and nodes can include objects, classes or interfaces.
|Add or remove space between elements|
|Link between two Instance Specifications|
|Interface As Circle|
|Connect Comment to Element|