OMG-OCUP2-FOUND100 Exam Dumps : OMG Certified UML Professional 2 (OCUP 2) - Foundation Level

The diagram fragment shows an instance specification for anEmployee. 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 thesalaryattribute is the one that is hidden outside of thecurrent:Employeeclassifier and cannot be accessed by entities that do not belong to theEmployeeclass.

Therefore, the correct answer is:

C. salary

In the given UML package diagram fragment, various elements are listed with stereotypes indicating their nature («class», «interface»). Stereotypes are used in UML to extend the vocabulary of UML in order to create new kinds of building blocks. They are typically enclosed in guillemets (« »).

The last element, 'six', does not have a stereotype indicating whether it's a class, interface, or some other kind of element. This lack of a stereotype leads to ambiguity about the nature of 'six'. Therefore, the fragment is considered invalid due to this omission.

All the other options do not constitute an error in the UML fragment: A) A list of elements is allowed in a package body. B) Visibility is not required for every element, especially within package diagrams. C) Interfaces are allowed in packages. D) Private elements are allowed in a package. E) Protected elements are also allowed in a package.

Therefore, the correct answer is:

F. Element six is missing its stereotype.

In UML 2, a class diagram is used to depict the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among the classes. The constraint{age >= 18}in thePersonclass diagram indicates a condition that must hold true for the instances of thePersonclass whenever they are used in the context of aBankAccount. This constraint is an invariant of thePersonclass that specifies the rule for the attributeage.

Now, let's consider the provided options and explain why option B is correct:

A. The preferred age to open a bank account is 18 years old or older – This statement is incorrect because the diagram does not indicate a preference; it indicates a constraint or a rule.

B. Only customers who are 18 years old or older can open a bank account – This is the correct statement. The{age >= 18}constraint next to theageattribute of thePersonclass signifies that any instance ofPersonassociated with aBankAccountmust be at least 18 years old. SincePersonis connected toBankAccountwith the role namecustomer, this implies that only persons who are at least 18 can be customers of a bank account.

C. The age condition should only hold when the setAge(Integer) function is called – This statement is incorrect because the constraint{age >= 18}is not a condition that applies only when thesetAgeoperation is invoked. Instead, it is a class invariant that must always hold true for any instance ofPerson.

D. An object of Customer with age set to 18 or greater will raise an exception – This is incorrect because the UML diagram specifies a constraint, not an exception condition. The constraint ensures validity, not the raising of an exception.

The answer is verified according to the UML 2 Foundation documents, such as the UML 2.5 specification, where class diagrams and constraints are defined. The specification states that constraints are semantic conditions or restrictions expressed in natural language text or in a machine-readable language that must hold true for the system being modeled (UML 2.5 specification, section 7.9).