Issue 17549: ControlOperator stereotype should also extend the CallBehaviorAction metaclass (sysml-rtf) Source: Lockheed Martin (Mr. Lenny Delligatti, lenny.delligatti(at)lmco.com) Nature: Revision Severity: Significant Summary: Table 11.1 on pg. 93 shows that the «controlOperator» stereotype can be applied to a call behavior action (when that call behavior action calls an activity that also has the «controlOperator» stereotype applied). However, the metamodel fragment on pg. 104 and the stereotype description on pg. 105 do not support that. Currently the spec. states that SysML::ControlOperator only extends UML4SysML::Behavior and UML4SysML::Operation, not UML4SysML::CallBehaviorAction. This would be appropriate, though, and seems to be in keeping with the original intent of the SysML Development Team given that it appears in Table 11.1 Proposed Resolution: Add another extension relationship from SysML::ControlOperator to UML4SysML::CallBehaviorAction. Resolution: Revised Text: Actions taken: August 10, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 10 Aug 2012 11:48:21 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Lenny Delligatti Employer: Lockheed Martin mailFrom: lenny.delligatti@lmco.com Terms_Agreement: I agree Specification: SysML Section: 11.3.2.2 FormalNumber: formal/2012-06-01 Version: 1.3 Doc_Year: 2012 Doc_Month: June Doc_Day: 01 Page: 93, 104-105 Title: ControlOperator stereotype should also extend the CallBehaviorAction metaclass Nature: Revision Severity: Significant CODE: 3TMw8 B1: Report Issue Description: Table 11.1 on pg. 93 shows that the «controlOperator» stereotype can be applied to a call behavior action (when that call behavior action calls an activity that also has the «controlOperator» stereotype applied). However, the metamodel fragment on pg. 104 and the stereotype description on pg. 105 do not support that. Currently the spec. states that SysML::ControlOperator only extends UML4SysML::Behavior and UML4SysML::Operation, not UML4SysML::CallBehaviorAction. This would be appropriate, though, and seems to be in keeping with the original intent of the SysML Development Team given that it appears in Table 11.1 Proposed Resolution: Add another extension relationship from SysML::ControlOperator to UML4SysML::CallBehaviorAction. From: "BERNARD, Yves" To: "Sysml-Rtf (sysml-rtf@omg.org)" Date: Thu, 15 Nov 2012 09:10:23 +0100 Subject: [Ballot 3] #17549 ControlOperator should extend CallBehaviorAction Thread-Topic: [Ballot 3] #17549 ControlOperator should extend CallBehaviorAction Thread-Index: Ac3DCKmYLFWWVl6NQO6s/rMAKEYmJw== Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US This issue is not a duplicate of #16046: .Rate does not support the examples. Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: "Bock, Conrad" To: "Sysml-Rtf (sysml-rtf@omg.org)" Date: Thu, 15 Nov 2012 09:06:49 -0500 Subject: RE: [Ballot 3] #17549 ControlOperator should extend CallBehaviorAction Thread-Topic: [Ballot 3] #17549 ControlOperator should extend CallBehaviorAction Thread-Index: Ac3DCKmYLFWWVl6NQO6s/rMAKEYmJwALgE0g Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Yves, > This issue is not a duplicate of #16046: "Rate does not support the examples" Yes, this is a "merge", the issue is about the same thing as 16046.