Paul Oldfield wrote:
> fork and join. The link between the fork and the Evaluation > activity state is decorated with " *[ for each candidate ] ". I also agree with Paul on this point. The only issue I would raise is that the discussion is about a *collection* of tools: prior to the fork, it might help to explicitly model (even a note would do) that a collection goes into the fork, the process then iterates over the collection members, and the collection is then subjected to the evaluation afterwards. Not sure if these two cents help, but I sensed that there was some "implied information" in the discussion to this point. Have a good weekend, jwb James Bielak, Consultant Greenstone Consulting Requirements Acquisition and Management http://www.greenstoneconsulting.com ************************************************************************ * 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 *************************************************************************
