Issue 14842: Implied NFP constraint on stereotypes Assign and Allocate (marte-rtf) Source: Commissariat a l Energie Atomique-CEA (Dr. Sebastien Gerard, sebastien.gerard(at)cea.fr) Nature: Clarification Severity: Minor Summary: 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? Resolution: 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 Revised Text: Actions taken: December 8, 2009: received issue January 14, 2011: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 08 Dec 2009 14:17:25 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Sebastien Gerard Company: CEA LIST mailFrom: sebastien.gerard@cea.fr Notification: Yes Specification: MARTE Section: Allocation FormalNumber: formal/2009-11-02 Version: 1.0 RevisionDate: 11-02-2009 Page: 135&136 Title: Implied NFP constraint on stereotypes Assign and Allocate Nature: Clarification Severity: Minor test: 3qw8 B1: Report Issue Description: 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?