"CHIAM CHOON YEE, LSD" wrote:
>
> 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.
IMO, you probably shouldn't present all details about "Maintain Employee
Records" in the main use case diagram. You would not put all use cases
into the main, either. You can make a very simplified main use case
diagram, create a package corresponding to each of the few use cases in
the main diagram, and put additional diagrams into that package
detailing the relationships with that use case.
-Eric
************************************************************************
* 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
*
*************************************************************************
