Packaging related use cases looks neat to me. However, how would I present
"Maintain Employee Records" in the main use case diagram? Or would I be
forced to place all the real use cases in the main use case diagram? In
this case, the diagram would be cluttered (when I start putting in other use
cases as well) which is what I want to avoid.
> -----Original Message-----
> From: Michael Hill [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 29, 2000 11:17 PM
> To: CHIAM CHOON YEE, LSD; ''[EMAIL PROTECTED] ' '
> Subject: RE: (ROSE) Use Cases and UC Diagram
>
> Hi,
> If "Maintain Employee Records" were a Use Case, then you would have more
> than one primary flow(Basic Flow) and several alternate flows for each
> basic
> flow. That isn't recommended by RUP. That Use Case would be too big and
> hard to follow and use.
>
> The "Maintain Employee Records" is more of a package in the Use Case View.
> The real Use Cases are "Update Records" (Update Employee Records), "Delete
> Records" (Delete Employee Records), "Add Records" (Add Employee Records),
> and "View Records" (View Employee Records) which are placed in the package
> "Maintain Employee Records".
>
> Michael Hill
> Consultant
> Solutech, Inc
>
>
> -----Original Message-----
> From: CHIAM CHOON YEE, LSD
> To: '[EMAIL PROTECTED] '
> Sent: 11/29/00 7:59 AM
> Subject: (ROSE) Use Cases and UC Diagram
>
>
> From what I understand, Use Case Diagram captures all the use cases
> which
> describes the functionalities of the system in relation to the system.
> Usually, I would want to keep the main use case diagram uncluttered,
> simple
> and neat. However, when I do that, I lose the details.
> As an example, I use "Maintain employee records" as a use case. In this
> use
> case, I actually have
> * update records
> * delete records
> * add records
> * view records
>
> Is there any good way to layer the use cases conveniently? That is, I
> click
> into one particular use case, if there is a layer of use case diagram
> below
> it, the diagram will be blown up?
>
> Thanks.
>
>
> This communication contains confidential or privileged information. If
> you
> are not the intended recipient, please notify us IMMEDIATELY that you
> have
> received it and destroy it. We are not liable for any unauthorised
> sending
> of or interference with this communication.
>
>
> ************************************************************************
> * 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/products/rose/usergroups/rose_forum.jtmpl
> * Other Requests: [EMAIL PROTECTED]
> *
> * To unsubscribe from the list, please send email
> *
> * To: [EMAIL PROTECTED]
> * Subject:<BLANK>
> * Body: unsubscribe rose_forum
> *
> ************************************************************************
> *
>
>
This communication contains confidential or privileged information. If you
are not the intended recipient, please notify us IMMEDIATELY that you have
received it and destroy it. We are not liable for any unauthorised sending
of or interference with this communication.
************************************************************************
* 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/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
