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

In the given UML activity diagram, "action 1" is an action that executes the classifier behavior (intrinsic behavior) of an instance. The correct UML action that represents this behavior is:

A. CallBehaviorActionis used to call a behavior directly, but not necessarily the classifier behavior of the input object.

B. CallOperationActionis used to call an operation, which is not the intrinsic behavior of an instance.

C. StartObjectBehaviorActionis the correct answer. This action starts the execution of the classifier behavior of an object.

D. CallClassifierBehaviorActionis not a standard UML action.

References:

UML Specification: Actions section, which explains the various types of actions including the StartObjectBehaviorAction.

Further details about actions that initiate behaviors of objects can be found in the UML 2.5 Documentation, specifically in the chapters discussing Actions in Activity diagrams.

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.

References:

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 UML 2, a “critical” section in a sequence diagram, like the one depicted, refers to a period where certain interactions are protected so that they can be executed without interruption or interference from other interactions (events). This is akin to a critical section in multi-threading where certain threads have exclusive access to resources or operations for a period of time. The correct answer is option C because it aligns with this definition: during the “critical” section on the sequence diagram, no other events may interfere between its events.

To provide the ability to specify CORBA physical components within a UML tool, the most appropriate approach is to create a UML profile that includes stereotypes, tagged values, and constraints that reflect the characteristics and requirements of CORBA components. Applying this profile to a UML model would extend the semantics of UML to support CORBA-specific concepts without modifying the UML metamodel itself. This approach allows the modeler to leverage the existing UML tooling while incorporating the additional semantics required for CORBA components. This practice is supported by the extensibility mechanisms provided by UML, as described in the UML 2.x Superstructure Specification, which outlines how to create and apply profiles.

The UML (Unified Modeling Language) specification, which is a part of the MOF (Meta-Object Facility) framework, suggests that the choice between creating a MOF-based metamodel and a UML profile depends on the specific needs of the domain being modeled. A MOF-based metamodel might be more appropriate for domains that require defining a completely new set of modeling concepts, whereas a UML profile is suitable for domains where the extension ofexisting UML concepts is sufficient. Since the specification recognizes the variability in modeling requirements across different domains, it emphasizes the importance of understanding the domain to make an informed decision on the modeling approach. The UML specification, therefore, does not prescribe a one-size-fits-all solution but rather leaves the decision to the modeler, based on the domain-specific requirements.

The UML sequence diagrams provided do not offer enough information to definitively determine the order of event occurrences. Sequence diagrams are used to show how objects interact in a given scenario, particularly the order of messages exchanged between objects. However, without a clear indication of the sequence or additional context, it’s impossible to ascertain which event occurs last.

In UML 2.x, sequence diagrams can be interconnected, but the execution order across separate diagrams is not inherently defined unless explicitly specified. Therefore, based on the information given, the answer is D, as we cannot uniquely determine the last event occurrence without additional details.

References:

OMG Unified Modeling Language (OMG UML), Infrastructure Version 2.5

UML 2.x specifications and sequence diagram notations

Assuming the system is inStateA1, the behaviors (or actions) executed when moving toStateCwould begin with any behaviors associated with internal transitions or exit actions withinStateA1. Transitiona6would be the trigger to go fromStateA1toStateA2, executinga4(the exit action ofStateA1) before the transition. Upon exitingStateAaltogether (a3is the exit action forStateA), the system would follow the transition labeleda1toStateB, executinga7as the entry action ofStateB. Then, the transition fromStateBtoStateCwould occur, likely with an internal trigger withinStateBor by completion, followed bya11to complete the transition intoStateC. The actions follow the flow of state transitions and the associated entry and exit actions as prescribed by UML state machine behavior specifications.