Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: andyd on March 12, 2003, 01:49:18 pm

Title: Usecase uses releationships
Post by: andyd on March 12, 2003, 01:49:18 pm

Hi guys,
I've come across some use case diagrams in our organisation which have a "Use" association between use cases.

I was under the impression that this is incorrect syntax and that only <<extend>>, <<include>> and generalisations could be used between usecases, where appropriate.

I dug out one of my older reference books which covers UML 1.1.  This shows <<communicates>> between Actors and Use cases and <<uses>> between use cases.  Am I right in my understanding that this syntax has changed  since 1.1 and that this practice is no longer correct?

Thanks,
Andy.

Title: Re: Usecase uses releationships
Post by: Gary Wong on March 12, 2003, 02:32:48 pm

Hi,

I took a Use Case course last year, and they mentioned this change (although I don't remember the exact UML version that took it out and added generalization).

Check out www.uml.org if you need to find proof of the change.  I couldn't access the 'vault' though to see which spec made the change.

According the the Use Case instructor, though, it didn't necessary clear up the confusion as people are still unsure how to use the new types.

Gary

Title: Re: Usecase uses releationships
Post by: PhilR on March 12, 2003, 06:22:56 pm

Hi Guys,

Yes the <<uses>> stereotype is not part of the UML 1.4 spec.  It has been replaced by the <<includes>> stereotype.  Note the worst thing you can do with a standard is keep changing it.

Simple solution to confusion over <<extend>> and <<include>> - don't use them ;-)

PhilR

Title: Re: Usecase uses releationships
Post by: andyd on March 13, 2003, 03:22:26 pm

Thanks Guys,
I think I'm happy with the use of the new stereotypes.  I just wanted to verify my concerns about the old syntax before getting it corrected.

Andy.