Issue 17562: N-ary Allocation needs better definition, or deletion (sysml-rtf) Source: Raytheon (Mr. Frederick A. Steiner, fsteiner(at)raytheon.com) Nature: Clarification Severity: Significant Summary: An unnumbered constraint on the Allocate relationship states: "A single «allocate» dependency shall have only one client (from), but may have one or many suppliers (to)." The use or meaning of this n-ary relationship is not described. An informal survey of RTF members indicated that this n-ary allocation capability has not been implemented in any tool, nor has it been used by practitioners. Note that Satisfy relationship (see 16.3.2.6) serves a similar purpose to Allocate, but does not require an n-ary implementation. Removal of the n-ary requirement on Allocate would simplify efforts to unify SysML relationship dependencies. This requirement should either be 1) rationalized, elaborated and applied consistently across similar SysML relationships, or 2) deleted to facilitate ongoing SysML improvements. Resolution: Revised Text: Actions taken: August 23, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 23 Aug 2012 13:24:53 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Rick Steiner Employer: Raytheon mailFrom: fsteiner@raytheon.com Terms_Agreement: I agree Specification: OMG SysML Section: 15.2.3.1 FormalNumber: formal/2012-06-01 Version: 1.3 Doc_Year: 2012 Doc_Month: June Doc_Day: Day Page: 133 Title: N-ary Allocation needs better definition, or deletion Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Description: An unnumbered constraint on the Allocate relationship states: "A single «allocate» dependency shall have only one client (from), but may have one or many suppliers (to)." The use or meaning of this n-ary relationship is not described. An informal survey of RTF members indicated that this n-ary allocation capability has not been implemented in any tool, nor has it been used by practitioners. Note that Satisfy relationship (see 16.3.2.6) serves a similar purpose to Allocate, but does not require an n-ary implementation. Removal of the n-ary requirement on Allocate would simplify efforts to unify SysML relationship dependencies. This requirement should either be 1) rationalized, elaborated and applied consistently across similar SysML relationships, or 2) deleted to facilitate ongoing SysML improvements.