> Question for the (UML) gurus:
>
> Imagine that you're supposed to model an activity diagram for the
> following flow:
> One first selects tool candidates to evaluate. As soon as this selection
> is done, evaluation process starts. Evaluation process stands here for
> applying the same technique for each tool from the selection (theses
> evaluations are not mutually synchronized). As soon as all the tools
> from the selection are completely evaluated, decision process starts in
> order to select the best candidate from the selection.
>
> Clearly the diagram starts with some "Select Tool Candidates" activity
> and ends up with some "Decide on the Tool" activity. The tricky section
> comes with evaluation chain. One could model this by "Evaluate Tools"
> activity, where could be specified that all the tools from the selection
> are being simultaneously evaluated applying the process P for each, but
> how to express this visually?
> Technically viewed, after the "Select Tool Candidates" activity several
> (one for each tool from the selection - the number is not fixed)
> instances of "Evaluate Tool" activity are *instantiated*. The flow goes
> on first after all of these instances arrive at the end of their life
> cycle.
>
> I thought on stereotyped transition or even stereotyped fork, but I
> guess this is not the way for non technical readers.
>
> Any ideas?
Ciao Vlado,
in UML 1.4 this problem is solved by the Dynamic Invocation for action
states (see OMG specification for details). Unfortunately Rose does not
support it. U must use some "faked" notation, e.g.:
- use "Evaluate Tools" and describe it verbally (as U mentioned before), or
- decorate "Evaluate Tool" action state with <<multiple>> stereotype and
describe the stereotype semantics separately, or
- create one "Evaluate Tool" action state. Copy it several times (e.g. 3)
and place those copies into one horizontal line. Place one synchronization
over the action states and one synchronization below. Connect all action
states with "surrounding" synchronization states. Then place ellipsis
("...") next to the action states, indicating that there may be more of the
action state executions. This is a notation similar to the additional
children for class generalization. I think this notation is understandable
also for non-technical readers.
- ...
Regards,
Rado1.
--
Radovan Cervenka | [EMAIL PROTECTED]
Whitestein Technologies | www.whitestein.com
Panenska 28 | SK-81103 Bratislava | Slovak Republic
Tel +421(2)5443-5502 | Fax +421(2)5443-5512
--
If you are not the intended recipient of this email,
you are not authorized to make any use of it;
please delete it and notify us by return email.
Thank you.
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Post or Reply to: [EMAIL PROTECTED]
* Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
* http://www.rational.com/support/usergroups/rose/rose_forum.jsp
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
* To: [EMAIL PROTECTED]
* Subject: <BLANK>
* Body: unsubscribe rose_forum
*************************************************************************
