Help with my first Use Case Diagram

[emblem]

Derek,
what I do is the following: from the UC I create a new package UC Realizations which holds (normally) a 1:1 copy of the UC as Collaborations with a Realize relationship between (Collab--<<realize>>-->UC). I have a Transformation template to create this automatically. Each Collaboration I set as composite. This creates a diagram inside which opens when the Collab is dbl-clicked. Also I put new diagrams (Sequence, Collab, State, etc.) as sub-diagrams inside. The most important of which is a Robustness diagram (see Google; use a Class Diagram for that). It gives an MVC overview over the realization of the corresponding UC. Try understanding this concept first before going into class/domain modeling in depth.

Hope this gets picked up even though I'm responding to an old post.

Based on some limited experience using Rational Rose years ago, I'm following the approach you outline above. I have some questions about it, though.

When adding boundary, entity, and control icons to a collaboration/communication diagram these are placed under the same composite Collaboration element. I thought of consolidating these into type-specific packages (Boundaries, Controls, Entities) in order to "reuse" them. But then, in trying to shallow-copy an existing diagram, I came across the fact that these icons are actually objects and not classes. So, does packaging them and trying to "reuse" them on other diagrams actually make sense, or should I just have multiple instances throughout the different collaborations? Or, should I be creating these as instances of a defined class?

Does this make sense?