OMG OMG Certified UML Professional 2 (OCUP 2) - Advanced Level OMG-OCUP2-ADV300 Exam Dumps: Updated Questions & Answers (September 2025)

In UML, a stereotype is a mechanism that extends the vocabulary of the UML in order to create new model elements. The given profile fragment defines a stereotype «architecture decision» that extends the metaclassClass. This stereotype includes three properties: Complexity, Risk, and Status, each typed by specific enumerations: Rank and Status. When a stereotype is applied to a UML element, it does not create physical attributes on the element; instead, it enables the element to carry additional information as specified by the stereotype — in this case, as Stereotype Properties. These properties are effectively tagged values that are associated with the stereotyped element. Hence, when a class is stereotyped as an «architecture decision», it will have the ability to hold values for Complexity, Risk, and Status according to the types defined bythe enumerations in the profile. This is consistent with the rules defined in the UML 2.x Superstructure Specification for profiles and stereotypes.

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.

StateMachine Redefinition in UML allows for the specialization of a StateMachine by a derived Classifier. This is crucial as it ties into the broader capability of UML to specialize behaviors and classifiers:

Ais incorrect; UML does discuss StateMachine Redefinition.

Bdescribes one aspect of redefinition but is too narrow as it omits that redefinition can also redefine transitions and internal behaviors, not just states or events.

Cdescribes more of an error correction or revision process, which is not specifically what StateMachine Redefinition is about.

Dcaptures the essence of StateMachine Redefinition, emphasizing that it is a necessary extension of UML's capabilities to allow for specialization and refinement of classifiers and their behaviors.

References:

UML Specification, Section on StateMachines

StateMachine Redefinition is further elaborated in UML 2.5 Documentation under the Behavior StateMachines sections.

The scope of fUML (Foundational UML) is to define execution semantics for a subset of the UML 2 metamodel that provides a shared foundation for higher-level UML modeling concepts. This includes the precise definition of the execution semantics of that subset, which is intended to be used by a wide range of system types, including physically distributed and concurrent systems without assumptions about global synchronization1.

The approach described in option B aligns with the concept of template classifiers in UML, which allows for the creation of parameterized elements that can be instantiated with different arguments. By modelingVehicleas a template classifier with a parameter namedThrustor, other modelers can instantiate this template with their chosen propulsion system, as long as it is a type that specializes thePropulsionSystemabstract class. This method provides the flexibility needed for modelers to tailor theVehicleclass to different propulsion systems while enforcing that only derivatives ofPropulsionSystemcan be used as the actual parameter forThrustor. This tactic of using template classifiers and class parameters is an application of UML's syntax and semantics for creating modular and customizable models. This practice is detailed in the UML 2.x Superstructure Specification, particularly in the sections describing template classifiers and their parameters.

In Option C, the propertiessuitable road surfaceandaverage speedhave been redefined in the subclassesRecumbent BikeandRacing Bike. The use of the{redefines}keyword in UML signifies that the subclass will provide its own specific values for these properties, overriding the general ones provided by the superclassBicycle. This is the correct way to enforce that each specialization ofBicyclehas a unique set of values for these attributes, as redefinition allows for the customization of inherited properties on a per-subclass basis. The use of{redefines}is specified in the UML 2.x Superstructure Specification, which describes how properties inherited from a superclass can be customized by subclasses.

In the diagram, "mycarVehicle" represents a class that likely encapsulates the concept of a vehicle within the system being modeled. The elements within "mycarVehicle" are properties that represent different parts of the car. The term "wheels" is not explicitly shown in the diagram, but based on UML conventions and the context provided, it would be a property of the Vehicle class. This property would likely be associated with the "frontleft" and "frontrightwheels" parts of the car. In UML, properties represent structural features of a class that hold data values or references to other objects. The correctness of this answer is consistent with the principles found in the UML 2.x Superstructure Specification regarding the structural features of classes.

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 inachieving this goal by limiting the scope to the essential elements necessary for execution, thereby reducing complexity and potential for misinterpretation.

The execution semantics of Alf (Action Language for Foundational UML) are defined by mapping the concrete syntax of Alf to the abstract syntax of fUML3. Alf provides a textual surface representation for a subset of UML model elements, and its main benefit is an execution semantics that allows for the generation of executable code out of Alf specifications4. This mapping ensures that Alf can be used to specify behavior in a way that is directly executable in the context of an fUML model.

The compiled model resulting from the Action Language for Foundational UML (fUML) must have the equivalent effect as a model resulting from the mapping to fUML. In other words, the compiled model should behave in the same way as if it were directly executed using the fUML execution semantics