• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

[component diagram] interface with subsystems

 
Hank GU
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
in [Mark Cade], "package" symbol is used to present a subsystem, an interface is placed in between the OrderProcessor and the subsystem.

but seems, in UML 1.4, it is illegal to has a package/subsystem in a companent diagram, (at least, in JUDE supporting of UML1.4, we can't do that), so I wonder whether there is another way to interface with subsystems in component diagram? or how do you think about it?

Thanks for any word replied.
 
I Roberts
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is not illegal in UML 1.x or UML 2.0 to have a subsystem referenced as a package within a component diagram. Please check the OMG website for a reference of the UML 1.5 Specification.

Please note that a number of vendor-specific UML tools constrain the use of the specification to their "vision" of how UML should support OOAD. As a result, there is an obvious variation between vendor-tools (e.g. Jude, Together Designer, Posiedon etc). Personally, due to this constraint and lack of flexibility that is allowed in the official specification, I prefer to use Microsoft Visio with an external supporting UML 1.x or UML 2.0 template. Please note that this is not Microsoft Visio UML, which also has a constraint, but a supporting template that offers full flexibility. The author, however, must know the specification.

Hope this helps!?
 
Hank GU
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ian, thanks for your reply. it does help!

So, to your understanding, is there a legal way to reference subsystem in component diagram in UML standard?

or for our assignment, is it sufficient to just put a interface?
 
I Roberts
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You wouldn't show an interface sourced by a subsystem package. For example, a component that has a dependency on a subsystem would have a dependency (e.g. "------>") relationship direct to the subsystem (i.e. an interface on the subsystem would not be shown as this would be conflict on the intention of the abstraction - an interface is a lower detailed abstraction than a subsystem).

You could also show a component at an appliation level (e.g. "<<application>>" stereotype) and then have it present an interface.

The UML 1.5 and UML 2.0 specifications are free to download from www.omg.com.

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic