I just want to know what is the common practice. In terms of putting
Activity Diagram in Use Case.
And at what level one should specify a Use Case. As I was reading a book on
UML it was dividing a Purchase Order Use Case in 4-5 diff use case like
Placing an Order, Cancellation of order and so on. And in rational few
examples that I had checked they define Use Case for purchase Order as one
Use Case and then specify the activity in documentation.

Thanks Manish




************************************************************************
* 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/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
*
*************************************************************************

Reply via email to