Issue 11276: Issue: Nested connector ends (sysml-rtf) Source: oose Innovative Informatik eG (Mr. Tim Weilkiens, tim.weilkiens(at)oose.de) Nature: Uncategorized Issue Severity: Summary: Nested connector ends: "Connectors may be drawn that cross the boundaries of nested properties to connect to properties within them." That's an important feature of SysML. "The ability to connect to nested properties within a containing block requires that multiple levels of decomposition be shown on the same diagram." I think that's a problem in practice. Often I don't want to see the nested properties in the diagram. I propose to add a notational feature to show that a connector end is connected with a nested property without showing that property. For example we could draw the connector to the border of the surrounding property and attach the stereotype <<nested>> as a short form of <<nestedConnectorEnd>> and optionally the propertyPath. What do you think? Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: August 10, 2007: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: Discussion of this issue was still in progress at the end of the current RTF. The issue is being deferred so the discussion can continue under any future revision process. Disposition: Deferred Discussion: This issue is deferred because no other proposed resolution was voted on during the schedule of the SysML 1.2 RTF. Following is the discussion from a previous deferred resolution by the SysML 1.1 RTF: Discussion of this issue was still in progress at the end of the current RTF. The issue is being deferred so the discussion can continue under any future revision process. Disposition: Deferred End of Annotations:===== ubject: Issue: Nested connector ends Date: Fri, 10 Aug 2007 08:01:26 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue: Nested connector ends Thread-Index: AcfZvtsen5pL/1e1RHeWOa4FCR5wwwAjYwZA From: "Tim Weilkiens" To: Nested connector ends: "Connectors may be drawn that cross the boundaries of nested properties to connect to properties within them." That's an important feature of SysML. "The ability to connect to nested properties within a containing block requires that multiple levels of decomposition be shown on the same diagram." I think that's a problem in practice. Often I don't want to see the nested properties in the diagram. I propose to add a notational feature to show that a connector end is connected with a nested property without showing that property. For example we could draw the connector to the border of the surrounding property and attach the stereotype <> as a short form of <> and optionally the propertyPath. What do you think? Tim > -----Original Message----- > From: Tim Weilkiens > Sent: Wednesday, August 08, 2007 3:20 PM > To: Tim Weilkiens > Subject: SysML issue: Darstellung nested connector ends > > > > Mit freundlichen Grüßen, > > i.A. Tim Weilkiens > (Berater und Trainer) > > ----------------------------------------------------------------- > oose Innovative Informatik GmbH > Tower Falkenried-Piazza, Straßenbahnring 7, D-20251 Hamburg > HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 > Geschäftsführer Bernd Schröder-Oestereich, Christian Weiss > Fon: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50 > Internet: www.oose.de, E-Mail: office@oose.de > Der Inhalt dieser E-Mail ist nur für den Empfänger und nicht > zur Veröffentlichung oder unautorisierten Weitergabe bestimmt. > nestedConnectorEnd.pdf From: "Nerijus Jankevicius" To: "Tim Weilkiens" , Subject: Re: Issue: Nested connector ends Date: Fri, 10 Aug 2007 09:14:53 +0300 X-Mailer: Microsoft Windows Mail 6.0.6000.16480 Hello Tim, In any case you will be forced to specify exact nested part, because connector shall be connected to it. SysML has ability to show deep nested part without graphical nesting, using regular part symbol with full path to nested part (using dots as separators). Isn't alternative to your suggestion? Regards, -- Nerijus Jankevicius Senior System Analyst OMG-Certified UML Professional No Magic Lithuanian Development Center Savanoriu pr. 363, LT 49425 Kaunas P.O. box 2166, LT- 3000, Kaunas Phone: +370-37-324032 Fax: +370-37-320670 e-mail: nerijus@magicdraw.com WWW: http://www.magicdraw.com -- MagicDraw - Architecture made simple! ----- Original Message ----- From: "Tim Weilkiens" To: Sent: Friday, August 10, 2007 9:01 AM Subject: Issue: Nested connector ends Nested connector ends: "Connectors may be drawn that cross the boundaries of nested properties to connect to properties within them." That's an important feature of SysML. "The ability to connect to nested properties within a containing block requires that multiple levels of decomposition be shown on the same diagram." I think that's a problem in practice. Often I don't want to see the nested properties in the diagram. I propose to add a notational feature to show that a connector end is connected with a nested property without showing that property. For example we could draw the connector to the border of the surrounding property and attach the stereotype <> as a short form of <> and optionally the propertyPath. What do you think? Tim -----Original Message----- From: Tim Weilkiens Sent: Wednesday, August 08, 2007 3:20 PM To: Tim Weilkiens Subject: SysML issue: Darstellung nested connector ends Mit freundlichen Grüßen, i.A. Tim Weilkiens (Berater und Trainer) ----------------------------------------------------------------- oose Innovative Informatik GmbH Tower Falkenried-Piazza, Straßenbahnring 7, D-20251 Hamburg HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 Geschäftsführer Bernd Schröder-Oestereich, Christian Weiss Fon: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50 Internet: www.oose.de, E-Mail: office@oose.de Der Inhalt dieser E-Mail ist nur für den Empfänger und nicht zur Veröffentlichung oder unautorisierten Weitergabe bestimmt. Subject: RE: Issue: Nested connector ends Date: Fri, 10 Aug 2007 09:30:39 . X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue: Nested connector ends Thread-Index: AcfbFiICpAluKsceRXKn9w7kjnQGLQACcpfw From: "Tim Weilkiens" To: "Nerijus Jankevicius" , Nerijus, Yes, that's an alternative, but it's not perfect, because it scatters the diagram. I've extended my example to show what I mean. Using your proposal I must show the nested part and the enclosing part in different symbols. I think it's only a notational issue. The nested connector end stores the complete path to the nested part. But the diagram shows only a part of it by attaching the connector to one of the enclosing parts. The stereotype shows that it is more nested and the propertyPath shows me the rest of the path. Tim > -----Original Message----- > From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] > Sent: Friday, August 10, 2007 8:15 AM > To: Tim Weilkiens; sysml-rtf@omg.org > Subject: Re: Issue: Nested connector ends > > Hello Tim, > > In any case you will be forced to specify exact nested part, because > connector shall be connected to it. > SysML has ability to show deep nested part without graphical > nesting, using > regular part symbol with full path to nested part (using dots as > separators). > Isn't alternative to your suggestion? > > Regards, > -- > Nerijus Jankevicius > Senior System Analyst > OMG-Certified UML Professional > No Magic Lithuanian Development Center > Savanoriu pr. 363, LT 49425 Kaunas > P.O. box 2166, LT- 3000, Kaunas > Phone: .37-324032 Fax: .37-320670 > e-mail: nerijus@magicdraw.com > WWW: http://www.magicdraw.com > -- > MagicDraw - Architecture made simple! > > > ----- Original Message ----- > From: "Tim Weilkiens" > To: > Sent: Friday, August 10, 2007 9:01 AM > Subject: Issue: Nested connector ends > > > Nested connector ends: > > "Connectors may be drawn that cross the boundaries of nested > properties to > connect to properties within them." > > That's an important feature of SysML. > > "The ability to connect to nested properties within a > containing block > requires that multiple levels of decomposition be > shown on the same diagram." > > I think that's a problem in practice. Often I don't want to > see the nested > properties in the diagram. > I propose to add a notational feature to show that a connector end is > connected with a nested property without > showing that property. > > For example we could draw the connector to the border of the > surrounding > property and attach the stereotype <> > as a short form of <> and optionally the > propertyPath. > > What do you think? > > Tim > > > > -----Original Message----- > > From: Tim Weilkiens > > Sent: Wednesday, August 08, 2007 3:20 PM > > To: Tim Weilkiens > > Subject: SysML issue: Darstellung nested connector ends > > > > > > > > Mit freundlichen Grüßen, > > > > i.A. Tim Weilkiens > > (Berater und Trainer) > > > > ----------------------------------------------------------------- > > oose Innovative Informatik GmbH > > Tower Falkenried-Piazza, Straßenbahnring 7, D-20251 Hamburg > > HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 > > Geschäftsführer Bernd Schröder-Oestereich, Christian Weiss > > Fon: (40) 41 42 50-0, Fax: (40) 41 42 50-50 > > Internet: www.oose.de, E-Mail: office@oose.de > > Der Inhalt dieser E-Mail ist nur für den Empfänger und nicht > > zur Veröffentlichung oder unautorisierten Weitergabe bestimmt. > > > > nestedConnectorEnd1.pdf Date: Fri, 10 Aug 2007 08:03:42 -0400 From: "Friedenthal, Sanford" Subject: RE: Issue: Nested connector ends To: Tim Weilkiens , Nerijus Jankevicius , sysml-rtf@omg.org Thread-Topic: Issue: Nested connector ends Thread-Index: AcfbFiICpAluKsceRXKn9w7kjnQGLQACcpfwAAl+HcA= X-MS-Has-Attach: yes X-MS-TNEF-Correlator: X-OriginalArrivalTime: 10 Aug 2007 12:03:43.0094 (UTC) FILETIME=[7F291160:01C7DB46] Tim Russell Peak has shown a compromise approach where he shows the part "c" flush with the internal boundary of B. In this way, the part "c:C" appears similar to a port (bud different), but would allow you to connect to the boundary. If the part is further nested, you would do the same using the dot notation for the part. Sandy Sanford Friedenthal Lockheed Martin (703) 293-5557 -----Original Message----- From: Tim Weilkiens [mailto:Tim.Weilkiens@oose.de] Sent: Friday, August 10, 2007 3:31 AM To: Nerijus Jankevicius; sysml-rtf@omg.org Subject: RE: Issue: Nested connector ends Nerijus, Yes, that's an alternative, but it's not perfect, because it scatters the diagram. I've extended my example to show what I mean. Using your proposal I must show the nested part and the enclosing part in different symbols. I think it's only a notational issue. The nested connector end stores the complete path to the nested part. But the diagram shows only a part of it by attaching the connector to one of the enclosing parts. The stereotype shows that it is more nested and the propertyPath shows me the rest of the path. Tim > -----Original Message----- > From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] > Sent: Friday, August 10, 2007 8:15 AM > To: Tim Weilkiens; sysml-rtf@omg.org > Subject: Re: Issue: Nested connector ends > > Hello Tim, > > In any case you will be forced to specify exact nested part, because > connector shall be connected to it. > SysML has ability to show deep nested part without graphical > nesting, using > regular part symbol with full path to nested part (using dots as > separators). > Isn't alternative to your suggestion? > > Regards, > -- > Nerijus Jankevicius > Senior System Analyst > OMG-Certified UML Professional > No Magic Lithuanian Development Center > Savanoriu pr. 363, LT 49425 Kaunas > P.O. box 2166, LT- 3000, Kaunas > Phone: +370-37-324032 Fax: +370-37-320670 > e-mail: nerijus@magicdraw.com > WWW: http://www.magicdraw.com > -- > MagicDraw - Architecture made simple! > > > ----- Original Message ----- > From: "Tim Weilkiens" > To: > Sent: Friday, August 10, 2007 9:01 AM > Subject: Issue: Nested connector ends > > > Nested connector ends: > > "Connectors may be drawn that cross the boundaries of nested > properties to > connect to properties within them." > > That's an important feature of SysML. > > "The ability to connect to nested properties within a > containing block > requires that multiple levels of decomposition be > shown on the same diagram." > > I think that's a problem in practice. Often I don't want to > see the nested > properties in the diagram. > I propose to add a notational feature to show that a connector end is > connected with a nested property without > showing that property. > > For example we could draw the connector to the border of the > surrounding > property and attach the stereotype <> > as a short form of <> and optionally the > propertyPath. > > What do you think? > > Tim > > > > -----Original Message----- > > From: Tim Weilkiens > > Sent: Wednesday, August 08, 2007 3:20 PM > > To: Tim Weilkiens > > Subject: SysML issue: Darstellung nested connector ends > > > > > > > > Mit freundlichen Grüßen, > > > > i.A. Tim Weilkiens > > (Berater und Trainer) > > > > ----------------------------------------------------------------- > > oose Innovative Informatik GmbH > > Tower Falkenried-Piazza, Straßenbahnring 7, D-20251 Hamburg > > HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 > > Geschäftsführer Bernd Schröder-Oestereich, Christian Weiss > > Fon: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50 > > Internet: www.oose.de, E-Mail: office@oose.de > > Der Inhalt dieser E-Mail ist nur für den Empfänger und nicht > > zur Veröffentlichung oder unautorisierten Weitergabe bestimmt. > > > > nestedConnectorEnd2.pdf Date: Fri, 10 Aug 2007 09:05:45 -0400 From: "Friedenthal, Sanford" Subject: RE: Issue: Nested connector ends To: Tim Weilkiens , Nerijus Jankevicius , sysml-rtf@omg.org Thread-Topic: Issue: Nested connector ends Thread-Index: AcfbFiICpAluKsceRXKn9w7kjnQGLQACcpfwAAl+HcAAAJtgQAABqnJw X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 10 Aug 2007 13:05:46.0117 (UTC) FILETIME=[2A414B50:01C7DB4F] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id l7AD4ZXE005526 I am not sure about the reference to the association block (water delivery), but the approach Russell uses is completely consistent with the notation. It merely modifies the size and location of the rectangle that represents the part. Sanford Friedenthal Lockheed Martin IS&GS (703) 293-5557 -----Original Message----- From: Tim Weilkiens [mailto:Tim.Weilkiens@oose.de] Sent: Friday, August 10, 2007 8:20 AM To: Friedenthal, Sanford; Nerijus Jankevicius; sysml-rtf@omg.org Subject: RE: Issue: Nested connector ends Sandy, I think there are similar notations in the sysml specification in the examples about the association block (water delivery etc.). Why is that allowed? I couldn't find the definition of that notation in SysML or UML. However that's not the best solution (I still prefer my one), but a practicable way. (Note: The problem occurs in a real medical systems project). Tim > -----Original Message----- > From: Friedenthal, Sanford [mailto:sanford.friedenthal@lmco.com] > Sent: Friday, August 10, 2007 2:04 PM > To: Tim Weilkiens; Nerijus Jankevicius; sysml-rtf@omg.org > Subject: RE: Issue: Nested connector ends > > Tim > > Russell Peak has shown a compromise approach where he shows > the part "c" flush with the internal boundary of B. In this > way, the part "c:C" appears similar to a port (bud > different), but would allow you to connect to the boundary. > If the part is further nested, you would do the same using > the dot notation for the part. > > Sandy > > Sanford Friedenthal > Lockheed Martin > (703) 293-5557 > > -----Original Message----- > From: Tim Weilkiens [mailto:Tim.Weilkiens@oose.de] > Sent: Friday, August 10, 2007 3:31 AM > To: Nerijus Jankevicius; sysml-rtf@omg.org > Subject: RE: Issue: Nested connector ends > > Nerijus, > > Yes, that's an alternative, but it's not perfect, because it > scatters the > diagram. I've extended my example to show what I mean. Using > your proposal > I must show the nested part and the enclosing part in > different symbols. > > I think it's only a notational issue. The nested connector > end stores the > complete path to the nested part. But the diagram shows only > a part of it > by attaching the connector to one of the enclosing parts. The > stereotype > shows that it is more nested and the propertyPath shows me > the rest of the > path. > > Tim > > > -----Original Message----- > > From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] > > Sent: Friday, August 10, 2007 8:15 AM > > To: Tim Weilkiens; sysml-rtf@omg.org > > Subject: Re: Issue: Nested connector ends > > > > Hello Tim, > > > > In any case you will be forced to specify exact nested > part, because > > connector shall be connected to it. > > SysML has ability to show deep nested part without graphical > > nesting, using > > regular part symbol with full path to nested part (using dots as > > separators). > > Isn't alternative to your suggestion? > > > > Regards, > > -- > > Nerijus Jankevicius > > Senior System Analyst > > OMG-Certified UML Professional > > No Magic Lithuanian Development Center > > Savanoriu pr. 363, LT 49425 Kaunas > > P.O. box 2166, LT- 3000, Kaunas > > Phone: +370-37-324032 Fax: +370-37-320670 > > e-mail: nerijus@magicdraw.com > > WWW: http://www.magicdraw.com > > -- > > MagicDraw - Architecture made simple! > > > > > > ----- Original Message ----- > > From: "Tim Weilkiens" > > To: > > Sent: Friday, August 10, 2007 9:01 AM > > Subject: Issue: Nested connector ends > > > > > > Nested connector ends: > > > > "Connectors may be drawn that cross the boundaries of nested > > properties to > > connect to properties within them." > > > > That's an important feature of SysML. > > > > "The ability to connect to nested properties within a > > containing block > > requires that multiple levels of decomposition be > > shown on the same diagram." > > > > I think that's a problem in practice. Often I don't want to > > see the nested > > properties in the diagram. > > I propose to add a notational feature to show that a > connector end is > > connected with a nested property without > > showing that property. > > > > For example we could draw the connector to the border of the > > surrounding > > property and attach the stereotype <> > > as a short form of <> and optionally the > > propertyPath. > > > > What do you think? > > > > Tim > > > > > > > -----Original Message----- > > > From: Tim Weilkiens > > > Sent: Wednesday, August 08, 2007 3:20 PM > > > To: Tim Weilkiens > > > Subject: SysML issue: Darstellung nested connector ends > > > > > > > > > > > > Mit freundlichen Grüßen, > > > > > > i.A. Tim Weilkiens > > > (Berater und Trainer) > > > > > > ----------------------------------------------------------------- > > > oose Innovative Informatik GmbH > > > Tower Falkenried-Piazza, Straßenbahnring 7, D-20251 Hamburg > > > HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 > > > Geschäftsführer Bernd Schröder-Oestereich, Christian Weiss > > > Fon: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50 > > > Internet: www.oose.de, E-Mail: office@oose.de > > > Der Inhalt dieser E-Mail ist nur für den Empfänger und nicht > > > zur Veröffentlichung oder unautorisierten Weitergabe bestimmt. > > > > > > > > Subject: RE: Issue: Nested connector ends Date: Fri, 10 Aug 2007 15:09:04 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue: Nested connector ends Thread-Index: AcfbFiICpAluKsceRXKn9w7kjnQGLQACcpfwAAl+HcAAAJtgQAABqnJwAAAi4oA= From: "Tim Weilkiens" To: "Friedenthal, Sanford" , "Nerijus Jankevicius" , X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id l7AD8rch006022 Ok. The examples in the sysml specification use a similar approach, but the small part rectangles are within the name compartment which is not allowed. Tim > -----Original Message----- > From: Friedenthal, Sanford [mailto:sanford.friedenthal@lmco.com] > Sent: Friday, August 10, 2007 3:06 PM > To: Tim Weilkiens; Nerijus Jankevicius; sysml-rtf@omg.org > Subject: RE: Issue: Nested connector ends > > I am not sure about the reference to the association block > (water delivery), but the approach Russell uses is completely > consistent with the notation. It merely modifies the size and > location of the rectangle that represents the part. > > Sanford Friedenthal > Lockheed Martin IS&GS > (703) 293-5557 > > > -----Original Message----- > From: Tim Weilkiens [mailto:Tim.Weilkiens@oose.de] > Sent: Friday, August 10, 2007 8:20 AM > To: Friedenthal, Sanford; Nerijus Jankevicius; sysml-rtf@omg.org > Subject: RE: Issue: Nested connector ends > > Sandy, > > I think there are similar notations in the sysml > specification in the examples about > the association block (water delivery etc.). Why is that > allowed? I couldn't find > the definition of that notation in SysML or UML. > > However that's not the best solution (I still prefer my one), > but a practicable way. > (Note: The problem occurs in a real medical systems project). > > Tim > > > -----Original Message----- > > From: Friedenthal, Sanford [mailto:sanford.friedenthal@lmco.com] > > Sent: Friday, August 10, 2007 2:04 PM > > To: Tim Weilkiens; Nerijus Jankevicius; sysml-rtf@omg.org > > Subject: RE: Issue: Nested connector ends > > > > Tim > > > > Russell Peak has shown a compromise approach where he shows > > the part "c" flush with the internal boundary of B. In this > > way, the part "c:C" appears similar to a port (bud > > different), but would allow you to connect to the boundary. > > If the part is further nested, you would do the same using > > the dot notation for the part. > > > > Sandy > > > > Sanford Friedenthal > > Lockheed Martin > > (703) 293-5557 > > > > -----Original Message----- > > From: Tim Weilkiens [mailto:Tim.Weilkiens@oose.de] > > Sent: Friday, August 10, 2007 3:31 AM > > To: Nerijus Jankevicius; sysml-rtf@omg.org > > Subject: RE: Issue: Nested connector ends > > > > Nerijus, > > > > Yes, that's an alternative, but it's not perfect, because it > > scatters the > > diagram. I've extended my example to show what I mean. Using > > your proposal > > I must show the nested part and the enclosing part in > > different symbols. > > > > I think it's only a notational issue. The nested connector > > end stores the > > complete path to the nested part. But the diagram shows only > > a part of it > > by attaching the connector to one of the enclosing parts. The > > stereotype > > shows that it is more nested and the propertyPath shows me > > the rest of the > > path. > > > > Tim > > > > > -----Original Message----- > > > From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] > > > Sent: Friday, August 10, 2007 8:15 AM > > > To: Tim Weilkiens; sysml-rtf@omg.org > > > Subject: Re: Issue: Nested connector ends > > > > > > Hello Tim, > > > > > > In any case you will be forced to specify exact nested > > part, because > > > connector shall be connected to it. > > > SysML has ability to show deep nested part without graphical > > > nesting, using > > > regular part symbol with full path to nested part (using dots as > > > separators). > > > Isn't alternative to your suggestion? > > > > > > Regards, > > > -- > > > Nerijus Jankevicius > > > Senior System Analyst > > > OMG-Certified UML Professional > > > No Magic Lithuanian Development Center > > > Savanoriu pr. 363, LT 49425 Kaunas > > > P.O. box 2166, LT- 3000, Kaunas > > > Phone: +370-37-324032 Fax: +370-37-320670 > > > e-mail: nerijus@magicdraw.com > > > WWW: http://www.magicdraw.com > > > -- > > > MagicDraw - Architecture made simple! > > > > > > > > > ----- Original Message ----- > > > From: "Tim Weilkiens" > > > To: > > > Sent: Friday, August 10, 2007 9:01 AM > > > Subject: Issue: Nested connector ends > > > > > > > > > Nested connector ends: > > > > > > "Connectors may be drawn that cross the boundaries of nested > > > properties to > > > connect to properties within them." > > > > > > That's an important feature of SysML. > > > > > > "The ability to connect to nested properties within a > > > containing block > > > requires that multiple levels of decomposition be > > > shown on the same diagram." > > > > > > I think that's a problem in practice. Often I don't want to > > > see the nested > > > properties in the diagram. > > > I propose to add a notational feature to show that a > > connector end is > > > connected with a nested property without > > > showing that property. > > > > > > For example we could draw the connector to the border of the > > > surrounding > > > property and attach the stereotype <> > > > as a short form of <> and optionally the > > > propertyPath. > > > > > > What do you think? > > > > > > Tim > > > > > > > > > > -----Original Message----- > > > > From: Tim Weilkiens > > > > Sent: Wednesday, August 08, 2007 3:20 PM > > > > To: Tim Weilkiens > > > > Subject: SysML issue: Darstellung nested connector ends > > > > > > > > > > > > > > > > Mit freundlichen Grüßen, > > > > > > > > i.A. Tim Weilkiens > > > > (Berater und Trainer) > > > > > > > > > ----------------------------------------------------------------- > > > > oose Innovative Informatik GmbH > > > > Tower Falkenried-Piazza, Straßenbahnring 7, D-20251 Hamburg > > > > HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 > > > > Geschäftsführer Bernd Schröder-Oestereich, Christian Weiss > > > > Fon: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50 > > > > Internet: www.oose.de, E-Mail: office@oose.de > > > > Der Inhalt dieser E-Mail ist nur für den Empfänger und nicht > > > > zur Veröffentlichung oder unautorisierten Weitergabe bestimmt. > > > > > > > > > > > > > Subject: RE: Issue: Nested connector ends Date: Fri, 10 Aug 2007 14:20:09 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue: Nested connector ends Thread-Index: AcfbFiICpAluKsceRXKn9w7kjnQGLQACcpfwAAl+HcAAAJtgQA== From: "Tim Weilkiens" To: "Friedenthal, Sanford" , "Nerijus Jankevicius" , Sandy, I think there are similar notations in the sysml specification in the examples about the association block (water delivery etc.). Why is that allowed? I couldn't find the definition of that notation in SysML or UML. However that's not the best solution (I still prefer my one), but a practicable way. (Note: The problem occurs in a real medical systems project). Tim > -----Original Message----- > From: Friedenthal, Sanford [mailto:sanford.friedenthal@lmco.com] > Sent: Friday, August 10, 2007 2:04 PM > To: Tim Weilkiens; Nerijus Jankevicius; sysml-rtf@omg.org > Subject: RE: Issue: Nested connector ends > > Tim > > Russell Peak has shown a compromise approach where he shows > the part "c" flush with the internal boundary of B. In this > way, the part "c:C" appears similar to a port (bud > different), but would allow you to connect to the boundary. > If the part is further nested, you would do the same using > the dot notation for the part. > > Sandy > > Sanford Friedenthal > Lockheed Martin > (703) 293-5557 > > -----Original Message----- > From: Tim Weilkiens [mailto:Tim.Weilkiens@oose.de] > Sent: Friday, August 10, 2007 3:31 AM > To: Nerijus Jankevicius; sysml-rtf@omg.org > Subject: RE: Issue: Nested connector ends > > Nerijus, > > Yes, that's an alternative, but it's not perfect, because it > scatters the > diagram. I've extended my example to show what I mean. Using > your proposal > I must show the nested part and the enclosing part in > different symbols. > > I think it's only a notational issue. The nested connector > end stores the > complete path to the nested part. But the diagram shows only > a part of it > by attaching the connector to one of the enclosing parts. The > stereotype > shows that it is more nested and the propertyPath shows me > the rest of the > path. > > Tim > > > -----Original Message----- > > From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] > > Sent: Friday, August 10, 2007 8:15 AM > > To: Tim Weilkiens; sysml-rtf@omg.org > > Subject: Re: Issue: Nested connector ends > > > > Hello Tim, > > > > In any case you will be forced to specify exact nested > part, because > > connector shall be connected to it. > > SysML has ability to show deep nested part without graphical > > nesting, using > > regular part symbol with full path to nested part (using dots as > > separators). > > Isn't alternative to your suggestion? > > > > Regards, > > -- > > Nerijus Jankevicius > > Senior System Analyst > > OMG-Certified UML Professional > > No Magic Lithuanian Development Center > > Savanoriu pr. 363, LT 49425 Kaunas > > P.O. box 2166, LT- 3000, Kaunas > > Phone: +370-37-324032 Fax: +370-37-320670 > > e-mail: nerijus@magicdraw.com > > WWW: http://www.magicdraw.com > > -- > > MagicDraw - Architecture made simple! > > > > > > ----- Original Message ----- > > From: "Tim Weilkiens" > > To: > > Sent: Friday, August 10, 2007 9:01 AM > > Subject: Issue: Nested connector ends > > > > > > Nested connector ends: > > > > "Connectors may be drawn that cross the boundaries of nested > > properties to > > connect to properties within them." > > > > That's an important feature of SysML. > > > > "The ability to connect to nested properties within a > > containing block > > requires that multiple levels of decomposition be > > shown on the same diagram." > > > > I think that's a problem in practice. Often I don't want to > > see the nested > > properties in the diagram. > > I propose to add a notational feature to show that a > connector end is > > connected with a nested property without > > showing that property. > > > > For example we could draw the connector to the border of the > > surrounding > > property and attach the stereotype <> > > as a short form of <> and optionally the > > propertyPath. > > > > What do you think? > > > > Tim > > > > > > > -----Original Message----- > > > From: Tim Weilkiens > > > Sent: Wednesday, August 08, 2007 3:20 PM > > > To: Tim Weilkiens > > > Subject: SysML issue: Darstellung nested connector ends > > > > > > > > > > > > Mit freundlichen Grüßen, > > > > > > i.A. Tim Weilkiens > > > (Berater und Trainer) > > > > > > ----------------------------------------------------------------- > > > oose Innovative Informatik GmbH > > > Tower Falkenried-Piazza, Straßenbahnring 7, D-20251 Hamburg > > > HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 > > > Geschäftsführer Bernd Schröder-Oestereich, Christian Weiss > > > Fon: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50 > > > Internet: www.oose.de, E-Mail: office@oose.de > > > Der Inhalt dieser E-Mail ist nur für den Empfänger und nicht > > > zur Veröffentlichung oder unautorisierten Weitergabe bestimmt. > > > > > > > > nestedConnectorEnd3.pdf From: "Bock, Conrad" To: "sysml-rtf@omg.org" Date: Sun, 31 Jul 2011 09:18:32 -0400 Subject: RE: draft ballot 5 available for discussion through Thursday, August 4, 2011, comment on 11276 Thread-Topic: draft ballot 5 available for discussion through Thursday, August 4, 2011, comment on 11276 Thread-Index: AcxLRnk/r3Os3C2YRkmMPe2hsz4UvAAAvukAAQ62gWA= Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Roger, One comment on ballot 5. Conrad - 11276 (Notation for nested connector end) Since we have something like this for parametrics, it isn't beyond the diagram extensions in SysML currently, as the resolution says. I think this should be deferred. It could be part of the variant