When John has finished the specification of the application, he gives it to Bob. From the existing application UML definition, Bob defines the application at a lower level.
At this point, Bob breaks the components out into classes and objects.
The class diagram is used to describe the structure of the system by showing the classes, the interfaces, their attributes, their operations and their relationships.

The class diagram is an unsynchronized diagram which means that the user has to add existing elements manually on the diagram to see them.
It is possible to create an element by selecting the type creation tool from the palette and then clicking on the diagram or an element.

A diagram is associated to a package and when the user clicks on the diagram background the element is created under the corresponding package in the UML model.
If the user selects a container, the element will be created under the corresponding semantic element in the UML model.
Tooltip tools are also available to create any kind of elements. So, you have the ability to create elements in a contextual way related to the currently selected elements.
If your pointer is on the diagram background, after a few seconds you should see the following assistant :

If your pointer is on a class the assistant will be :

Creation tools are available in the class diagram for the following types :
| Element | Representation | Comments |
|---|---|---|
| Class | ![]() |
Representation of objects |
| Enumeration | ![]() |
A data type set of values |
| Interface | ![]() |
Contract that implementers agree to meet |
| Datatype | ![]() |
All copies of an instance of a data type are considered as same instance |
| Primitive type | ![]() |
Default data type |
| Package | ![]() |
Organize the model content |
To define a Generic Class, use the direct edit tool:

To define a Binding, use the create edge tool called “Binding” from a Class to a Generic Class.
You may notice that “?” refers to an undefined actual type:

To specify the binding association from the formal to the actual type use also the direct edit tool:

The user can also delete an element (see Diagram editor/Editor tab-bar/Delete element/from model).
The contextual menu Import primitive types can import predefined types libraries from a right-click on the background of a class diagram. This menu allows to import primitives for :
Then, the imported types can be used in the property’s definition.
Another way to import primitive types is just by editing a property on a class (by typing directly on the selected property or by hitting F2) and type the wanted datatype. If it’s a known type, as String for example, the corresponding library is automatically imported : this library is visible in the model explorer when the project dependencies entry is expanded.
The case is not taken into account, so it is possible to type “string” and the “String” datatype of UML Primitive types library will be used.
It is possible to create a feature by selecting the feature creation tool from the palette and then clicking on the diagram or an element.
If the user selects a container, the feature will be created under the corresponding semantic element in the UML model.
Tooltip tools are also available to create any kind of features.
Creation tools are available in the class diagram for the following features :
It is possible to add and edit :
aNewName will update the attribute name.aNewName : SomeType will update the attribute name and will look for the datatype with the given name. If found it will/someName will set the Attribute as derived.=someValue will set the default value of the Attribute.[0..1] will set the multiplicity of the attribute to 0 for the lower bound and 1 for the upper bound.[0..*] will set the multiplicity of the attribute to 0 for the lower bound and unbounded for the upper bound.The user can also delete a feature (see Diagram editor/Editor tab-bar/Delete element/from model).
It is possible to create a relationship by selecting the edge creation tool from the palette and then clicking on a source element and a target element.
The following edge creation tools exist in the palette :
And finally, he can reconnect relationships. It is possible to reconnect the source and the target of any kind of edge in the activity diagram :
It might happen that for some reason you have an Association instance in your package which doesn’t have the proper ends. In that case
the class diagram will show the broken associations as nodes :
!../images/features/class_pics/broken associations Class Diagram.jpg!
You can use the Association tools in the palette (Association, Reference, Composition and Aggregation) to re-attach the Association to a classifier.
As the diagram is unsynchronized, the user needs to add manually the elements already existing in the semantic model that should appear on the representation.
It is possible to add existing elements by :
The following elements can be added on a class diagram :
The user can see that an element is not coming from the current package :
And finally, he can remove an existing element from a diagram. In this case the element is only deleted from the representation but it is not removed from the UML model. This Remove tool exists in the Existing elements section in the palette (
see Diagram editor/Editor tab-bar/Delete element/from model).
In the class diagram a contextual action is available to show on the diagram the element related to the selection.
The add related elements action is available from :
In the class diagram, it is possible to edit the elements labels (
see Diagram editor/Editor main graphical area/Direct edit). This actions allows to edit :
UML in colors is an object modeling technique proposed by Peter Coad, Eric Lefebvre, and Jeff De Luca in a series of articles in 1999.

An Archetypes layer is available in the UML Designer class diagram.

When the layer is selected, new tools are available in the palette :

The modeling in color patterns and strategies are built around the idea of class archetypes.

It exists four different kind of archetypes :
The Domain Neutral Component (DNC) is the common pattern applied with the UML in colors technique.

To create an archetype in a class diagram just select an archetype from the palette of the tooltip.
The archetypes are stored in UML model as stereotyped classes.
To change an existing class to an archetype just selects the tool from the palette and the existing class. The stereotype of the selected archetype is applied on the class which is colored.
UML in colors examples are available from Eclipse menu File > New > Example… > UML > Uml in colors.
For more detailed explanation on UML in colors have a look to Peter Coad’s website.
This diagram is not yet implemented.
The object diagram is used to describe the structure of the system by showing the objects at a specific time.

The object diagram is an unsynchronized diagram which means that the user has to add existing elements manually on the diagram to see them.
It is possible to create and delete instances in the object diagram.

It is possible to create an instance by selecting the creation tool from the palette and then clicking on the diagram or an element. A diagram is associated to a package and when the user click on the diagram background the element is created under the corresponding package in the UML model.
If the user selects a container, the element will be created under the corresponding semantic element in the UML model.
Tooltip tools are also available to create instances.
It is possible to set a default value to an instance property by selecting the tool from the palette and then clicking on an instance. This tool opens a wizard to ask the user to select a property of the selected instance type.
As the diagram is unsynchronized, the user needs to add manually the elements already existing in the semantic model that should appear on the representation.
It is possible to add existing elements by :
Only instances can be added on an object diagram.
The user can see that an element is not coming from the current package :
The user can also delete an instance (see Diagram editor/Editor tab-bar/Delete element/from model).
In the class diagram a contextual action is available to show on the diagram the element related to the selection.
The Add related elements action is available from :
In the class diagram, it is possible to edit the elements labels (see Diagram editor/Editor main graphical area/Direct edit). This actions allows to edit :
Bob describes the application behavior thanks to Statemachine diagrams and Sequence diagrams.
The statemachine diagram is used to represent the different states and transitions of a system.

The statemachine diagram is a synchronized diagram which means that any elements existing under a statemachine in the UML model will be visible automatically in the statemachine diagram.
It is possible to create statemachine elements by selecting the creation tools from the palette and then clicking on the diagram or an element. A diagram is associated to a package and when the user click on the diagram background the element is created under the corresponding package in the UML model.
If the user selects a container, the element will be created under the corresponding semantic element in the UML model.

Tooltip tools are also available to create any kind of elements.
Creation tools are available in the statemachine diagram for the following types :
The user can also delete a statemachine element (see Diagram editor/Editor tab-bar/Delete element/from model).
It is possible to :
In the statemachine diagram, it is possible to edit the elements labels (see Diagram editor/Editor main graphical area/Direct edit). This actions allows to edit any statemachine elements labels.
The sequence diagram is used to show how processes operate with one another and in what order.

The sequence diagram is a synchronized diagram which means that any elements existing under an interaction in the UML model will be visible automatically in the sequence diagram.
It is possible to create:
The user can also delete an element (see Diagram editor/Editor tab-bar/Delete element/from model).
It is possible to reorder the interaction elements :
This tool updates the semantic element positioned in the interaction fragments list. If a representation is open, the view corresponding to the moved element is automatically updated.
In the sequence diagram, it is possible to edit the elements labels (see Diagram editor/Editor main graphical area/Direct edit). This actions allows to edit any interaction elements labels.