OMG-OCUP2-ADV300 Exam Dumps

In UML, profiles are applied to specific model elements to adapt the UML metamodel to different domains or platforms. The provided diagram shows a UML package diagram within which the Versioning profile is applied to the 'Business Logic' package, and the DBProfile is applied to the 'Data' package. This is a correct use of profiles in UML as they allow the customization of parts of a model by applying additional constraints and stereotypes to specific packages or classes. There is no restriction in UML that a profile cannot be applied to multiple packages in the model simultaneously, and profiles do not necessarily need to be members of the namespace of the model they are applied to; they can be defined externally. Therefore, the scenario presented is a correct application of two different profiles to two distinct packages within the same model, conforming to the UML 2.x Superstructure Specification.

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.

In UML 2.5, a NamedElement can have a name attribute, which is a string representing the element's name, and a nameExpression attribute, which is a ValueSpecification used to specify the element's name in a more dynamic way. The presentation of the name of a NamedElement in a tool that conforms to the OMG specification could either be the literal name (as specified in the name attribute) or the evaluated expression from the nameExpression property. Therefore, a tool may choose to present either the simple name or the evaluated expression or allow toggling between the two. The specification does not mandate a single fixed presentation, allowing for flexibility in how tools display the name. This conforms to the OMG's UML 2.5 specification, which describes the properties of NamedElement and their presentations within tools.

In UML Sequence Diagrams, a 'neg' (negative) combined fragment is used to specify invalid or forbidden interactions. Therefore:

A . Incorrect, because a 'neg' fragment defines an invalid interaction, so following it by normal positive constructs does not affect its interpretation of invalidity.

B . Incorrect, as nesting a 'neg' fragment within another 'neg' fragment does not inherently result in valid traces.

C . Correct. Normal positive constructs followed by a 'neg' fragment define some sequences of interactions as invalid, which is the intended use of the 'neg' fragment.

D . Incorrect, because an 'assert' fragment is used to specify required interactions, and containing a 'neg' fragment within it does not make the invalid traces valid.

UML Specification: Interactions section, particularly the explanation of combined fragments and their meanings.

The negative combined fragment and its semantics are discussed in the UML 2.5 Documentation, under the Sequence Diagrams and Combined Fragments sections.

In the MOF class hierarchy, the class 'Element' sits at the top.It is the superclass of all classes defined in MOF and is an implicit superclass of all metaclasses defined using MOF1. This superclass relationship to 'Element' does not need to be explicitly declared in the metamodels.