This menu entry creates a blank use case diagram, and selects that diagram in the editing pane. If a package is currently selected, then the use case diagram will be created within that package. This means that it will be shown within the package on the explorer hierarchy (under Package-centric view) and model elements created on the diagram will be created within the namespace of the package. This does not only apply to a package, but also to a class, interface, use case, etc.

	Tip
	This does not prevent model elements from other namespaces/packages appearing on the diagram. They can be added from the explorer using Add to Diagram from the button 2 pop-up menu.

This menu entry creates a blank class diagram, and selects that diagram in the editing pane. If a package is currently selected, the class diagram will be created within that package. This means that it will be shown within the package on the explorer hierarchy (under Package-centric view) and model elements created on the diagram will be created within the namespace of the package. This does not only apply to a package, but also to a class, interface, use case, etc.

	Tip
	This does not prevent model elements from other namespaces/packages appearing on the diagram. They can be added from the explorer using Add to Diagram from the button 2 pop-up menu.

This menu entry creates a blank sequence diagram, and selects that diagram in the editing pane. It also creates a Collaboration UML element, which is a container for the elements shown on the new diagram. If a class is currently selected, a sequence diagram and a collaboration will be created that represent the behaviour of that class. This means that the created elements will be shown within the class in the explorer hierarchy (under Package-centric view) and model elements created on the diagram will be created within the namespace of the collaboration. A sequence diagram may not only represent the behavior of a class, but also of any other classifier, such as interface, use case, etc. It is also possible to make sequence diagrams for an operation.

This menu entry creates a blank collaboration diagram, and selects that diagram. It also creates a Collaboration UML element, which is a container for the elements shown on the new diagram. If a package is selected when this menu item is activated, the collaboration diagram will be created within a collaboration within that package. This means that it will be shown within the collaboration within the package on the explorer hierarchy (under Package-centric view) and model elements created on the diagram will be created within the namespace of the collaboration within the package.

	Tip
	This does not prevent model elements from other namespaces/packages appearing on the diagram. They can added from the explorer by dragging or by using Add to Diagram from the button 2 pop-up menu.

This menu entry creates a blank statechart diagram associated with the currently selected class, and selects that diagram in the editing pane. It also creates a Statemachine UML element, which is a container for the elements shown on the new diagram.

Statechart diagrams are associated with a model element capable of dynamic behavior, such as a classifier or a behavioral feature, which provides the context for the state machine it represents. Suitable model elements are e.g. a class, an operation, and a use case. If such element is not selected at the time the New Statechart Diagram menu is activated, then an unattached statemachine is created. To obtain a well-formed UML model, you have to set the context of the statemachine on its details pane.

This menu entry creates a blank activity diagram associated with the currently selected class, and selects that diagram in the editing pane. It also creates a ActivityGraph UML element, which is a container for the elements shown on the new diagram.

Activity diagrams are associated with a model element capable of dynamic behavior, such as packages, classifiers (including use cases) and behavioral features. Suitable model elements are e.g. a class, a use case, an operation, and a package. If such element is not selected at the time the New Activity Diagram menu is activated, then an unattached ActivityGraph is created. To obtain a well-formed UML model, you have to set the context of the ActivityGraph on its details pane.

This menu entry creates a blank deployment diagram, and selects that diagram in the editing pane.

	Tip
	Model elements from other namespaces/packages can be added from the explorer by dragging or by using Add to Diagram from the button 2 pop-up menu.