SOFTWARE DESIGN
OBJECT ORIENTED DESIGN
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Object Diagram
|
|
|
Class Diagram
|
|
|
Component Diagram
|
|
|
System Diagram
|
Detailed explanation-1: -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: -A UML object diagram represents a specific instance of a class diagram at a certain moment in time.
Detailed explanation-3: -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.
Detailed explanation-4: -An Object Model Diagram shows the interaction between objects at some point, during run time. A Class Diagram will show what the Objects in your system consist of (members) and what they are capable of doing (methods) mostly static.