Issue 17549: ControlOperator stereotype should also extend the CallBehaviorAction metaclass (sysml-rtf)
Source: Lockheed Martin (Mr. Lenny Delligatti, lenny_delligatti2(at)omg.org)
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: <issues@omg.org>
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.