This just shows there are lots of ways to skin the cat. Do what is easier and adds max clarification.
********************************************************
R a t i o n a l
the software development company(tm)
Todd Dunnavant
Technical Lead, IBM End User Programs
Office Phone #: (281) 431-8751
Fax Phone #: (281) 431-8791
E-mail address: [EMAIL PROTECTED] < mailto:[EMAIL PROTECTED]>
Rational's Mission: "To ensure the success of Customers who
depend on software development and deployment."
********************************************************
-----Original Message-----
From: Eric D. Tarkington [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 1:17 PM
To: Dunnavant, Todd
Cc: Frank Yang; Rose_Forum (E-mail)
Subject: Re: (ROSE) How is Xor-association represented in Rose?
Todd, thanks for the clarification, but why not just insert a note with
"XOR" in it, and link the note to the associations? Admittedly, this is
just a kluge, but it is a simpler kluge, no?
-Eric
> Subject: RE: (ROSE) How is Xor-association represented in Rose?
> Date: Wed, 8 Jan 2003 12:51:42 -0500
> From: "Dunnavant, Todd" <[EMAIL PROTECTED]>
> To: Frank Yang <[EMAIL PROTECTED]>, "Rose_Forum (E-mail)" > <[EMAIL PROTECTED]>
>
> Frank, you are headed in the right direction and what I said was a bit
> misleading. I would use the note link relation (the dashed line)
> to tie the associations together. Then, you need to go to the spec
> dialog for one of the associations, choose the Detail tab, and
> define the association-level constraint as XOR. This will show up on
> your diagram as {XOR}. I then would drag this on the diagram
> so that it appears as a label next to the note link.
>
> Sorry for the misinformation!
