UMLR — UML2.5 issue: constraints needed in model of Standard Profile

Issue 15144 pointed out a lot of flaws in the modeling of standard profiles. Some of those flaws involved the absence of constraints. To help manage the process, I’m raising a separate issue that just lists the constraints that are needed. They ought to be OCL in the profile.

The client and supplier of Usages stereotyped by Call must be Operations.

The client and supplier of Usages stereotyped by Create must be Classifiers.

Realization and ImplementationClass may not both be applied to the same element.

Specification and Type may not both be applied to the same element.

The clients of Usages stereotyped by Send must be Operations, and the suppliers must be Signals.