1
If a use case has five system events for a specific scenario then the number of interaction diagrams will always be atleast five TrueView Answer
2
Interaction diagrams are the outcomes of dynamic modeling TrueView Answer
3
In a UML interaction diagram the singleton object is shown with '1' in the upper left corner of the object box FalseView Answer
4
Multiple communication diagrams CANNOT be used to show each concrete polymorphic case in sequence diagram FalseView Answer
5
In interaction diagrams, parentheses for a message are usually excluded if there are no parameters TrueView Answer
6
Class diagrams are the only important diagram in Object Oriented design. FalseView Answer
7
Each new object is added to the right side in sequence diagrams. TrueView Answer
8
UML is only a visual modeling language, knowing its details CANNOT teach you how to think in objects TrueView Answer
9
UML is a standard visual modeling language, knowing its details teach you how to think in objects FalseView Answer
10
Cohesion measures “how software elements are functionally related the operations” TrueView Answer
11
Coupling measures “how software elements are functionally related the operations” FalseView Answer
12
In communication diagrams the first message is called a lost message. FalseView Answer
13
In communication diagrams the first message is called a found message. TrueView Answer
14
In communication diagrams the first message is not numbered TrueView Answer
15
You can show class or static method calls by using a lifeline box label that indicates the receiving object is a class, or more precisely, an instance of a metaclass TrueView Answer