Issue 19284: Update to Trace Relationship’ (sysml-rtf) Source: oose Innovative Informatik eG (Mr. Tim Weilkiens, tim.weilkiens(at)oose.de) Nature: Uncategorized Issue Severity: Summary: I potentially found a mistake in the latest SysML specification. It can be found on page 144. The “Trace Dependency” and the “TraceCallout” are introduced on this page. Usually these two visualizations should show the same aspect of a SysML model. Unfortunately the “Trace Dependency” is only introduced between two requirements whilst the “TraceCallout” is shown between a requirement and a more general NamedElement. I think the named element should be allowed in both cases in the client role of the trace dependency. ADDITIONAL TEXT The trace stereotype as defined in 16.3.2.7 does not constrain either end of the trace relationship than the having one client and one supplier. 16.3.2.7 Trace Description The Trace stereotype specializes UML4SysML Trace and DirectedRelationshipPropertyPath to enable traces to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets. Constraints [1] The Trace stereotype may only be applied to dependencies. [2] Dependencies with a Trace stereotype or one of its specializations applied must have exactly one client and one supplier. From the UML 2.5 Standard Profile, the UML4SysML::Trace extends Abstraction, which subclasses Dependency. Dependencys are directed relationships between Named Elements. Therefore, the SysML::Trace can have any Named Element as its ends. The diagram elements Table 16.2 on pg 144 should be clarified. Also, in section 16.3.2.7, the trace relationship has specific definitions for Requirements: Operations [1] The query getTracedFrom() gives all the requirements that are clients (from end of the concrete syntax) of a Trace relationship whose supplier is the element in parameter. This is a static query. Trace::getTracedFrom(ref : NamedElement) : Set(Requirement ) {query, static} getTracedFrom=Requirement.AllInstances()->select(traceTo->includes(ref)) The query getTracedFrom() could be more general and query all NamedElements and not only Requirements. Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: March 14, 2014: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: End of Annotations:===== m: Tim Weilkiens To: "sysml-rtf@omg.org" Subject: Issue about Trace and NamedElement Thread-Topic: Issue about Trace and NamedElement Thread-Index: Ac8/pk8kC5mo+r/iTUCnO9t8qkFnvA== Date: Fri, 14 Mar 2014 16:56:14 +0000 Accept-Language: de-DE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.21] X-XWALL-BCKS: auto X-Virus-Scanned: amavisd-new at omg.org Hi, I work with Georg together in a research project about functional architectures with SysML and the mapping the mechanical world (CAD). He has spotted a potential issue and ask me to forward his finding to the group: ---- To whom it may concern, I potentially found a mistake in the latest SysML specification. It can be found on page 144. The .Trace Dependency. and the .TraceCallout. are introduced on this page. Usually these two visualizations should show the same aspect of a SysML model. Unfortunately the .Trace Dependency. is only introduced between two requirements whilst the .TraceCallout. is shown between a requirement and a more general NamedElement. I think the named element should be allowed in both cases in the client role of the trace dependency. Yours sincerely Georg Moeser Karlsruhe Institute of Technology (KIT) IPEK . Institute of Product Engineering Dipl.-Ing. Georg Moeser Scientific Assistant . Research Group Systemic Mobility KaiserstraĂź 10 Gebäe 10.23 76131 Karlsruhe Germany Phone: +49 721 608-47176 Fax: +49 721 608-46051 E-Mail: georg.moeser@kit.edu Web: http://www.ipek.kit.edu/ KIT . University of the State of Baden-Wuerttemberg and National Research Center of the Helmholtz Association Diese Information ist fĂĽ Gebrauch durch die Person oder die Firma/Organisation bestimmt, die in der Empfäeradresse benannt ist und unterliegt u. U. dem Betriebsgeheimnis, dem Schutz von Arbeitsergebnissen oder anderweitigem rechtlichen Schutz. Wenn Sie nicht der angegebene Empfäer sind, nehmen Sie bitte zur Kenntnis, dass Weitergabe, Kopieren, Verteilung oder Nutzung des Inhalts dieser E-Mail-Ăśertragung unzuläig ist. Falls Sie diese E-Mail irrtĂĽ erhalten haben, benachrichtigen Sie den Absender bitte unverzĂĽ telefonisch oder durch eine E-Mail und löen Sie diese Information aus Ihrem EDV-System. This e-mail message is intended only for the use of the named recipient(s) and contains information which may be confidential or privileged. If you are not the intended recipient, be aware that any distribution, or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the sender and delete the material from the computer. ---- Tim Weilkiens (CEO) oose Innovative Informatik GmbH Kontorhaus Montblanc, Schulterblatt 36, D-20357 Hamburg, Germany HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 CEO Tim Weilkiens Fon: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50 Internet: www.oose.de, E-Mail: info@oose.de