Issue 15075: Including Property Notation for Redefinition and Subsetting (sysml-rtf) Source: INCOSE (Mr. Sanford A. Friedenthal, safriedenthal(at)gmail.com) Nature: Clarification Severity: Significant Summary: The property notation from UML to support redefinition and subsetting should be included in SysML explicitly. This notation is not currently included in the diagram element tables in the Blocks Chapter. Refer to property notation in Section 7.3.44 of the Superstructure Specification (v2.3). Resolution: Revised Text: Actions taken: February 20, 2010: received issue Discussion: This issue is being deferred because no proposed resolution was voted on during the schedule of the SysML 1.3 RTF. Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 20 Feb 2010 14:42:42 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Sanford Friedenthal Company: Lockheed Martin mailFrom: sanford.friedenthal@lmco.com Notification: Yes Specification: SysML Section: 8.2.1 FormalNumber: formal/2008-11-02 Version: 1.1 RevisionDate: Nov 2008 Page: 32-35 Title: Including Property Notation for Redefinition and Subsetting Nature: Clarification Severity: Significant test: 3qw8 B1: Report Issue Description: From: Burkhart Roger M To: Sanford Friedenthal , "sysml-rtf@omg.org" Date: Sun, 22 Jul 2012 19:53:58 -0500 Subject: RE: Comments and Proposed Updates to: draft ballot 2 available for discussion through Friday, August 3, 2012 Thread-Topic: Comments and Proposed Updates to: draft ballot 2 available for discussion through Friday, August 3, 2012 Thread-Index: Ac1mtZGhFXy2219yTAO8Wn3juoG66gAi/mMgAEpGC/AAALxcEA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.260,0.0.0000 definitions=2012-07-22_06:2012-07-20,2012-07-22,1970-01-01 signatures=0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.260,0.0.0000 definitions=2012-07-22_06:2012-07-20,2012-07-22,1970-01-01 signatures=0 Sandy-- On Issue 17246, my resolution had already proposed to keep the current first sentence of the paragraph in question ("It is common practice for systems engineers to use a wide range of modeling languages, tools, and techniques on large systems projects.") I'm OK with your new version, however, including making the first sentence for engineers in general, and your single sentence to follow ("As a general purpose modeling language, SysML is intended to be used with a diverse set of discipline and domain specific modeling languages.") On Issue 17307, thanks for the catch that my editing instructions hadn't removed the old sentence now subsumed by the new. I'll fix it in the next update. On Issue 15075 ("Including Property Notation for Redefinition and Subsetting"), I didn't try to address it in this ballot. This ballot was to include only resolutions we expect to be non-controversial, and I don't know whether that one will be or not. I'd prefer to go one step at a time, and postpone any further consideration on that additional issue until after we finish this ballot. --Roger From: Sanford Friedenthal [mailto:safriedenthal@gmail.com] Sent: Saturday, July 21, 2012 9:23 AM To: sysml-rtf@omg.org Subject: Comments and Proposed Updates to: draft ballot 2 available for discussion through Friday, August 3, 2012 SysML RTF I have included the following comments and proposed updates to the resolutions per below. Thanks. Sandy Issue 17246 Part 1, 4th paragraph Current text: It is common practice for systems engineers to use a wide range of modeling languages, tools, and techniques on large systems projects. In a manner similar to how UML unified the modeling languages used in the software industry, SysML is intended to unify the diverse modeling languages currently used by systems engineers. Text in proposed resolution: The SysML language is intended to provide a common systems engineering context which can be integrated with the diverse modeling languages used by systems engineers. Contents of additional modeling languages, tools, and techniques can be mapped into a SysML systems model for use across the systems development life cycle. Suggested modified text in proposed resolution: (modifications in strikethrough and yellow highlighted text) It is common practice for systems engineers to use a wide range of modeling languages, tools, and techniques on large systems projects. As a general purpose modeling language, SysML is intended to be used with a diverse set of discipline and domain specific modeling languages. In a manner similar to how UML unified the modeling languages used in the software industry, SysML is intended to unify the diverse modeling languages currently used by systems engineers. Issue 17307 In addition to the proposed text change, suggest you also delete the sentence in the current text that is highlighted below since it is subsumed in the proposed modified text. Current text: A property typed by a SysML Block that has composite aggregation is classified as a part property, except for the special case of a constraint property. Constraint properties are further defined in Clause 10, .Constraint Blocks.. A port is another category of property, as further defined in Clause 9, .Ports and Flows.. Suggested modified text in proposed resolution: (modifications in strikethrough and yellow highlighted text) A property typed by a SysML Block that has composite aggregation is classified as a part property, except for the special cases of ports and constraint properties. Ports are further defined in Clause 9, .Ports and Flows,. and constraint properties are further defined in Clause 10, .Constraint Blocks.. A port is another category of property, as further defined in Clause 9, .Ports and Flows. Issue 17120 While we address the addition of the derived property notation to blocks, this seems like a good time to address another somewhat related issue 25075 to include redefinition and subsetting in the table. If it is too late to address in this ballot, please address .Issue 15075: Including Property Notation for Redefinition and Subsetting. in next ballot. Issue 17250 Suggest we add the operations label to the compartment to be consistent with the block notation in Table 8.2.1. Although it may be ok not to include a compartment label, we should encourage consistent use of the notation in the specification to avoid confusion. Issue 13153 I don.t understand the motivation for adding an additional action stereotype called ReadExecution. Shouldn.t this be something that should be done in UML? Issue 16406 The resolution of this issue on the rate stereotype refers to Issue 13153. I don.t see how the proposed resolution to Issue 13153 addresses this issue. Issue 15302 The create message should be a dashed line in the figure as indicated in the statement of the issue. Issue 17445 This resolution proposes adding some existing state machine notation to the diagram tables. Adding the composite notation is good since this is pretty intuitive and standard. I am questioning whether adding the connection point reference notation (via .)is sufficiently used and intuitive to warrant adding to SysML notation tables. Can we include this separately so it can be voted on separately. From: Burkhart Roger M [mailto:BurkhartRogerM@JohnDeere.com] Sent: Friday, July 20, 2012 4:24 PM To: sysml-rtf@omg.org Subject: draft ballot 2 available for discussion through Friday, August 3, 2012 A draft Ballot 2 is available for review and discussion on the SysML 1.4 RTF wiki at http://www.omg.org/members/sysml-rtf-wiki. (Click on the Ballot 2 link.) Ballot 2 will be open for discussion through Friday, August 3, 2012. The normal two-week voting period will then begin by Monday, August 6. Following are ballot review instructions which appear at the bottom of the ballot page: The review period is currently open. Please download the PDF file above to review the detail of the proposed resolutions, which will be frozen at the start of voting. If you have any concerns or questions about any of the proposed resolutions, please send a message to the sysml-rtf@omg.org mailing list. This ballot is intended to continue our cleanup of (relatively) easily disposed issues, picking up where ballot 1 left off. These resolutions are intended to be noncontroversial. If significant debate or discussion is raised during the review period, we will likely remove those resolutions from ballot 2 prior to voting. A review and discussion of this ballot will occur on the regularly scheduled RTF telecon on Thursday, July 26, 2012 at 10:00 ET, and in any subsequent telecons as required. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:x-mailer:content-language:thread-index; bh=au21/ibCDn7oGmTP63/4rXm15VzBARGzVogtHNkhfAk=; b=P6CzxkvvPoBds0b3BOrTly1DCpVMHegf+Rgby6WqiVQQRXJU6qeMJVnqbNzX8c3nWB zEVKfn0G0MSH2IP/aNoqYqgDjd8AfTDrkMfAPqfzkT5V10FIhZMozuuPCq1/EJBvwmMU IxDyLuKDCAIBL5vd580XzTSb87c1QOOSlDAJKuWBeMGDuXgXbs+K+tvcZD/AviZOuGHG r7TA7ZCjlpO12L51i0au+CuRmYUbE7wOg35MG/bCvKzOhVRNd/rPXSFXKs7JdXZHSNMS drExvmGMICdysFN/DNav3+EtY8VP/4pl2z0dJ9Vmha6kBg0RBMtvZJOu1Ct2GxFixtur 0pEQ== From: "Sanford Friedenthal" To: "'Burkhart Roger M'" , Subject: RE: Comments and Proposed Updates to: draft ballot 2 available for discussion through Friday, August 3, 2012 Date: Sun, 22 Jul 2012 21:46:03 -0400 X-Mailer: Microsoft Office Outlook 12.0 Thread-index: Ac1mtZGhFXy2219yTAO8Wn3juoG66gAi/mMgAEpGC/AAALxcEAAByiLQ Roger, Thank you for the response. Please include the proposed resolution to include property notation for redefinition and subsetting on the next ballot. This is particularly important for variant modeling. Thank you. Sandy From: Burkhart Roger M [mailto:BurkhartRogerM@JohnDeere.com] Sent: Sunday, July 22, 2012 8:54 PM To: Sanford Friedenthal; sysml-rtf@omg.org Subject: RE: Comments and Proposed Updates to: draft ballot 2 available for discussion through Friday, August 3, 2012 Sandy-- On Issue 17246, my resolution had already proposed to keep the current first sentence of the paragraph in question ("It is common practice for systems engineers to use a wide range of modeling languages, tools, and techniques on large systems projects.") I'm OK with your new version, however, including making the first sentence for engineers in general, and your single sentence to follow ("As a general purpose modeling language, SysML is intended to be used with a diverse set of discipline and domain specific modeling languages.") On Issue 17307, thanks for the catch that my editing instructions hadn't removed the old sentence now subsumed by the new. I'll fix it in the next update. On Issue 15075 ("Including Property Notation for Redefinition and Subsetting"), I didn't try to address it in this ballot. This ballot was to include only resolutions we expect to be non-controversial, and I don't know whether that one will be or not. I'd prefer to go one step at a time, and postpone any further consideration on that additional issue until after we finish this ballot. --Roger From: Sanford Friedenthal [mailto:safriedenthal@gmail.com] Sent: Saturday, July 21, 2012 9:23 AM To: sysml-rtf@omg.org Subject: Comments and Proposed Updates to: draft ballot 2 available for discussion through Friday, August 3, 2012 SysML RTF I have included the following comments and proposed updates to the resolutions per below. Thanks. Sandy Issue 17246 Part 1, 4th paragraph Current text: It is common practice for systems engineers to use a wide range of modeling languages, tools, and techniques on large systems projects. In a manner similar to how UML unified the modeling languages used in the software industry, SysML is intended to unify the diverse modeling languages currently used by systems engineers. Text in proposed resolution: The SysML language is intended to provide a common systems engineering context which can be integrated with the diverse modeling languages used by systems engineers. Contents of additional modeling languages, tools, and techniques can be mapped into a SysML systems model for use across the systems development life cycle. Suggested modified text in proposed resolution: (modifications in strikethrough and yellow highlighted text) It is common practice for systems engineers to use a wide range of modeling languages, tools, and techniques on large systems projects. As a general purpose modeling language, SysML is intended to be used with a diverse set of discipline and domain specific modeling languages. In a manner similar to how UML unified the modeling languages used in the software industry, SysML is intended to unify the diverse modeling languages currently used by systems engineers. Issue 17307 In addition to the proposed text change, suggest you also delete the sentence in the current text that is highlighted below since it is subsumed in the proposed modified text. Current text: A property typed by a SysML Block that has composite aggregation is classified as a part property, except for the special case of a constraint property. Constraint properties are further defined in Clause 10, .Constraint Blocks.. A port is another category of property, as further defined in Clause 9, .Ports and Flows.. Suggested modified text in proposed resolution: (modifications in strikethrough and yellow highlighted text) A property typed by a SysML Block that has composite aggregation is classified as a part property, except for the special cases of ports and constraint properties. Ports are further defined in Clause 9, .Ports and Flows,. and constraint properties are further defined in Clause 10, .Constraint Blocks.. A port is another category of property, as further defined in Clause 9, .Ports and Flows. Issue 17120 While we address the addition of the derived property notation to blocks, this seems like a good time to address another somewhat related issue 25075 to include redefinition and subsetting in the table. If it is too late to address in this ballot, please address .Issue 15075: Including Property Notation for Redefinition and Subsetting. in next ballot. Issue 17250 Suggest we add the operations label to the compartment to be consistent with the block notation in Table 8.2.1. Although it may be ok not to include a compartment label, we should encourage consistent use of the notation in the specification to avoid confusion. Issue 13153 I don.t understand the motivation for adding an additional action stereotype called ReadExecution. Shouldn.t this be something that should be done in UML? Issue 16406 The resolution of this issue on the rate stereotype refers to Issue 13153. I don.t see how the proposed resolution to Issue 13153 addresses this issue. Issue 15302 The create message should be a dashed line in the figure as indicated in the statement of the issue. Issue 17445 This resolution proposes adding some existing state machine notation to the diagram tables. Adding the composite notation is good since this is pretty intuitive and standard. I am questioning whether adding the connection point reference notation (via .)is sufficiently used and intuitive to warrant adding to SysML notation tables. Can we include this separately so it can be voted on separately. From: Burkhart Roger M [mailto:BurkhartRogerM@JohnDeere.com] Sent: Friday, July 20, 2012 4:24 PM To: sysml-rtf@omg.org Subject: draft ballot 2 available for discussion through Friday, August 3, 2012 A draft Ballot 2 is available for review and discussion on the SysML 1.4 RTF wiki at http://www.omg.org/members/sysml-rtf-wiki. (Click on the Ballot 2 link.) Ballot 2 will be open for discussion through Friday, August 3, 2012. The normal two-week voting period will then begin by Monday, August 6. Following are ballot review instructions which appear at the bottom of the ballot page: The review period is currently open. Please download the PDF file above to review the detail of the proposed resolutions, which will be frozen at the start of voting. If you have any concerns or questions about any of the proposed resolutions, please send a message to the sysml-rtf@omg.org mailing list. This ballot is intended to continue our cleanup of (relatively) easily disposed issues, picking up where ballot 1 left off. These resolutions are intended to be noncontroversial. If significant debate or discussion is raised during the review period, we will likely remove those resolutions from ballot 2 prior to voting. A review and discussion of this ballot will occur on the regularly scheduled RTF telecon on Thursday, July 26, 2012 at 10:00 ET, and in any subsequent telecons as required. The property notation from UML to support redefinition and subsetting should be included in SysML explicitly. This notation is not currently included in the diagram element tables in the Blocks Chapter. Refer to property notation in Section 7.3.44 of the Superstructure Specification (v2.3).