Issue 16406: Rate does not support the examples (sysml-rtf) Source: NASA (Dr. Nicolas F. Rouquette, nicolas.f.rouquette(at)jpl.nasa.gov) Nature: Uncategorized Issue Severity: Summary: There is an inconsistency w.r.t. the definition of SysML Rate with the notation & examples. According to figure 11.8, SysML Rate extends only 2 metaclasses: Parameter and ActivityEdge. By generalization, SysML Continuous and Discrete also extend these two metaclasses. According to the notation in Table 11.1, <<rate>>, <<continuous>> and <<discrete>> also apply to ObjectNodes. The examples in figure B.33 and B.35 show applications of <<continuous>> to CentralBufferNodes and ActivityParameterNodes, both are direct specializations of ObjectNode. Some examples in the Practical Guide to SysML do the same -- see figure 8.17 on p. 196; figure 15.14 on p. 373 Both SysML 1.2 Figure 11.8 and the published profile http://www.omg.org/spec/SysML/20100301/SysML-profile.uml are incomplete. The resolution is fairly simple: Add an extension from Rate to ObjectNode in figure 11.8 and update the SysML profile accordingly. I propose to include this resolution in ballot 5 for sysml 1.3. Resolution: Revised Text: Actions taken: July 30, 2011: received issue Discussion: End of Annotations:===== m: "Rouquette, Nicolas F (313K)" To: "issues@omg.org" CC: "sysml-rtf@omg.org" Date: Sat, 30 Jul 2011 15:37:42 -0700 Subject: SysML 1.2 definition of Rate in Figure 11.8 is inconsistent with notation (Table 11.1) and usage examples (Figures B.33, B.35) Thread-Topic: SysML 1.2 definition of Rate in Figure 11.8 is inconsistent with notation (Table 11.1) and usage examples (Figures B.33, B.35) Thread-Index: AcxPCWJD4V75vYM3SqqW59edlyJNNw== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Source-IP: altvirehtstap01.jpl.nasa.gov [128.149.137.72] X-Source-Sender: nicolas.f.rouquette@jpl.nasa.gov X-AUTH: Authorized There is an inconsistency w.r.t. the definition of SysML Rate with the notation & examples. According to figure 11.8, SysML Rate extends only 2 metaclasses: Parameter and ActivityEdge. By generalization, SysML Continuous and Discrete also extend these two metaclasses. According to the notation in Table 11.1, <>, <> and <> also apply to ObjectNodes. The examples in figure B.33 and B.35 show applications of <> to CentralBufferNodes and ActivityParameterNodes, both are direct specializations of ObjectNode. Some examples in the Practical Guide to SysML do the same -- see figure 8.17 on p. 196; figure 15.14 on p. 373 Both SysML 1.2 Figure 11.8 and the published profile http://www.omg.org/spec/SysML/20100301/SysML-profile.uml are incomplete. The resolution is fairly simple: Add an extension from Rate to ObjectNode in figure 11.8 and update the SysML profile accordingly. I propose to include this resolution in ballot 5 for sysml 1.3. - Nicolas. From: "Rouquette, Nicolas F (313K)" To: "Bock, Conrad" CC: "sysml-rtf@omg.org" Date: Sun, 31 Jul 2011 12:36:09 -0700 Subject: Re: SysML 1.2 definition of Rate in Figure 11.8 is inconsistent with notation (Table 11.1) and usage examples (Figures B.33, B.35) Thread-Topic: SysML 1.2 definition of Rate in Figure 11.8 is inconsistent with notation (Table 11.1) and usage examples (Figures B.33, B.35) Thread-Index: AcxPuTE8ohYziQuqRheDNpTvFIsfxA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Source-IP: altvirehtstap02.jpl.nasa.gov [128.149.137.73] X-Source-Sender: nicolas.f.rouquette@jpl.nasa.gov X-AUTH: Authorized Conrad, The semantics of streaming parameters and edges is incomplete as described in 11.3.2.8 Rate: When the Ğrateğ stereotype is applied to an activity edge, it specifies the expected value of the number of objects and values that traverse the edge per time interval, that is, the expected value rate at which they leave the source node and arrive at the target node. Shouldn't the source/target nodes be streaming as well? When the stereotype is applied to a parameter, the parameter must be streaming, and the stereotype gives the number of objects or values that flow in or out of the parameter per time interval while the behavior or operation is executing. Streaming is a characteristic of UML behavior parameters that supports the input and output of items while a behavior is executing, rather than only when the behavior starts and stops. When the behavior is an activity, the streaming parameter has a corresponding activity parameter node -- ActivityParameterNode::parameter : Parameter[1]. Shouldn't the activity parameter node corresponding to a streaming activity behavior parameter be streaming as well? Making SysML's Rate extend UML's ObjectNode would help fill the gap in the semantics of streaming parameters and edges to include the streaming semantics of edge source/target nodes and the streaming semantics of activity parameter nodes corresponding to streaming activity behavior parameters. All of the tool vendors who have successfully participated in MIWG TestCase 12a clearly have implemented SysML 1.2 with the described fix: http://www.omgwiki.org/model-interchange/doku.php?id=test_case_12a WIthout the proposed fix, the above test case and the examples in the sysml spec will remain as ill-formed in sysml 1.3 as they were in sysml 1.2 and 1.1 - Nicolas. On Jul 31, 2011, at 6:25 AM, Bock, Conrad wrote: Nicolas, According to figure 11.8, SysML Rate extends only 2 metaclasses: Parameter and ActivityEdge. By generalization, SysML Continuous and Discrete also extend these two metaclasses. According to the notation in Table 11.1, <>, <> and <> also apply to ObjectNodes. The examples in figure B.33 and B.35 show applications of <> to CentralBufferNodes and ActivityParameterNodes, both are direct specializations of ObjectNode. Some examples in the Practical Guide to SysML do the same -- see figure 8.17 on p. 196; figure 15.14 on p. 373 Don't fix this, just file and defer. The semantics for rate is only given for streaming parameters and edges. Will straighten things out in v.1.3. Conrad :wq From: "Bock, Conrad" To: "sysml-rtf@omg.org" Date: Thu, 26 Jul 2012 09:14:19 -0400 Subject: RE: draft ballot 2 available for discussion through Friday, August 3, 2012, 16406 Thread-Topic: draft ballot 2 available for discussion through Friday, August 3, 2012, 16406 Thread-Index: Ac1rMIbJmNOXWjIAT7GAi+XcCtCyMA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Nicolas, > Therefore, I propose resolving 16406 by explaining in the spec that Fig C.33 > & C.35 use the alternative object flow notation. Good idea, thx.