> Hi, Les. > > Would using a naming convention help? That is, use the same name for the use > case and the transition. > > I say transition because I'm not sure what the association between a state > and a use case would be. Ah, would the states be the pre and post-conditions > of the use case, by any chance? Again, a naming convention might help -- > i.e. referring to the states by name in the use case. > > A little awkward, but should do most of the job. >
Well using the same name for the activity/state and the use case is part of the solution. The states are the pre and post-conditions in the use case, yes. The activity resides between them. Anyway I soplved the problem. Simply don't use Rose's state/activity diagram editor for drawing state/activity diagrams. Use its use case/class diagram editor instead and the problem is solved. The other benefit to doing it this way is that your states and activities are located in the same place in the diagram after you close and re-open your diagram, unlike typical Rose activity diagrams. Les. ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag ************************************************************************ * 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 *************************************************************************
