OMG Certified UML Professional 2 (OCUP 2) - Advanced Level OMG-OCUP2-ADV300 Exam Practice Test

Answer : C

The Profile mechanism in UML provides the capability to adapt existing metamodel elements for specific purposes. Profiles allow modelers to extend the standard UML metamodel with additional semantics by defining stereotypes, tagged values, and constraints that are specific to a particular domain, platform, or methodology. This means that profiles tailor the existing UML metamodel elements to create domain-specific models without changing the underlying metamodel itself. This adaptation mechanism is described in the UML 2.x Superstructure and Infrastructure Specifications, which detail how profiles can be used to customize the UML for particular domains or purposes.

Answer : C

State Machine Events in UML are triggers for transitions and do not classify as objects or classifiers; thus they do not inherently have features:

A . Incorrect, because State Machine Events are not treated as classifiers with features.

B . Incorrect, though it hints at an extended use case, State Machine Events do not extend classifiers in standard UML usage.

C . Correct, State Machine Events are not Classifiers and therefore cannot have features such as properties or operations.

D . Incorrect, because UML State Machines certainly have an Event concept, but these Events are not classified as having features.

UML Specification: State Machine chapter, specifically sections discussing the nature of events and triggers.

Further insights can be found in the event and trigger management sections of the UML 2.5 Documentation.

Answer : B

A template signature in UML specifies a set of formal parameters that can be substituted by actual parameters when a template is instantiated. This template signature is part of a templateable element, which is the element that can be parameterized using the template mechanism in UML. The template signature defines the formal template parameters that will be replaced by actual values or types when a bound element is created from the template. This concept is detailed in the UML 2.x Superstructure Specification, particularly in the sections describing templates and how they are used to create reusable and customizable model elements.

Answer : C

A stereotype in UML is a powerful extension mechanism that allows developers to tailor UML models for particular domains or platforms. Stereotypes can adapt UML model elements by adding constraints, changing notation, and adding attributes and operations.However, they cannot remove existing constraints from a model element12.

Notation Change (A):Stereotypes can indeed change the notation of a model element to make it more expressive or domain-specific.For example, a stereotype could be used to visually distinguish between different kinds of classes in a class diagram1.

Adding Constraints (B):Stereotypes can add new constraints to a model element to specify additional rules or requirements that are not defined by the standard UML1.

Removing Constraints :This is not a capability of stereotypes. Constraints define rules that must be followed, and once they are part of a model element, they cannot be removed by a stereotype.Instead, they are an intrinsic part of the model's definition1.

Adding Attributes and Operations (D):Stereotypes can be used to add attributes and operations to a model element, which allows for the specification of additional properties or behaviors that are not part of the standard UML metamodel1.

In summary, while stereotypes are versatile and can extend the capabilities of UML model elements in various ways, they do not have the ability to remove constraints that are already applied to those elements.This is because constraints are considered fundamental rules that govern the integrity of the model, and removing them would potentially violate the model's correctness or completeness1.

Answer : B

In the context of the diagram, 'clientNo' is placed next to the association line between 'ExamCompany' and 'Examinee,' which indicates that 'clientNo' is a qualifier of the association. In UML, a qualifier is used to refine the association between two classes by providing a way to access linked objects based on some attribute value. The qualifier essentially acts as a key in an associative array or map, allowing access to instances of the associated class. In this case, 'clientNo' is likely used to uniquely identify examinees associated with an exam company. This use of qualifiers is detailed in the UML 2.x Superstructure Specification, which describes how qualifiers can be used to specify refined access to linked objects within an association.

Answer : A

The reason for fUML to be compact is to facilitate the definition of clear semantics. A smaller, more focused subset of UML allows for a more precise and unambiguous specification of the execution semantics.This clarity is essential for ensuring that models are executed consistently and as intended across different tools and platforms2. The compact nature of fUML helps in achieving this goal by limiting the scope to the essential elements necessary for execution, thereby reducing complexity and potential for misinterpretation.

Answer : E

When a template classifier is used to specify the type of a typed element, the actual parameters for the template classifier's formal parameters must be provided by a set of bound elements. This means that for a template classifier to be used as a type, there must be a corresponding binding that specifies what elements are used as arguments for its template parameters. This allows the typed element to have a concrete type that is a specific instantiation of the template classifier with particular values for its template parameters. This use of template classifiers is described in the UML 2.x Superstructure Specification, which details how template binding works to create specific instances of template classifiers.