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

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.

References:

UML Specification: Protocol State Machines section.

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

In UML, the multiplicity of an association end specifies how many instances of the class at that end can participate in a single association. A lower multiplicity of one (1) at one end of an n-ary (where n > 2) association implies that there must be at least one link that combines the values of the other ends, but it doesn't require that a link exists for every possible combination. Therefore, it's possible for some combinations to exist as links, while others do not, which is indicated by the option that links combining the values of the other ends may exist or may not exist. This interpretation is consistent with the definition of multiplicity in associations as outlined in the UML 2.x Superstructure Specification.

fUML (Foundational UML) is a subset of the standard Unified Modeling Language (UML) that includes standard, precise execution semantics. This subset encompasses typical structural modeling constructs of UML such as classes, associations, data types, and enumerations, as well as the ability to model behavior using UML activities composed from a set of primitive actions. Therefore, a model constructed in fUML is executable in the same sense as a program in a traditional programming language, but with the level of abstraction and richness of expression of a modeling language2.

In Option C, the propertiessuitable road surfaceandaverage speedhave been redefined in the subclassesRecumbent BikeandRacing Bike. The use of the{redefines}keyword in UML signifies that the subclass will provide its own specific values for these properties, overriding the general ones provided by the superclassBicycle. This is the correct way to enforce that each specialization ofBicyclehas a unique set of values for these attributes, as redefinition allows for the customization of inherited properties on a per-subclass basis. The use of{redefines}is specified in the UML 2.x Superstructure Specification, which describes how properties inherited from a superclass can be customized by subclasses.

The UML model fragment that best supports the project's requirements for collection class design is one that allows the fixed length of the collections to be specified but also permits flexibility for collections longer than 25 elements. In Option C, theClarusCollectionclass is shown as a template class with a template parameterSizeset to a default of 25. However, the dashed lines and the separate box forTypeandSizeindicate that while there is a default value, it can be overridden. This means that theSizecan be parameterized, thus allowing the creation ofClarusCollectioninstances with different fixed lengths, not just 25. This design will enable most collections to be created with the default size of 25, but also allows for creating collections with sizes greater than 25, providing the flexibility required by the project's requirements. This adheres to the UML 2.x specification on templates and parameterization.

The correct representation of a binding of the template operationaddElement<E>withEbeing bound to the typeCardisaddElement (e : Card). This notation means that the template parameterEis being replaced by the concrete typeCard, thus instantiating the template operation with that specific type. In UML, this instantiation does not require the«bind»keyword or the template brackets<>around the type in the operation signature itself; it is simply represented by using the concrete type as the type of the parameter in the operation. Thisusage is consistent with the UML 2.x Superstructure Specification, which explains how operations of a template classifier are instantiated when template parameters are bound to actual types.

In UML, a stereotype is a mechanism that extends the vocabulary of the UML in order to create new model elements. The given profile fragment defines a stereotype «architecture decision» that extends the metaclassClass. This stereotype includes three properties: Complexity, Risk, and Status, each typed by specific enumerations: Rank and Status. When a stereotype is applied to a UML element, it does not create physical attributes on the element; instead, it enables the element to carry additional information as specified by the stereotype — in this case, as Stereotype Properties. These properties are effectively tagged values that are associated with the stereotyped element. Hence, when a class is stereotyped as an «architecture decision», it will have the ability to hold values for Complexity, Risk, and Status according to the types defined bythe enumerations in the profile. This is consistent with the rules defined in the UML 2.x Superstructure Specification for profiles and stereotypes.

The value of Essential MOF (EMOF) lies in its ability to provide a straightforward framework for mapping MOF models to implementations such as XML Metadata Interchange (XMI) for simple metamodels2. This allows for easier integration and manipulation of MOF models in various platforms and tools.

The compiled model resulting from the Action Language for Foundational UML (fUML) must have the equivalent effect as a model resulting from the mapping to fUML. In other words, the compiled model should behave in the same way as if it were directly executed using the fUML execution semantics

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.