Most Recent OMG-OCUP2-ADV300 Exam Questions & Answers

'QueryCustomerFromParcel' is annotated with the transformation stereotype, which indicates that it is a behavior element that specifies how to convert input objects into output objects. Therefore, the answer is D, a Behavior element, for example, an Activity, State Machine, or OpaqueBehavior. In UML, the transformation stereotype is applied to specify that an action or activity is responsible for transforming an input (in this case, 'Parcel') into an output ('Customer'), typically by employing a specific behavior element.

UML 2.5 Specification: Section on Object Flows describes how transformations can be used within activity diagrams to turn inputs into outputs using behavior elements.

A coregion in a UML Sequence Diagram is a notation that:

A . Incorrect, as interactions are behavioral units that can involve multiple lifelines and are not specific to a coregion.

B . Incorrect, as combined fragments are constructs that control flow with interaction operands, not directly related to a coregion.

C . Correct. A coregion is a shorthand notation for a parallel combined fragment on a single lifeline. It allows for the representation of parallel behavior within a single lifeline.

D . Incorrect, as the area between lifelines for communication is not what defines a coregion.

UML Specification: Sequence Diagrams section, specifically about coregion and combined fragments.

The concept and usage of coregions in sequence diagrams are further elaborated in the UML 2.5 Documentation, under the Sequence Diagrams section.

The correct answer is B, which uses a selection edge to specify task behavior based on task priority. In UML, an object flow with a selection property is used to select objects from a collection according to some criterion, which is typically represented by a Boolean expression. In the case of B, the selection criterion is described as 'ordering = the most important first', indicating that tasks are selected to be executed based on their priority.

UML 2.5 Specification: The UML 2.5 specification describes how selection behaviors can be applied to object flows to filter objects according to specific criteria, such as priority in this scenario.

A UML profile can define several different elements to extend the UML for a specific domain, platform, or purpose. Besides stereotypes, a profile can define DataTypes and Enumerations, which can be used within Stereotypes to type the tagged values. A profile can also define Classes, which can be used as base classes for stereotypes. However, a profile does not typically define instances of elements, such as Objects, nor does it define composite structures, such as Components. The intent of a profile is to adapt existing metamodel elements through the use of stereotypes, tag definitions, and constraints rather than to create instances or define system architectures. This definition and use of a profile are aligned with the guidelines in the UML 2.x Superstructure Specification, which outlines what elements a profile can define within the UML framework.

In fUML (Foundational UML), an execution model must be modeled as an Activity.fUML is a subset of UML that includes the ability to model behavior using UML activities, which are composed of a rich set of primitive actions1.Activities in fUML represent the executable aspects of a model and define the flow of control and data2. They are the primary means for specifying the detailed procedural logic of the behavior of a system within fUML.