-
Key: SYSMLR-326
-
Status: closed
-
Source: GfSE e.V. ( Mr. Robert Karban)
-
Summary:
Issue:
When ItemFlow connects (deeply) nested or inherited properties (e.g. ports or parts) we cannot uniquely identify the sources and targets in its context.Description:
This is similar to other relationships which specialize DirectedRelationshipPropertyPath, e.g. "The Allocate stereotype
specializes DirectedRelationshipPropertyPath to enable allocations to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets."The DirectedRelationshipPropertyPath stereotype based on UML DirectedRelationship.
Stereotype <<ItemFlow>> extends UML metaclass UML4SysML::InformationFlow which specializes DirectedRelationship. -
Reported: SysML 1.4 — Tue, 13 Sep 2016 18:48 GMT
-
Disposition: Deferred — SysML 1.5
-
Disposition Summary:
This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force
-
Updated: Tue, 3 Jan 2017 13:36 GMT
SYSMLR — Make ItemFlow a specialization of DirectedRelationshipPropertyPath
- Key: SYSMLR-326
- OMG Task Force: SysML 1.5 RTF