|Automatic display of object relationships [message #764398]
||Mon, 12 December 2011 05:00
Registered: December 2011
New to Papyrus and have a question creating a component diagram.
I have two component objects with a dependency link between the two components.
When I create a new component diagram and drag the two components to my diagram
it does not automatically render the dependency between the two objects.
Have this be achieved? Is there a setting or maybe I'm using the wrong type of
|Re: Automatic display of object relationships [message #765205 is a reply to message #764922]
||Tue, 13 December 2011 16:05
>The other nice feature that does not seem to be available is that Component
>1 gets the dependency registered but not Component 2.
>That is component 1 knows it is dependant on component 2 but component 2
>does not know component 1 is dependent on it.
Well, this is given with the native UML::Dependency capability. If Component
1 depends on Component 2 (i.e. Component 1 is the source of the dependency)
than Component 2 participates in the relationship, but does not know
anything about incoming dependencies. Then, you get access to Component2
from Component1 via Component1.classifierDependency.
But if your statement means that Papyrus does not allow to specify those
attributes through the UML section in properties view, you're right. You can
still use those features via the 'Advanced' section in properties view (what
is quite inconvenient). I already filed a bug entry for this. See
"Roelie viviers" schrieb im Newsbeitrag
Thanks for the feedback. You are correct, dragging the dependency in the
diagram brings the supplier+client into diagram also.
Although a nice feature this is not typically what we want when doing
architecture design. We want to re-use existing relationships
between systems and dropping two components on the diagram should give us
all its dependencies.
The other nice feature that does not seem to be available is that Component
1 gets the dependency registered but not Component 2.
That is component 1 knows it is dependant on component 2 but component 2
does not know component 1 is dependent on it.
Powered by FUDForum
. Page generated in 0.01942 seconds