This article will take you through the most important elements of a use case driven UML model, and introduce you to a variety of tips and tricks that we've developed as we've taught UML modeling workshops with Rose. There are a number of UML diagramming elements, but when following a use case driven style, five of them have proven to be the most important. Class diagrams, which form the static portion of your UML object model. We'll be explaining these different elements of a UML model, how they relate to each other, and how they fit together within Rose. Organize your models into packages Packages, represented by tabbed folder icons within the Rose browser, and on the use case diagramming palette, are used as containers for other UML modeling elements.
Packages can contain both use cases and classes.
In a use-case driven process, both robustness analysis diagrams and sequence diagrams are done for each use case, and are organized in this manner in the Rose broswer. Rose allows import and export of packages. This becomes especially significant when working in a multi-user, configuration controlled environment. Keep in mind that you can't import and export the top level packages such as Logical View or Use Case View, so it's a good idea to keep your diagrams, classes, and use cases in subpackages. This organization facilitates partitioning of work across a team of developers.