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

Answer : C

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.

Answer : B

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.

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.

Answer : C

State Machine Events in UML are triggers for transitions and do not classify as objects or classifiers; thus they do not inherently have features:

A . Incorrect, because State Machine Events are not treated as classifiers with features.

B . Incorrect, though it hints at an extended use case, State Machine Events do not extend classifiers in standard UML usage.

C . Correct, State Machine Events are not Classifiers and therefore cannot have features such as properties or operations.

D . Incorrect, because UML State Machines certainly have an Event concept, but these Events are not classified as having features.

UML Specification: State Machine chapter, specifically sections discussing the nature of events and triggers.

Further insights can be found in the event and trigger management sections of the UML 2.5 Documentation.

Answer : C

Protocol Conformance in UML is a relationship between protocol state machines that ensures consistency in behavior inheritance:

A . Incorrect as it describes a general-to-inherited relationship, which is not the focus of protocol conformance.

B . Incorrect, as it describes a relationship the wrong way around (general to nested).

C . Correct. Protocol Conformance ensures that a specific Protocol State Machine conforms to the rules and constraints specified by a redefined, more general Protocol State Machine.

D . Incorrect, because it generally describes conformance but does not specifically focus on the relationship between specific and general state machines in the context of protocols.

UML Specification: Protocol State Machines section.

Specifics of protocol conformance are detailed under state machine and classifier behaviors in the UML 2.5 Documentation.

Answer : C

Protocol State Machines in UML are used to specify the allowable protocol transitions that can be observed in the instances of a classifier. The interpretations that can be defined for protocol state machines are:

A . Behavioral and protocol are not specific types of interpretations but rather describe aspects of state machines in general.

B . Declarative and procedural describe styles or approaches to programming or specification, not specific to UML state machine interpretations.

C . Declarative and executable is the correct answer. Declarative interpretations specify the allowed sequences of events in a state machine, while executable interpretations are concerned with the actual implementation that can be executed by a machine.

D . Executable and non-executable are distinctions but not specifically pertaining to protocol state machine interpretations alone.

UML Specification: State Machines chapter, particularly sections on protocol state machines.

Further details can be found in the UML 2.5 Documentation discussing the differences between different state machine interpretations.

Answer : D

A FunctionBehavior in UML is a specialized form of behavior that specifies a function that, when executed, yields results influenced only by its input arguments and its internal attributes, without any side effects (e.g., altering global variables or I/O operations). This makes it stateless. Among the options provided:

A involves I/O operations which are not covered under FunctionBehavior as it implies side effects.

B deals with environmental inputs and actuator control, not just function computation.

C could be considered but implies a state change which again might involve side effects, depending on the implementation.

D purely involves calculation based on input parameters, which fits the definition of FunctionBehavior perfectly, as it is a stateless computation.

E is incorrect because UML indeed includes the concept of FunctionBehavior.

UML Specification, Section on Behaviors

Further details on FunctionBehaviors can be found in the UML 2.5 Documentation under the Classification and Behaviors sections.

Answer : C

Assuming the system is in StateA1, the behaviors (or actions) executed when moving to StateC would begin with any behaviors associated with internal transitions or exit actions within StateA1. Transition a6 would be the trigger to go from StateA1 to StateA2, executing a4 (the exit action of StateA1) before the transition. Upon exiting StateA altogether (a3 is the exit action for StateA), the system would follow the transition labeled a1 to StateB, executing a7 as the entry action of StateB. Then, the transition from StateB to StateC would occur, likely with an internal trigger within StateB or by completion, followed by a11 to complete the transition into StateC. The actions follow the flow of state transitions and the associated entry and exit actions as prescribed by UML state machine behavior specifications.