There's definitely an ArgoUML bug here. That wasn't the point of my message. It was to point out that you might not be modeling what you intend to model, potentially hindering the model's ability to convey the information that you desire. A Generalization arrow points from more specific to more general, thus the normal form of a generalization for zooming would be: ZoomIn ----> Zoom Tom
-----Original Message----- From: Mark Fortner [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 4:02 PM To: [email protected] Subject: Re: [argouml-users] Strange Advice From Critics My first thought was that I was drawing the diagram improperly and that perhaps (as you point out) the arrows might be pointing in the wrong direction. My thought is that use-cases that exhibit greater levels of specificity would radiate rightward from the more generic "Zoom" use-case, in the same way that you might outline the requirements in a document. Zoom - Zoom In - Zoom Out However, either way that I draw it I still have the same problem. Mark On 4/19/07, Tom Morris <[EMAIL PROTECTED]> wrote: Both ASCII art and UML can be a little tricky to interpret, but it seems possible to me that you've got the generalization arrows going opposite the way you intend and, perhaps as a result, you've got the associations going to the wrong place. What do you think about drawing it like this? ___ UseCase 'ZoomIn'___ / \ Actor 'User' -< |--> UseCase 'Zoom' \___ UseCase 'ZoomOut'__/ where the lines on the left are two associations from User to ZoomIn & ZoomOut and the lines on the right are generalization from those two use cases to the Zoom use case. Alternatively, you could have the use case Zoom include the sub use cases, depending on your exact semantics. Either way your still going to get an unwanted critic firing though. It looks like it doesn't think being used via Include, Generalize, Extend, etc to be enough consider an element not being orphaned. Tom -----Original Message----- From: Mark Fortner [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 12:30 PM To: [email protected] Subject: [argouml-users] Strange Advice From Critics I've been trying to use the critics as a way of insuring that my model is complete. However, when creating use case diagrams I've noticed that the critics often provide me with feedback that doesn't make sense. For example, let's say you want to create the following use-cases Actor -- (Zooming) --> (Zoom Into Rectangular Selection) --> (Zoom In By Increment) --> (Zoom Out By Increment) To create the first generalization of Zooming (Zoom Into Rectangular Selection), I click the Zooming use-case and drag the generalization arrow at the top of the use-case. When I release the mouse, the new use case is created, and I enter it's name directly into the use-case ellipse. However, when I do this I get feedback telling me that I need to "Add Associations" to the usecase even though in my estimation I just created the association that I wanted. Am I missing something? Regards, Mark
