Sparx Systems Forum
Enterprise Architect => Uml Process => Topic started by: RainerQ on July 22, 2010, 08:36:12 pm
-
Hi
is there a possibility in EA to define a relation ship between a Send-Signal (activity) and Receive-Signal (activity) which are located on different activity diagrams?
Thanks for hints and help.
Regards
Rainer
-
With the appropriate options set, if necessary, you can create any type of relationship between any two items in the model - by placing both on the same diagram and drawing the relationship type you want.
The diagram is NOT the model; it is a VIEW into the model (not withstanding the UML requirement that the activity diagram IS the activity).
HTH,
Paolo
-
Hi Paolo,
thanks for your hint! I think it switched on a other light in one of the EA-rooms I am exploring :)
As in my case, where I want to depict the "myEvent.Set" and "myEvent.WaitOne(...)" behavior, what would you use?
"Trace" or "Information Flow"? Or even something else?
Regards
Rainer
-
[size=18]...[/size]
As in my case, where I want to depict the "myEvent.Set" and "myEvent.WaitOne(...)" behavior, what would you use?
"Trace" or "Information Flow"? Or even something else?
Hi Rainer,
I'll leave it up to the folks who live in the "Real time" world to provide that advice. I move in the more Enterprise level area.
Glad to have helped,
Paolo
-
myEventWait depends on... both temporaly and structurally.
-
... so, what would you use?
Trace or information flow?
Regards
Rainer
-
I think bruce's (sargasso's) answer was "Dependency".
-
yup
-
... between a Send-Signal (activity) and Receive-Signal (activity) which are located on different activity diagrams?...
FWIW
You might want to add a diagram - preserving the logic of your model to date - where you can show this relationship. If these elements are related in some way that matters (i.e. contributes to the overall integrity of the system) then the relationship should be explicitly depicted in your model. Perhaps you will find other instances where relationships span diagrams (or otherwise cross partitions in your model). These could be shown (perhaps grouped) on other such diagrams, which might themselves be packaged together for ease of reference.
Just adding my 0.02 CAD, whatever that's worth these days.
David