The correct answer is C, which uses a transformation edge to indicate that when an order is closed, information is transformed or processed to notify the customer. This is expressed in UML with an object flow that has a transformation property, which specifies how an object is transformed from one state to another as it flows along the edge. This is appropriate for a scenario where closing an order leads to the creation of a customer notice, implying some form of transformation or processing of the order information to generate the notice.

References:

UML 2.5 Specification : The UML 2.5 specification details how object flows with transformations can be used to show that one piece of data is transformed into another as it flows from one action to another.

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.

A coregion in a UML Sequence Diagram is a notation that:

A. Incorrect, as interactions are behavioral units that can involve multiple lifelines and are not specific to a coregion.

B. Incorrect, as combined fragments are constructs that control flow with interaction operands, not directly related to a coregion.

C. Correct. A coregion is a shorthand notation for a parallel combined fragment on a single lifeline. It allows for the representation of parallel behavior within a single lifeline.

D. Incorrect, as the area between lifelines for communication is not what defines a coregion.

References:

UML Specification: Sequence Diagrams section, specifically about coregion and combined fragments.

The concept and usage of coregions in sequence diagrams are further elaborated in the UML 2.5 Documentation, under the Sequence Diagrams section.

The Profile mechanism in UML provides the capability to adapt existing metamodel elements for specific purposes. Profiles allow modelers to extend the standard UML metamodel with additional semantics by defining stereotypes, tagged values, and constraints that are specific to a particular domain, platform, or methodology. This means that profiles tailor the existing UML metamodel elements to create domain-specific models without changing the underlying metamodel itself. This adaptation mechanism is described in the UML 2.x Superstructure and Infrastructure Specifications, which detail how profiles can be used to customize the UML for particular domains or purposes.

The correct answer is B, which uses a selection edge to specify task behavior based on task priority. In UML, an object flow with a selection property is used to select objects from a collection according to some criterion, which is typically represented by a Boolean expression. In the case of B, the selection criterion is described as "ordering = the most important first", indicating that tasks are selected to be executed based on their priority.

References:

UML 2.5 Specification : The UML 2.5 specification describes how selection behaviors can be applied to object flows to filter objects according to specific criteria, such as priority in this scenario.

The semantics of MOF elements are typically provided in the specification as natural language descriptions 1 . This approach allows for a clear and understandable explanation of the elements and their intended use within the framework.

The approach described in option B aligns with the concept of template classifiers in UML, which allows for the creation of parameterized elements that can be instantiated with different arguments. By modeling Vehicle as a template classifier with a parameter named Thrustor , other modelers can instantiate this template with their chosen propulsion system, as long as it is a type that specializes the PropulsionSystem abstract class. This method provides the flexibility needed for modelers to tailor the Vehicle class to different propulsion systems while enforcing that only derivatives of PropulsionSystem can be used as the actual parameter for Thrustor . This tactic of using template classifiers and class parameters is an application of UML's syntax and semantics for creating modular and customizable models. This practice is detailed in the UML 2.x Superstructure Specification, particularly in the sections describing template classifiers and their parameters.