"Dunnavant, Todd" wrote:
>
> The 1998 comments by Terry were due to the fact that Rose 98 didn't support
> the correct UML symbols between use cases, so we had to kludge things.
> "Correct" UML represents include/extend using stereotyped dependency
> relations. Rose 2001 supports this notation.
>
> Todd Dunnavant
> Rational Software Corporation
There are actually two bar bets here. In use case diagrams:
1. Uses/extends is the same as the newer include/extend.
2. Unidirectional association is the relationship to which these
stereotypes should apply.
I'm not trying to pin anything on Terry Quatrani -- she's my favorite
author on the UML.
Quatrani actually uses generalization with uses/extends for Rose 98, and
the unidirectional association with includes/extends for Rose 2000. Did
2000 support dependency between use cases?
Setting aside the question of what is standard according to authority,
the question is: What is right and why?
Here are three options for which relationship "goes with" include and
extend stereotypes:
1. generalization (solid line, closed arrow)
2. dependency (dashed line, open arrow)
3. unidirectional association (solid line, open arrow)
-Eric
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
