Component diagram missing features

[Cosmin]

• The ball and socket notation for connecting provided and required interfaces cannot be connected via a dependency arrow. What I mean is the following situation:

That dependency arrow cannot be placed between the 2 interface symbols, it throws an error.

• Also, I didn't find a proper (simple) way to connect a ball and a socket like so:

The steps I used to do this are:

1. double click BlogDataSource and select Add provided interface

2. double click ConversionManagement and select Add required interface

3. carefully select the continuous line that touches the ball connector and drag the end of the line that is near the ball to the ConversionManagement connector. Now, StarUML will correctly display the symbol of a "connected interface" (ball with exterior encapsulating semi-circle symbol)

4. delete the ball simbol

This is annoying, if I chose the "implement interface" option from the toolbox, StarUML draws a continuous line to the ball symbol and does not draw the circle part from the exterior (the encapsulating symbol).

• There is no simple way of adding the following sections to a component:
• required interfaces
• provided interfaces
• artifacts

The only workaround I found for this is to hide the visibility modifiers of the attributes of the component and then add attributes and manually name them:
<<provided interface>> --- the first attribute

DataSource --- the second attribute

etc...

just to look like in the picture above, but it is... weird to do it like that.

Plus, there is no way to separate the <<artifacts>> section, because that would be replaced by the Operations section, which only shows method names with parentheses symbols at the end - there is no way to get rid of the parentheses symbols at the end of their names.

• there is no way to add classes that realize components in Component Diagrams

There should be a way of expressing that a class or more are contained / realized by a particular component, in 2 ways of expressing it:

internally (eventually with relationships with those classes):

externally, by specifying the realization relationship between the component and the class:

• there is no delegation connector available, to specify which interfaces of the component corresponds to which class that realizes that component:

• there is no assembly connector available, to specify the components that are working together using an interface:

(note that this is different as a symbol from the interface connection symbol - the external circle part has the same dimensions as the ball symbol and it is farther than the connection symbol, it does not touch the ball symbol at all)

[StarUML]

Hi,

StarUML support not all notations of UML.

About lollipop notation of interface, please check here: https://docs.staruml.io/working-with-diagrams/class-diagram#interface

Thanks,

StarUML Team

2020년 6월 25일 목요일 오후 10시 23분 40초 UTC+9에 cosminc...@gmail.com님이 작성:

[Jakub Bobran]

But will it?

I've recently purchased my personal license mainly because I was (wrongly) assuming that as a tool with UML in the name, I'll have full UML support (maybe, not SysML, maybe not BPM, but definitely UML...).

Or maybe there is a possibility to develop an extension which would expand ie. Component Diagram's functionality to fully support UML? Is it possible?

[StarUML]

Hi Jakub,

As we know, there is no tool supporting 100% of the latest UML specification and notations. UML specification is really complicated and quite ambiguous.

We believe that StarUML supports 99% of UML standard metamodel and notation and the 1% is the mostly not used in the ordinary projects. Even Dr. Grady Booch, the one of the UML inventor, is using StarUML as a go-to modeling tool.

If you have UML standard notation not supported in StarUML but in UML specification, please describe in detail the problem. Then we will investigate the possibility and try to fix the problem in subsequent versions.

Thanks,

StarUML Team

2021년 8월 8일 일요일 오후 10시 1분 54초 UTC+9에 jakub....@gmail.com님이 작성:

[Jakub Bobran]

Cosmin explained this quite accurate, so in my opinion there is no need to describe it once again. :)

The most important part of Component Diagram which is missing is 'delegation' relationship.

[StarUML]

Delegation is a connector (not a separate element), so you can use delegation by adding a "Connect" relationship and set the "kind" property to "delegation" (See the 11.2.2 section in UML 2.5.1 specification).

Thanks,

StarUML Team

2021년 8월 9일 월요일 오후 4시 33분 58초 UTC+9에 jakub....@gmail.com님이 작성:

[Jakub Bobran]

While this is true, I cannot set direction of this delegation which when we are talking about interfaces and ports - is quite important. Or maybe as a new user I simply couldn’t find this option?

Jakub.

Wiadomość napisana przez StarUML <sta...@googlegroups.com> w dniu 09.08.2021, o godz. 09:57:

Delegation is a connector (not a separate element), so you can use delegation by adding a "Connect" relationship and set the "kind" property to "delegation" (See the 11.2.2 section in UML 2.5.1 specification).

--
You received this message because you are subscribed to a topic in the Google Groups "StarUML" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/staruml/GcoYELauRLw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to staruml+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/staruml/797a2228-7235-41bd-bc7e-d3a2e43fd07an%40googlegroups.com.

[StarUML]

Double-click on the end of the connector and select "Not-Navigable" in the Quick Edit. Or, uncheck "end1/2.navigable" in the Property Editor.

Thanks,

StarUML Team

2021년 8월 9일 월요일 오후 6시 8분 38초 UTC+9에 jakub....@gmail.com님이 작성:

[Jakub Bobran]

Perfect. :)

Thanks for your help!

To view this discussion on the web visit https://groups.google.com/d/msgid/staruml/37f5fca0-1dee-439a-807b-8b1832b33185n%40googlegroups.com.