Design and Implementation

A. A node
B. An interface
C. An activity
D. None of the mentioned

A. Things
B. Relationships
C. Diagrams
D. All of the mentioned

A. Interaction diagrams are at their best when they deal with one main design flow and not multiple variants that can happen
B. Interaction diagrams are good at designing part or all of one use case’s functionality across multiple objects
C. Interaction diagrams allow the analyst to show iteration and conditional execution for messaging between objects
D. All of the mentioned

A. operations only
B. attributes only
C. both operations and attributes
D. none of the mentioned

A. An object is an instance of a class
B. An object includes encapsulation of data
C. An object is not an instance of a class
D. All of the mentioned

A. A class that has direct instances, but whose descendants may have direct instances
B. A class that has direct instances, but whose descendants may not have direct instances
C. A class that has no direct instances, but whose descendants may have direct instances
D. All of the mentioned

A. They can be used to discover parallel activities
B. They are used to depict workflow for a particular business activity
C. Activity diagram do not tell who does what and are difficult to trace back to object models
D. All of the mentioned

A. Generalization
B. Include
C. Extend
D. All of the mentioned

A. specify required services for types of objects
B. program in Java, but not in C++ or Smalltalk
C. define executable logic to reuse across classes
D. define an API for all classes