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

Answer : A

The reason for fUML to be compact is to facilitate the definition of clear semantics. A smaller, more focused subset of UML allows for a more precise and unambiguous specification of the execution semantics.This clarity is essential for ensuring that models are executed consistently and as intended across different tools and platforms2. The compact nature of fUML helps in achieving this goal by limiting the scope to the essential elements necessary for execution, thereby reducing complexity and potential for misinterpretation.

Answer : A

The correct representation of a binding of the template operation addElement<E> with E being bound to the type Card is addElement (e : Card). This notation means that the template parameter E is being replaced by the concrete type Card, 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. This usage 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.

Answer : C

In the given diagram, myType1 is shown redefining prop1, which was originally of type Integer. Given that Integer is a subtype of Number, and myType1 is used in a redefinition context, it implies that myType1 must also be a subtype of Number. In UML, when a property is redefined, the redefining property must be type compatible with the property it redefines. Therefore, myType1 could be substituted by any subtype of Number, which includes Integer, Real, and all their subtypes (Short, Long, Float, Double, etc.). This is based on the UML principle of type conformance in property redefinition, as specified in the UML 2.x Superstructure Specification.

Answer : C

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, the ClarusCollection class is shown as a template class with a template parameter Size set to a default of 25. However, the dashed lines and the separate box for Type and Size indicate that while there is a default value, it can be overridden. This means that the Size can be parameterized, thus allowing the creation of ClarusCollection instances 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.

Answer : C

In UML, profiles are mechanisms to extend the UML for a specific domain or purpose. The UML specification allows for one profile to reuse or import elements from another profile. This enables modularity and encourages reusability of profile elements across different domains. Additionally, one profile may extend the stereotypes or metaclasses defined in another profile, which allows for the creation of layered profiles where each layer adds its own specificities. This is a common practice in software and systems modeling to cater to different aspects of a system within separate profiles, which are then integrated to form a comprehensive model. The capability to reuse and extend profiles is defined in the UML 2.x Superstructure Specification, which gives guidelines on how to define and use profiles within UML.

Answer : C

In UML, a Dependency is a relationship that signifies that one NamedElement, the client, depends on another NamedElement, the supplier, meaning that a change in the supplier could affect the client. If NamedElement A is the supplier and NamedElement B is the client in a Dependency relationship, and there is a Comment indicating that both participate in a transformation, the interpretation is that B (the client) depends on A (the supplier) for that transformation. The comment does not necessarily change the nature of the Dependency relationship; it simply adds additional information about the nature of their interaction. A transformation could mean that B transforms A's supplied element in some way, but in terms of UML Dependency relationships, it would still be interpreted as 'A depends on B' or 'B requires A for its transformation'. This interpretation aligns with the UML 2.x Infrastructure and Superstructure specifications, which explain Dependencies and their meanings within the UML metamodel.

Answer : C

The UML diagram illustrates two types of reproduction for cattle: natural and assisted. In natural reproduction, a bull (xy) and a cow (xx) result in a new cattle (result), which aligns with biological principles. The same principle applies to assisted reproduction, where the donor is also cattle (xy), and the result is a new cattle. Since both Ferd Bull and Don Donor are specialized types of Cattle, and the result of both reproductions is Cattle, it implies that both xx and xy are of type Cattle, but within the context, xx is specifically a Cow. Therefore, xx is a Cow, xy is Cattle (which can be a Bull or Donor), and the result is also Cattle. This interpretation aligns with the principles of UML where specific instances (like Ferd Bull and Don Donor) are instances of the more general classifier Cattle.