-
Key: UMLR-153
-
Legacy Issue Number: 13192
-
Status: open
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
With the increasing use of UML and descendant languages (e.g.., SysML) for more complex diagramming situations, the occasion for crossing lines becomes increasingly hard to avoid. When such happens, it often becomes difficult to determine the correct start/destination of each line. This is compounded by the use of tree structures for the depicting of generalization and aggregation/composition relationships.
Whenever two lines cross, there can ambiguity associated with the line path. The UML standard should supply a normative technique to resolve this ambiguity, The introduction of a “jog” - a small curve in one of the intersecting lines has traditionally be acceptable.
Proposed solution:
In the diagram appendix, add a paragraph introducing the problem and recommending a standard graphical solution. A diagram may be useful to convey the intent.
If a normative solution is not desired, the paragraph can recommend several selected approaches to resolve the disambiguities.
-
Reported: UML 2.5 — Wed, 24 Dec 2008 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
UMLR — UML: Standard Techniques to disambiguate crossing lines needed
- Key: UMLR-153
- OMG Task Force: UML 2.6 RTF