MCQ IN COMPUTER SCIENCE & ENGINEERING

Detailed explanation-1: -"An object diagram is a graph of instances, including objects and data values. A static object diagram is an instance of a class diagram; it shows a snapshot of the detailed state of a system at a point in time. The use of object diagrams is fairly limited, namely to show examples of data structure."

Detailed explanation-2: -We have already discussed that an object diagram is an instance of a class diagram. It implies that an object diagram consists of instances of things used in a class diagram. So both diagrams are made of same basic elements but in different form.

Detailed explanation-3: -An InstanceDiagram is a part of the UnifiedModelingLanguage that one does not see mentioned too often. The basic idea is to make a static snap shot of instances (not classes) in your system or subsystem. Make it show exactly who points to whom.

Detailed explanation-4: -The class diagram provides an abstract view which comprises of classes and their relationships, whereas the object diagram represents an instance at a particular point of time. The object diagram is actually similar to the concrete (actual) system behavior. The main purpose is to depict a static view of a system.

Detailed explanation-5: -A communication diagram (called collaboration in previous version of UML) without messages is also known as an object diagram, and the relationships between objects are called links. An object diagram must be a valid instantiation of a static class diagram.