OMG OMG-OCUP2-FOUND100 Online Practice Questions and Exam Preparation

OMG OMG-OCUP2-FOUND100 Online Questions & Answers

• Question 71:

  Consider the following model

  

  Where is v visible?

  A. Only inside S
  B. Only inside T
  C. Only inside S and T
  D. Inside the whole P
  C. Only inside S and T

  ---

  Explanation

  In UML, visibility of an attribute is determined by the scope of the classifier it belongs to and its visibility markers. The attribute 'v' is marked with a '-' sign, indicating it is private. Being private, it would normally be visible only within the class it is defined in, which is 'S' in this case. However, since 'T' is a subclass of 'S' (as indicated by the generalization relationship, a line with a closed, unfilled arrowhead), it inherits the attribute 'v'. Therefore, 'v' is visible in both 'S' and 'T'. Option A is incorrect because it does not consider inheritance.

  Option B is incorrect for the same reason.

  Option D is incorrect because a private attribute in a class is not visible to the entire package, only to the class itself and its subclasses. The UML 2.5 specification states that a private member is only accessible within the namespace it is defined (section 7.5.3). Since 'T' is within the namespace of 'S' due to inheritance, 'v' is visible in both.

• Question 72:

  Consider the following class definition:

  

  Which diagram fragment shows an instance of the Company class in which name has the value OMG?

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  E. Option E
  D. Option D

  ---

  Explanation

  An instance should be written as : Company and show the attribute value.

  D correctly shows name = "OMG" (though it unnecessarily includes String).

  Key point: "OMG" must be the value of name, not the object name.

• Question 73:

  Consider the following diagram:

  

  Which element(s) from P3 are visible inside P2 without using a qualified name?

  A. None
  B. One
  C. TWo
  D. One and Two
  B. One

  ---

  Explanation

  In UML, the <<import>> relationship indicates that the namespace of the target element (in this case, P3) is added to the namespace of the source (in this case, P2). However, it's important to distinguish between different types of imports.

  There are two types of import relationships:

  Public Import: If P2 were to import P3 publicly (using <<import>>), then all public members of P3 would become accessible to P2 as if they were part of P2. Private Import: If P2 were to import P3 privately (using <<access>>), then the public members of P3 are only accessible within P2 and not to elements that use P2. Given the diagram, it seems that

  P2 is importing P3 (the nature of the import, public or private, is not explicitly mentioned). Assuming it is a public import and considering that P2 itself is within P1, which is the higher-level package, then P1 has visibility over its own contents as well as any elements imported into P2. Element One P3 in has the same name as One P1 in, and typically in UML, when an element is imported into a namespace where an element with the same name exists, the imported element is not accessible without a qualified name to avoid ambiguity. However, since P2 is within P1, it could be argued that One P3 in, when imported, would effectively "merge" with One P1 in, reby making One visible inside P2 without a qualified name due to its presence in the higher-level package.

• Question 74:

  Which statement is correct about EnumerationLiterals in UML?

  A. They may appear more than once with the same name in one Enumeration.
  B. They may be anonymous if their order is unique.
  C. They are named constants defined by an Enumeration.
  D. They are operations owned by an Enumeration.
  C. They are named constants defined by an Enumeration.

  ---

  Explanation

  An Enumeration defines a set of named literals, and each EnumerationLiteral is one of those named constants. These literals are not operations, and they are not anonymous. Their names must be unique within the Enumeration so that they can be referenced without ambiguity. The key idea is that an Enumeration provides a closed set of explicit named values, and EnumerationLiterals are those values.

• Question 75:

  Consider the following diagram:

  

  Which change could the modeler make to fix the UML error in this model?

  A. Specify a unique value in the position slot for each instance specification
  B. Add a description slot to a 1.
  C. Change the type of ClassB.version from Real to Integer
  D. Change the type of ClassA.position from Integer to Real.
  B. Add a description slot to a 1.

  ---

  Explanation

  In the UML diagram given, we see two classes, ClassA and ClassB, with ClassB inheriting from ClassA ClassA. has two attributes, position of type Integer and description of type String ClassB. introduces an additional attribute, version of type Real.

  Looking at the instance specifications (the right part of the diagram), we have three instances: a1 of type ClassA, b1 of type ClassB, and b2 also of type ClassB. In UML, an instance specification must comply with the structure of its classifier, which means an instance of ClassA must show slots for both position and description, whereas an instance of ClassB must show slots for position description,, and version.

  In the provided diagram, instance a1 of ClassA only shows a slot for position. This is an error because it does not show a slot for description, which is a defined attribute of ClassA. To correct this error, we would need to add a description slot to a1.

  This means that the correct answer is:

  B. Add a description slot to a1. The other options do not correct the error in the model:

  A. Specifying unique values for position does not address the missing description slot in a1.

  C. Changing the type of ClassB.version from Real Integer to is not required by any UML constraint in the context given.

  D. Changing the type of ClassA.position from Integer Real to does not address the missing description slot in a1 and is unrelated to the inheritance structure.

• Question 76:

  Consider the following diagram:

  

  Is this diagram valid?

  A. No, because a DataType cannot have Associations to a Class.
  B. No, because a DataType cannot have Operations.
  C. No, because a DataType cannot have Attributes.
  D. Yes, it is formally correct.
  A. No, because a DataType cannot have Associations to a Class.

  ---

  Explanation

  The provided diagram depicts a DataType named Route with operations, attributes, and associations to a Class named City. In UML, a DataType is a type of classifier that specifiesthe values that do not have identity (i.e., are not distinguishable from other objects). DataTypes may contain Attributes and Operations, so options B and C are incorrect.

  However, DataTypes should not have associations to Classes because DataTypes are meant to be value types without identity, and associations typically imply a relationship between instances (which have identity). Thus, the presence of associations from Route to City is not consistent with the definition of a DataType.

  References:

  UML 2.x Superstructure Specification: Sections on Classifiers and DataTypes provide definitions of what constitutes a DataType and what features they can have. They specifically mention that DataTypes are kinds of classifiers that do not have identity and are often used to type attributes. UML 2.x Infrastructure Specification: This foundational document gives additional context on the semantics of different types of classifiers, including DataTypes, and how they relate to other elements in a UML model.

• Question 77:

  Consider the following diagram;

  

  What is the minimum number of occurrences that must happen before the reception of m(200)?

  B. 2
  C. 4
  D. 5
  E. 6
  B. 2

  ---

  Explanation

  The diagram shown is a UML Sequence Diagram, which is used to depict the interaction and order of messages between objects.

  In the given diagram, we can see two occurrences of the message 'm' with different parameters (100 and 200), and one occurrence of the message 'p' with the parameter "run". To determine the minimum number of occurrences that must happen before the reception of 'm(200)', we look at the order of messages: The message 'm(100)' must occur.

  The message 'p("run")' must occur after 'm(100)' and before 'm(200)'. These two occurrences are the minimum necessary before 'm(200)' can be received by the object. The dashed line represents a return message, which does not count as an occurrence for this purpose.

• Question 78:

  Consider the following diagram fragment:

  

  Which slot's value is hidden outside of the current Employee9

  A. age
  B. name
  C. salary
  D. title
  E. gender
  F. company
  C. salary

  ---

  Explanation

  The diagram fragment shows an instance specification for an Employee. The different prefixes before each attribute indicate the visibility of that attribute:

  +Public: Visible to everyone. -Private: Visible only within the defining class. #Protected: Visible to subclasses and package. ~Package: Visible to all classes within the same package. Given these visibility indicators, the attribute with the private visibility is -salary: Real. This means that the salary attribute is the one that is hidden outside of the current:Employee classifier and cannot be accessed by entities that do not belong to the Employee class.

  Therefore, the correct answer is:

  C. salary

• Question 79:

  Which statement is true about the following diagram?

  

  C. C will be executed when B or D finishes.
  D. After A finishes, either B or D will be executed, but not both.
  D. After A finishes, either B or D will be executed, but not both.

  ---

  Explanation

  The diagram likely represents a UML activity diagram, which is used to model the workflow of a system. The correct answer is D because it reflects the behavior of decision nodes and concurrent flows in UML activity diagrams. In UML, when an activity reaches a decision node (depicted as a diamond), it chooses one among several alternative flows. In this case, after the completion of action A, the flow must decide between B or D, but not both, which is a fundamental aspect of decision nodes in UML. This is supported by the UML 2.5 specification, which states that a decision node routes tokens to one of the available outgoing edges based on the conditions evaluated at runtime, ensuring that only one path is taken. Furthermore, the UML specification explains that the notation for decision nodes and the semantics of token flows are such that they support the modeling of conditional and concurrent behaviors within an activity. This is essential for accurately capturing the logic of complex systems and their operations. For a more in-depth understanding, you can refer to the UML 2.5.1 specification provided by the Object Management Group (OMG), which details the notation and semantics of activity diagrams, including decision nodes and flows. Additionally, studying the official OMG UML 2 Certification Guide can provide further clarification on these concepts.

• Question 80:

  Consider the following diagram:

  

  According to the diagram, which statement describes the property db?

  A. The property db is a primary key
  B. The property db is a static property.
  C. The property db is inherited from a superclass.
  D. The property db is important and is emphasized by the modeler with an underline.
  B. The property db is a static property.

  ---

  Explanation

  In UML, a static property is one that belongs to the class itself rather than any instance of the class. In UML diagrams, static properties are denoted by underlining the property name.

  Now, let's review the options:

  A. There is no UML notation in the diagram that specifies whether the property db is a primary key. Primary keys are a database concept and UML does not have a standard way to denote them.

  B. The property db is underlined, which indicates that it is a static property. This is the correct UML notation for depicting a class-level attribute.

  C. There is no indication in the diagram that db is inherited from a superclass. Inherited properties typically are not underlined (unless they are also static), and there is no superclass shown in the diagram.

  D. Underlining in UML does not signify importance or emphasis by the modeler, it indicates that a property is static. Therefore, the answer is B: The property db is a static property. This is based on standard UML notation as outlined in the UML 2.5 Specification by the Object Management Group (OMG), which dictates that static members (attributes or operations) are underlined in class diagrams.