Design and Implementation

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

Explanation: All are the building blocks of UML which are further sub-categorized.

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

Explanation: Interaction diagram is used to describe some type of interactions among the different elements in the model. So this interaction is a part of dynamic behaviour of the system.

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

Explanation: In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system’s classes, their attributes, operations, and the relationships among objects.

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

Explanation: An object is an instance of a class.

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

Explanation: An abstract type is a type in a nominative type system which cannot be instantiated directly.

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

Explanation: Activity diagrams are graphical representations of workflows of step wise activities and actions with support for choice, iteration and concurrency.

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

Explanation: Generalization, include, extend all of these are valid relationships in use case diagrams.
advertisement

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

Explanation: An interface is like a template design for a class that contains no data or implementation; only definitions for methods, properties etc