When using <<include>> or <<extend>> relationships between use cases, somehow it expresses the sequence of the use cases initiated. For example, UC-Maintain Customer can be extended by UC-Search Customer if the user wants to update an existing customer details, equally, UC-Search Customer could be extended by UC-Maintain Customer if at the end of customer search the user wants to edit the customer's info. Now we end up with <<extend>> relationship either from UC-Maintain Customer to UC-Search Customer or the other direction.
Clearly there is a question regarding if it is appropriate to use the <<extend>> relationship above. What I would prefer is not to use <<extend>> relationship at all and create a User Experience diagram to model the navigation path. Even further, I would like to have no any <<include>> or <<extend>> relationship between use cases that can be activated directly by users. Any thought/best practice about this? Thanks Jie ************************************************************************ * 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 *************************************************************************
