OMG-OCUP2-ADV300 Exam Questions

In Option C, the properties suitable road surface and average speed have been redefined in the subclasses Recumbent Bike and Racing 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 superclass Bicycle. This is the correct way to enforce that each specialization of Bicycle has 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.

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.

The diagram depicts Electronic Device Kind as a class that requires a set of Certifications (required : Certification[1..*]). This implies that any subclass of Electronic Device Kind must provide a set of required Certifications because the multiplicity [1..*] indicates that at least one Certification is mandatory for each instance of Electronic Device Kind or its subclasses. Therefore, when a subclass is created, it inherits the requirement to specify what Certifications are needed. This is a standard UML generalization, where the subclass inherits the attributes and constraints of its superclass. This interpretation is consistent with the rules defined in the UML 2.x Superstructure Specification, which includes the semantics of class generalization and attribute inheritance.

The UML diagram fragment provided shows a UML profile with a required extension from the metaclass Class to the stereotype DisplayArea, which in turn has two subclasses Frame and Form. The use of {required} indicates that whenever an instance of Class is extended by the DisplayArea stereotype, it becomes mandatory to do so. However, this does not enforce that every instance of Class must be linked to DisplayArea or its subclasses (Frame or Form). It only means that if the DisplayArea stereotype is applied, it is required. Therefore, there is no obligation for every instance of Class or its subclasses to be stereotyped as DisplayArea, Frame, or Form. It's also worth noting that the last option (E) could be considered true in some interpretations of UML, but given the options provided and common UML practices, option D is more accurate.

In UML, a simple State can indeed be redefined, but the specifics of how it is redefined matter:

A is incorrect as redefinition of States, including simple States, is permitted.

B is correct. A simple State can be effectively removed or altered through redefinition in a derived StateMachine, which could include changing its type or characteristics.

C suggests that a simple State can be turned into a composite State. While theoretically possible in the context of redefinition, this option might be considered a significant alteration that could be misleading without additional context.

D is incorrect; UML does support State Redefinition.

UML Specification, particularly the sections on Redefinition and StateMachines.

Detailed rules on state redefinition are outlined in the UML 2.5 Documentation, specifically under StateMachine specializations.