Issue 16373: Content of Requirement::/tracedTo (sysml-rtf) Source: Commissariat a l Energie Atomique-CEA (Mr. Yann Tanguy, yann.tanguy(at)cea.fr) Nature: Uncategorized Issue Severity: Summary: In the specification the content of the derived property “Requirement::tracedTo” is defined as follows: • /tracedTo: NamedElement [*] Derived from all elements that are the supplier of a «trace» relationship for which this requirement is a client. As «copy» «deriveReqt» «verify» and «satisfy» inherit from “Trace”, does this means that /tracedTo also list all elements that are the supplier of a «copy» «verify» «satisfy» «deriveReqt» relationship for which this requirement is a client ? Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: July 18, 2011: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: End of Annotations:===== m: TANGUY Yann 176637 To: "sysml-rtf@omg.org" CC: GERARD Sebastien 166342 Subject: Content of Requirement::/tracedTo Thread-Topic: Content of Requirement::/tracedTo Thread-Index: AcxFS1k2RP8Nxyn/TyGKOV/yETMwTw== Date: Mon, 18 Jul 2011 13:05:21 +0000 Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [132.166.88.105] x-tm-as-product-ver: SMEX-10.0.0.4152-6.500.1024-18268.002 x-tm-as-result: No--36.862800-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Hi, In the specification the content of the derived property .Requirement::tracedTo. is defined as follows: . /tracedTo: NamedElement [*] Derived from all elements that are the supplier of a «trace» relationship for which this requirement is a client. As «copy» «deriveReqt» «verify» and «satisfy» inherit from .Trace., does this means that /tracedTo also list all elements that are the supplier of a «copy» «verify» «satisfy» «deriveReqt» relationship for which this requirement is a client ? Best regards, Yann Tanguy From: TANGUY Yann 176637 To: Juergen Boldt , "sysml-rtf@omg.org" CC: GERARD Sebastien 166342 Subject: RE: Content of Requirement::/tracedTo Thread-Topic: Content of Requirement::/tracedTo Thread-Index: AQHMRjnJRP8Nxyn/TyGKOV/yETMwT5T04mcA Date: Wed, 20 Jul 2011 08:40:41 +0000 Accept-Language: fr-FR, en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [132.166.88.105] x-tm-as-product-ver: SMEX-10.0.0.4152-6.500.1024-18272.001 x-tm-as-result: No--41.370300-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No I you agree on the fact that the specification is unclear on this, yes you should probably file a bug. Moreover, I have some implementation choices to do here for Papyrus depending on our interpretation of the specification, and I wanted to get some feedback from the SysML team before that. Can someone share some information about the expected .content. of these derived properties ? Yann. De : Juergen Boldt [mailto:juergen@omg.org] Envoyé : mardi 19 juillet 2011 19:32 À : TANGUY Yann 176637; sysml-rtf@omg.org Cc : GERARD Sebastien 166342 Objet : Re: Content of Requirement::/tracedTo should I file this as an issue? -Juergen At 09:05 AM 7/18/2011, TANGUY Yann 176637 wrote: Hi, In the specification the content of the derived property .Requirement::tracedTo. is defined as follows: . /tracedTo: NamedElement [*] Derived from all elements that are the supplier of a «trace» relationship for which this requirement is a client. As «copy» «deriveReqt» «verify» and «satisfy» inherit from .Trace., does this means that /tracedTo also list all elements that are the supplier of a «copy» «verify» «satisfy» «deriveReqt» relationship for which this requirement is a client ? Best regards, Yann Tanguy Juergen Boldt Director, Member Services 140 Kendrick Street, Building A Suite 300 Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org X-Trusted-NM: yes Subject: Re: Content of Requirement::/tracedTo From: Nerijus Jankevicius Date: Wed, 20 Jul 2011 13:52:58 +0300 Cc: Juergen Boldt , "sysml-rtf@omg.org" , GERARD Sebastien 166342 To: TANGUY Yann 176637 X-Mailer: Apple Mail (2.1084) Note that verify and satisfy relations are in opposite direction, so don't count. Copy and Derive remain unclear. In MagicDraw SysML implementation, we don't add these into TracedTo values. We check <> only, without subtypes. I believe, this is what description means. Regards, -- Nerijus Jankevicius SysML Product Manager OMG-Certified UML Professional No Magic Europe Savanoriu pr. 363, LT 49425 Kaunas, Lithuania 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 - UML made simple! On Jul 20, 2011, at 11:40 AM, TANGUY Yann 176637 wrote: I you agree on the fact that the specification is unclear on this, yes you should probably file a bug. Moreover, I have some implementation choices to do here for Papyrus depending on our interpretation of the specification, and I wanted to get some feedback from the SysML team before that. Can someone share some information about the expected .content. of these derived properties ? Yann. De : Juergen Boldt [mailto:juergen@omg.org] Envoyé : mardi 19 juillet 2011 19:32 À : TANGUY Yann 176637; sysml-rtf@omg.org Cc : GERARD Sebastien 166342 Objet : Re: Content of Requirement::/tracedTo should I file this as an issue? -Juergen At 09:05 AM 7/18/2011, TANGUY Yann 176637 wrote: Hi, In the specification the content of the derived property .Requirement::tracedTo. is defined as follows: . /tracedTo: NamedElement [*] Derived from all elements that are the supplier of a «trace» relationship for which this requirement is a client. As «copy» «deriveReqt» «verify» and «satisfy» inherit from .Trace., does this means that /tracedTo also list all elements that are the supplier of a «copy» «verify» «satisfy» «deriveReqt» relationship for which this requirement is a client ? Best regards, Yann Tanguy Juergen Boldt Director, Member Services 140 Kendrick Street, Building A Suite 300 Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org From: TANGUY Yann 176637 To: Nerijus Jankevicius CC: "sysml-rtf@omg.org" , GERARD Sebastien 166342 Subject: RE: Content of Requirement::/tracedTo Thread-Topic: Content of Requirement::/tracedTo Thread-Index: AQHMRjnJRP8Nxyn/TyGKOV/yETMwT5T04mcAgAAF/QCAACz3UA== Date: Wed, 20 Jul 2011 11:34:49 +0000 Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [132.166.88.105] x-tm-as-product-ver: SMEX-10.0.0.4152-6.500.1024-18272.001 x-tm-as-result: No--44.137400-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Thanks. De : Nerijus Jankevicius [mailto:nerijus@nomagic.com] Envoyé : mercredi 20 juillet 2011 12:53 À : TANGUY Yann 176637 Cc : Juergen Boldt; sysml-rtf@omg.org; GERARD Sebastien 166342 Objet : Re: Content of Requirement::/tracedTo Note that verify and satisfy relations are in opposite direction, so don't count. Copy and Derive remain unclear. In MagicDraw SysML implementation, we don't add these into TracedTo values. We check <> only, without subtypes. I believe, this is what description means. Regards, -- Nerijus Jankevicius SysML Product Manager OMG-Certified UML Professional No Magic Europe Savanoriu pr. 363, LT 49425 Kaunas, Lithuania 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 - UML made simple! On Jul 20, 2011, at 11:40 AM, TANGUY Yann 176637 wrote: I you agree on the fact that the specification is unclear on this, yes you should probably file a bug. Moreover, I have some implementation choices to do here for Papyrus depending on our interpretation of the specification, and I wanted to get some feedback from the SysML team before that. Can someone share some information about the expected .content. of these derived properties ? Yann. De : Juergen Boldt [mailto:juergen@omg.org] Envoyé : mardi 19 juillet 2011 19:32 À : TANGUY Yann 176637; sysml-rtf@omg.org Cc : GERARD Sebastien 166342 Objet : Re: Content of Requirement::/tracedTo should I file this as an issue? -Juergen At 09:05 AM 7/18/2011, TANGUY Yann 176637 wrote: Hi, In the specification the content of the derived property .Requirement::tracedTo. is defined as follows: . /tracedTo: NamedElement [*] Derived from all elements that are the supplier of a «trace» relationship for which this requirement is a client. As «copy» «deriveReqt» «verify» and «satisfy» inherit from .Trace., does this means that /tracedTo also list all elements that are the supplier of a «copy» «verify» «satisfy» «deriveReqt» relationship for which this requirement is a client ? Best regards, Yann Tanguy Juergen Boldt Director, Member Services 140 Kendrick Street, Building A Suite 300 Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org