Hi all,
Please be gentle with me, since this is my first post on this forum. I realise this is a hotly discussed topic, but I am interested in feedback on the issue of using diagrams to capture the processing order within Use Cases, particularly Business Use Cases. Given that the steps in a Use Cases are often documented using an Activity Diagram in Rose, it would be true to say that the sequence of events is defined in the Activity Diagram, or perhaps a Sequence Diagram or similar. We are looking at high level Busines Use Cases which effectively would contain and define the order of other Use Cases, which are thus "include"d in the high level one. The question is, since the inclusion of other Use Cases is specified in the steps of the high level Use Case, would not the Activity Diagram representing those steps also contain a reference to "include" those other Use Cases? I am trying to use the Rational approach, and can find minimal documentation describing this issue. Any ideas how we might document such Use Case sequencing? Is the use of Use Case Realization appropriate here (by the way, is there any documentation defining the purpose of Use Case Realizations)? Lastly, does anyone have a clear and precise definition of a Business Use Case vs a System Use Case? Thanks, - Jeremy Ellis (Vutech Pty. Ltd.) ---------------------------- ERG Group -------------------------- The contents of this email and any attachments are confidential and may only be read by the intended recipient. ----------------------------------------------------------------- ************************************************************************ * 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 * *************************************************************************
