Question 1

In Unified Modeling Language, diagrams which captures systemstatic structure and provide foundation for other models is called&#10;A)deployment diagrams&#10;B)class diagrams&#10;C)component diagrams&#10;D)object diagrams

Accepted Answer

Class diagrams capture the static structure of a system, showing the system's classes, their attributes, operations (or methods), and the relationships among objects. They are foundational for other types of diagrams in UML, serving as a blueprint for the system's structure.

Question 2

The Unified Modeling Language (UML) has become an effective standard for software modelling.How many different notations does it have&#10;A)three&#10;B)four&#10;C)six&#10;D)nine

Accepted Answer

UML consists of nine different types of diagrams, which are used for various aspects of software modeling, including structure, behavior, and interaction.

Question 3

Which model in system modelling depicts the static nature of the system&#10;A)behavioral model&#10;B)context model&#10;C)data model&#10;D)structural model

Accepted Answer

The structural model depicts the static nature of a system, focusing on the organization and relationships between the system's components rather than on the dynamic behavior or data flow within the system.

Question 4

A Class consists of which of these abstractions&#10;A)set of the objects&#10;B)operations&#10;C)attributes&#10;D)all of the mentioned

Accepted Answer

A class in object-oriented programming is an abstraction that encapsulates data for the objects (attributes) and behavior (operations) of those objects. It can be thought of as a blueprint from which individual objects are created, thus encompassing all of the mentioned aspects.

Question 5

Which among these are the rules to be considered to form Class diagrams&#10;A)class symbols must have at least a name compartment&#10;B)compartment can be in random order&#10;C)attributes and operations can be listed at any suitable place&#10;D)none of the mentioned

Accepted Answer

Class symbols in UML class diagrams must have at least a name compartment to identify the class. The other options are incorrect because compartments have a defined order (usually name, attributes, then operations), and attributes and operations are not placed randomly but within their specific compartments.

Question 6

Which of these are the heuristics&#10;A)name classes, attributes, and roles with noun phrases&#10;B)name operations and associations with verb phrases&#10;C)stick to binary associations&#10;D)all of the mentioned

Accepted Answer

Heuristics in the context of software engineering and design, particularly in object-oriented design, include guidelines such as naming classes, attributes, and roles with noun phrases, naming operations and associations with verb phrases, and sticking to binary associations. These are general rules of thumb that help in creating more understandable, maintainable, and consistent designs.

Question 7

Which of the following is a building block of UML&#10;A)things&#10;B)relationships&#10;C)diagrams&#10;D)all of the mentioned

Accepted Answer

UML (Unified Modeling Language) is built upon several key components, including things, relationships, and diagrams, making all of the mentioned options correct building blocks of UML.

Question 8

Classes and interfaces are a part of&#10;A)structural things&#10;B)behavioral things&#10;C)grouping things&#10;D)annotational things

Accepted Answer

Classes and interfaces are considered structural things in UML as they define the static structure of a system.

Question 9

What is a collection of operations that specify a service of a class or component&#10;A)use case&#10;B)actor&#10;C)interface&#10;D)relationship

Accepted Answer

An interface is a collection of operations that specify a service of a class or component. It defines a set of methods or messages that an object can send to another.

Question 10

What is a physical element that exists at runtime in UML&#10;A)a node&#10;B)an interface&#10;C)an activity&#10;D)none of the mentioned

Accepted Answer

A node in UML represents a physical element that exists at runtime, such as a computer or a network device, which is capable of executing a software artifact.

Deck 1: Understanding UML Diagrams and Elements