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

A stereotype in UML is a powerful extension mechanism that allows developers to tailor UML models for particular domains or platforms. Stereotypes can adapt UML model elements by adding constraints, changing notation, and adding attributes and operations. However, they cannot remove existing constraints from a model element12.

• Notation Change (A): Stereotypes can indeed change the notation of a model element to make it more expressive or domain-specific. For example, a stereotype could be used to visually distinguish between different kinds of classes in a class diagram1.
• Adding Constraints (B): Stereotypes can add new constraints to a model element to specify additional rules or requirements that are not defined by the standard UML1.
• Removing Constraints ©: This is not a capability of stereotypes. Constraints define rules that must be followed, and once they are part of a model element, they cannot be removed by a stereotype. Instead, they are an intrinsic part of the model’s definition1.
• Adding Attributes and Operations (D): Stereotypes can be used to add attributes and operations to a model element, which allows for the specification of additional properties or behaviors that are not part of the standard UML metamodel1.

In summary, while stereotypes are versatile and can extend the capabilities of UML model elements in various ways, they do not have the ability to remove constraints that are already applied to those elements. This is because constraints are consideredfundamental rules that govern the integrity of the model, and removing them would potentially violate the model’s correctness or completeness1.

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.

The UML (Unified Modeling Language) specification, which is a part of the MOF (Meta-Object Facility) framework, suggests that the choice between creating a MOF-based metamodel and a UML profile depends on the specific needs of the domain being modeled. A MOF-based metamodel might be more appropriate for domains that require defining a completely new set of modeling concepts, whereas a UML profile is suitable for domains where the extension ofexisting UML concepts is sufficient. Since the specification recognizes the variability in modeling requirements across different domains, it emphasizes the importance of understanding the domain to make an informed decision on the modeling approach. The UML specification, therefore, does not prescribe a one-size-fits-all solution but rather leaves the decision to the modeler, based on the domain-specific requirements.