Architecting and designing : UML 2.0 Lite : UML models : Packages : Moving UML definitions and diagrams between packages
  
Moving UML definitions and diagrams between packages
To move UML class and Use Case definitions between packages, and all UML diagram types between packages, drag and drop the items within the UML tab of System Architect’s browser.
Moving definitions: UML Class and Use Case “classifiers”
You may move classes and Use Cases from one package to another within the UML tab of System Architect's browser, using standard Windows drag and move techniques:
1 In System Architect’s browser, select one or more classifiers.
2 Drag the items onto the destination package. System Architect displays a message confirming the move.
The items moved will still exist on all diagrams that they were present on, however their ownership package will change. Relationships that the moved items have to other classifiers are maintained.
What cannot be moved
You cannot move:
components or nodes between packages
objects, which instantiate classes (and are represented on a Sequence, Collaboration, or Class diagram); instead, move the owning class
a state that represents a class (and is represented on a state diagram); instead, move the owning class.
Example
For example, if class Reception of package Reservation_System is associated with class Reservation (of package Reservation_System), and class Customer is moved to the Human Resources package, then class Customer will still be associated with class Reservation.
Class diagram before class reception is moved
Class diagram after class reception is moved
Moving diagrams
Any and all UML diagram types may be moved between packages. You may use standard Windows techniques to select a diagram in the UML tab of the browser, and drag/move it to another package. The definitions underlying the symbols on the diagram are not moved. They must be specifically moved themselves.
Example
For example, if a Class diagram exists within the package Reservation_System, and it is moved to the package Human_Resources, the classes on the diagram will still belong to the original Reservation_System package until they are themselves moved to the new package.
See also
Packages