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

In UML, the concept used to represent a model element such as a class or an activity is known as a Classifier. A Classifier in UML is a term that categorizes a group of model elements that have similar structural features, which include attributes and associations, and similar behavioral features, which include operations and methods1. The term applies not only to specific UML model elements but to all classifiers, encompassing a variety of elements such as classes, components, interfaces, and even activities1.

For instance, a class is a classifier because it describes a set of objects with similar properties (attributes), common behavior (operations), common relationships to other objects, and common semantics. An activity, which is a behavior, can also be considered a classifier because it describes a sequence of actions or flow of controland data1. Therefore, the correct answer is C. Classifier, as it is the overarching concept that includes both structural and behavioral elements within UML.

The scope of fUML (Foundational UML) is to define execution semantics for a subset of the UML 2 metamodel that provides a shared foundation for higher-level UML modeling concepts. This includes the precise definition of the execution semantics of that subset, which is intended to be used by a wide range of system types, including physically distributed and concurrent systems without assumptions about global synchronization1.

In UML, an InformationItem represents an abstraction of all those elements in a UML model that have an information-bearing feature. It is depicted as a classifier with the keyword «informationItem». An InformationItem does not have direct instances and serves as a mechanism to handle unspecified, untyped information in a model. In the context of a commercial transaction model, currencies such as euros, pesos, and dollars can be abstractly represented as InformationItems to signify that they are used as a form of data exchange but without specifying the concrete structure or data type. Figure 2 correctly uses InformationItem notation, with the «informationItem» keyword and the directed association pointing from the Currency InformationItem to the Euro, Peso, and Dollar, which are likely representations or manifestations of the Currency. This complies with the UML specification for representing abstract entities in models that are involved in the exchange or flow of information.