OMG-OCUP2-ADV300 Leak Questions

"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.

References:

• 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.

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.

References:

• 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.

UML allows the introduction of new concepts that are not part of the standard UML metamodel by creating a profile. To add capabilities for modeling requirements and tracing relationships in UML, a profile can be created where a Class is stereotyped to represent a requirement, and a Dependency is stereotyped to represent the trace relationship. This approach is both practical and conforms to the UML standard's mechanisms for extending the language. It is a common practice to create such profiles for requirements engineering within the UML framework. This conforms to the UML 2 Superstructure Specification, which provides guidelines on creating and applying profiles and stereotypes.

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.

References:

• 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.