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. From: "Bock, Conrad" To: "sysml-rtf@omg.org" Date: Fri, 26 Oct 2012 15:18:59 -0400 Subject: SysML Issue 16406, required stereotype, vendor poll Thread-Topic: SysML Issue 16406, required stereotype, vendor poll Thread-Index: Ac2zrsAUbQfMh2xST0urZZiVCyPCfg== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US SysML vendors, Can your implementation support this solution to issue 16406: http://tinyurl.com/boqscdf (long url below) in particular the use of required stereotypes? Please enter your answer at http://www.surveymonkey.com/s/BFFNB5N If the poll doesn't come up, empty your browser cache/cookies and try again. Thx, Conrad http://www.omg.org/members/sysml-rtf-wiki/lib/exe/fetch.php?id=rtf4%3Agroups%3Arelationship_dependencies%3Aindex&cache=cache&media=rtf4:groups:relationship_dependencies:16046_resolved_v1.0.doc Subject: Re: SysML Issue 16406, required stereotype, vendor poll From: Nerijus Jankevicius Date: Tue, 30 Oct 2012 16:49:36 +0200 Cc: "sysml-rtf@omg.org" To: "Bock, Conrad" X-Mailer: Apple Mail (2.1084) X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id q9UEo0KW028523 Conrad, Proposed resolution does not answer these questions: 1. Is it allowed to NOT serialize stereotype if all properties are derived? If not, problem is not solved. 2. if required stereotype is applied to EVERY SysML model element, does that mean it must be represented on every shape in applied stereotypes compartment? As I know, there is no such concept a "invisible stereotype" in UML/SysML. Also, required stereotype means we should double number of elements in memory, as every SysML element has linked stereotype instance. Of course we can cheat and do not create such stereotype instance in tool, but is it according the standard? Nerijus On Oct 26, 2012, at 10:18 PM, Bock, Conrad wrote: > SysML vendors, > > Can your implementation support this solution to issue 16406: > > http://tinyurl.com/boqscdf (long url below) > > in particular the use of required stereotypes? Please enter your answer > at > > http://www.surveymonkey.com/s/BFFNB5N > > If the poll doesn't come up, empty your browser cache/cookies and try > again. > > Thx, > > Conrad > > > http://www.omg.org/members/sysml-rtf-wiki/lib/exe/fetch.php?id=rtf4%3Agroups%3Arelationship_dependencies%3Aindex&cache=cache&media=rtf4:groups:relationship_dependencies:16046_resolved_v1.0.doc From: "Bock, Conrad" To: "sysml-rtf@omg.org" Date: Thu, 1 Nov 2012 08:36:21 -0400 Subject: RE: SysML Issue 16406, required stereotype, vendor poll Thread-Topic: SysML Issue 16406, required stereotype, vendor poll Thread-Index: Ac24LX9AvhWU01PnSAiGaRf/mLZkfQ== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Reminder to SysML vendors about this. Silence might be taken as assent! Conrad -----Original Message----- From: Bock, Conrad Sent: Friday, October 26, 2012 3:19 PM To: sysml-rtf@omg.org Subject: SysML Issue 16406, required stereotype, vendor poll SysML vendors, Can your implementation support this solution to issue 16406: http://tinyurl.com/boqscdf (long url below) in particular the use of required stereotypes? Please enter your answer at http://www.surveymonkey.com/s/BFFNB5N If the poll doesn't come up, empty your browser cache/cookies and try again. Thx, Conrad http://www.omg.org/members/sysml-rtf-wiki/lib/exe/fetch.php?id=rtf4%3Agroups%3Arelationship_dependencies%3Aindex&cache=cache&media=rtf4:groups:relationship_dependencies:16046_resolved_v1.0.doc From: "Bock, Conrad" To: "sysml-rtf@omg.org" Date: Thu, 1 Nov 2012 08:58:54 -0400 Subject: RE: SysML Issue 16406, required stereotype, vendor poll Thread-Topic: SysML Issue 16406, required stereotype, vendor poll Thread-Index: Ac24MFiq08g+Y9bDTuS2hvMu8k6+XA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Nerijus, Thanks for the questions. I forwarded the first two with rewording to the UML FTF. > Also, required stereotype means we should double number of elements > in memory, as every SysML element has linked stereotype instance. > Of course we can cheat and do not create such stereotype instance in > tool, but is it according the standard? Tools can implement any internal optimizations they like as long as it behaves as if the stereotypes are applied. For example, the user should be able to get the values of derived properties. Conrad From: "Bock, Conrad" To: "sysml-rtf@omg.org" Date: Thu, 1 Nov 2012 16:23:05 -0400 Subject: RE: SysML Issue 16406, required stereotype, vendor poll, stereotype questions Thread-Topic: SysML Issue 16406, required stereotype, vendor poll, stereotype questions Thread-Index: Ac24blkDrD0hHvNaRMO5l9saz1MePA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Nerijus, If Pete is correct below, the answers to your other two questions are: > 1. Is it allowed to NOT serialize stereotype if all properties are > derived? If not, problem is not solved. No. Seems like a reasonable request that required stereotypes not be serialized in this case, but it would introduce a special case into the interchange. > 2. if required stereotype is applied to EVERY SysML model element, > does that mean it must be represented on every shape in applied > stereotypes compartment? No. Does this change your answers to the poll? If so, you can answer again at http://www.surveymonkey.com/s/BFFNB5N. It has a comment field if needed. If the poll doesn't come up, empty your browser cache/cookies and try again. Conrad -----Original Message----- From: Pete Rivett [mailto:pete.rivett@adaptive.com] Sent: Thursday, November 01, 2012 10:11 AM To: Bock, Conrad; uml25-ftf@omg.org Subject: RE: Stereotype questions My takes (I can supply spec references if really needed but have too much on my plate right now)... 1. No: it's the only way to indicate that the stereotype has been applied. And no, stereotypes cannot be considered to be implicitly applied even if the stereotype is required. 2. Yes in general stereotypes can be elided. But no if their properties are displayed. For example if a compartment represents properties for a stereotype it is not allowed (and does not make sense) to elide the stereotype name. Likewise for any display of properties (in name string or comment symbol) Assuming the preference would be the opposite to my responses, MEF will of course allow this to be a lot more achievable. I suggest SysML focus on that rather than trying to take UML to places it was never designed to go. Cheers, Pete -----Original Message----- From: Bock, Conrad [mailto:conrad.bock@nist.gov] Sent: Thursday, November 01, 2012 5:53 AM To: uml25-ftf@omg.org Subject: Stereotype questions UMLers, The SysML RTF has some questions about stereotypes (forwarded from Nerijus with rewording): 1. Is it allowed to NOT serialize stereotype instances if all properties are derived? 2. Can applied stereotypes be elided from diagrams (in particular from compartments)? Conrad