A class view is used to design the classes and may contain classes, class instances, states, activities, class diagrams, object diagrams, sequence diagrams and collaboration diagrams in any order :
A class view may have an associated deployment view, in this case the menu of the sub-classes propose a shortcut to create an artifact in the associated deployment view (refer to class menu).
The menu appearing with a right mouse click on a class view in the browser is something like this, supposing it is not read-only nor deleted :
The menu entry select associated deployment view is only present when the class view has an associated deployment view, this feature allows to quickly associate an artifact to a class (see class menu). The menu entry new stereotype is only present when the class view is placed inside a profile.
The stereotype of a class view doesn't have a special meaning for BOUML.
As you can see, the association with a deployment view is made through this menu.
The editor button visible above and associated here to the description, allows to edit the description in an other window, or to call an external editor (for instance Xcoral) specified through the environment dialog. Note that this external editor have to create an own window, its parameter is the pathname of the file containing the description, its execution is done in parallel with BOUML which looks each second at the file contents to get the new definition until the dialog is closed (I do not like very much this polling but this works even QT isn't compiled with the thread support).
This setting allows to set a default visibility at the UML level for the attributes, relations and operations of the classes defined in the class view. default means that the visibility of the upper level is followed (which itself may be default etc ... up to the project level). When you create a new class view the visibilities are set to default.
This dialog allows to specify how the class view's diagrams must be drawn by default.
The menu entry delete is only present when the class view is not read-only.
Delete the class view and all its children, and all the representation of them in the opened diagrams. After that it is possible to undelete them (from the browser) until you close the project : obviously the deleted items are not saved !
It is possible to put a lock on a class or an artifact. A locked element cannot be modified editing it nor roundtriped, and there is no code generation for it. When you put/unput a lock on a class it is also put/unput on its sub classes and on the associated artifact and all the other classes associated to this artifact and their sub classes. When you put/unput a lock on an artifact it is also put/unput on the associated classes and their sub classes. It is also possible to put/unput locks recursively from a package, a class view and a deployment view.
To generate the C++/Java/Idl code of all the sub-items. Refer to C++ generator, Java generator and Idl generator for more details.
The menu entry tool is present in case at least a plug-out may be applied on the class view.
Only present when the class view has an associated deployment view, select it as you do this manually, except that you do not have to search it !
Previous : use case view
Next : component view