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

For question number 50, the correct answer is C: Control tokens are offered on the outgoing Control Flows of the ExceptionHandler. According to the UML 2.5 specification, when an Exception Handler completes its execution, it does not halt the execution of the thread or retain control tokens internally; instead, it passes control tokens along the outgoing Control Flows. This behavior allows the activity to continue processing other behaviors or activities, based on the exception handling outcome.

References:

UML 2.5 Specification: Provides a detailed description of the behavior of Exception Handlers within activity diagrams, including how control tokens are managed upon the completion of an exception handling sequence.

During the lexical analysis of Action Language for Foundational UML (fUML) text, whitespace (such as spaces, tabs, and line breaks) is discarded. The lexical analysis focuses on identifying meaningful tokens (such as keywords, identifiers, and operators) while ignoring whitespace, which does not contribute to the semantics of the language2.

In the context of UML 2.0 and the specifications around Decision Nodes, option C is the correct choice. According to the UML 2.5 specification, when a Decision Node has an incoming control flow and adecisionInput, thedecisionInputmust have a single input parameter (in Parameter). This ensures that the decision node can evaluate the decision input using the value passed through the incoming control flow. This mechanism is crucial for decision-making processes within activity diagrams where decisions are made based on dynamic data provided at runtime.

References:

UML 2.5 Specification: The specification details the properties and behaviors of Decision Nodes within activity diagrams, particularly emphasizing how decision inputs and their parameters are handled.

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.

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 UML, class templates are the concept used to create classes that can be parameterized with different data types. This feature satisfies the first condition, allowing collections to support any data type. Class templates can be specialized, fulfilling the second condition, where some collections can inherit from others, thus enabling the reuse of functionality. Additionally, UML allows for operations to be defined in such a way that they cannot be overridden, by specifying them as non-virtual or final, which meets the third condition. Therefore, the use of class templates would be the most suitable approach for the design criteria specified by the programming language designers. This approach is consistent with the capabilities of class templates as described in the UML 2.x Superstructure Specification.

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.

In addition to ObjectFlow, which is used to denote the flow of objects between activities in a UML Activity diagram, data movement can also be facilitated through:

A.Pin is a point on a node that is used to accept or provide objects or data, but does not move data by itself.

B.Correct. Variables can be used to hold and move data within an activity, facilitating state maintenance or transitions between different actions.

C.Property, while it holds data, typically pertains to classes or components, not activities.

D.ControlFlow dictates the order of execution but does not inherently move data.

References:

UML Specification: Activity Diagrams section.

Details on how data can be managed within activities can be explored in the UML 2.5 Documentation, particularly under Activity and Object Nodes.

In UML, a specialized behavior that is an extension or modification of a more general behavior is typically shown using the generalization relationship. Option A correctly models this scenario by showing behavior B as a specialization of behavior A, which is indicated by the containment within the package and a nesting of B inside A without any stereotype on the relationship. This representation implies that B inherits the characteristics of A while potentially adding or overriding some aspects of it.

References:

UML 2.5 Specification: Generalization is defined in the UML 2.5 Specification, where a more specific classifier may override the behaviors of a more general classifier.