MARTE11 — Implied NFP constraint on stereotypes Assign and Allocate

Both stereotypes Assign and Allocate have a properties called impliedConstraint. Do we need this additional attribute because indeed a NfpConstraint being a extension of the UML constraint can be apply on any elements.
Or if we need, could these properties be derived?

The intent is to emphasize that allocations and assignments always come at
price and the costs should be made explicit by some NFP constraints. These
NFP constraints will then guide the architecture exploration, for instance. Of
course, constraints can be applied to anything but having an explicit association
is useful for traceability purpose.
If you allocation one element to two execution platforms, the costs may be
different and you need to know which constraint is imposed by which allocation.
Disposition: Closed, no change