Discussion:
Criss-crossing lines in UML diagrams
(too old to reply)
Ishan De Silva
2004-10-12 05:34:26 UTC
Permalink
Hi,

It seems that UML suggests to use a "jump" (as in an electrical
circuit), if one gets a situation where crossing-lines cannot be
avoided.

Is there a way of duplicating UML elements such as use cases, classes
etc. to avoid criss-crossing lines? (I mean a duplicating notation as
in structured notation SSADM)

If duplication is not allowed, is there a particular reason for it?

Thanks,
Ishan.
Phlip
2004-10-12 14:38:07 UTC
Permalink
Post by Ishan De Silva
It seems that UML suggests to use a "jump" (as in an electrical
circuit), if one gets a situation where crossing-lines cannot be
avoided.
Is there a way of duplicating UML elements such as use cases, classes
etc. to avoid criss-crossing lines? (I mean a duplicating notation as
in structured notation SSADM)
If duplication is not allowed, is there a particular reason for it?
Why does your UML diagram have so many elements that lines cross?

Try using a solid dot to link lines that connect. Or, only route lines from
node to node.
--
Phlip
http://industrialxp.org/community/bin/view/Main/TestFirstUserInterfaces
Ishan De Silva
2004-10-13 04:24:13 UTC
Permalink
Post by Phlip
Why does your UML diagram have so many elements that lines cross?
Well this is not what I expected. One can ask, Why can't you break up
the diagram to have a manageable number of elements?, Why don't you
revisit the desgin? etc.

But mine was a question on UML syntax. Is there a way to *duplicate*
elements? If not, why?
Post by Phlip
Try using a solid dot to link lines that connect. Or, only route lines from
node to node.
Anyway, I'm not clear what you mean here.

Thanks,
Ishan.
Robert C. Martin
2004-10-13 07:16:36 UTC
Permalink
Post by Ishan De Silva
Hi,
It seems that UML suggests to use a "jump" (as in an electrical
circuit), if one gets a situation where crossing-lines cannot be
avoided.
Is there a way of duplicating UML elements such as use cases, classes
etc. to avoid criss-crossing lines? (I mean a duplicating notation as
in structured notation SSADM)
If duplication is not allowed, is there a particular reason for it?
Duplication is allowed.

|A|<-----|B|----->|C|----->|A|




-----
Robert C. Martin (Uncle Bob) | email: ***@objectmentor.com
Object Mentor Inc. | blog: www.butunclebob.com
The Agile Transition Experts | web: www.objectmentor.com
800-338-6716


"The aim of science is not to open the door to infinite wisdom,
but to set a limit to infinite error."
-- Bertolt Brecht, Life of Galileo
Universe
2004-10-14 04:17:25 UTC
Permalink
Post by Robert C. Martin
Post by Ishan De Silva
Hi,
It seems that UML suggests to use a "jump" (as in an electrical
circuit), if one gets a situation where crossing-lines cannot be
avoided.
Is there a way of duplicating UML elements such as use cases, classes
etc. to avoid criss-crossing lines? (I mean a duplicating notation as
in structured notation SSADM)
If duplication is not allowed, is there a particular reason for it?
Duplication is allowed.
|A|<-----|B|----->|C|----->|A|
Just please avoid actual separate duplicate package classes--as some
XP'ers incredibly advocate.

Elliott
--
Global Plans + Iterative/Incremental Development
Theory Leads, Practice Verifies
Profiteer US Out of Iraq Now!
Loading...