Page History
...
Read the following definitions to get familiar with different change types.
Addition change Anchor #additionchange #additionchange
If an element has been added to a compared project version, an addition change occurs.
Deletion change Anchor #deletionchange #deletionchange
If an element has been removed from a compared project version, a deletion change occurs.
Modification change Anchor #modificationchange #modificationchange
If an element property in a compared project version has been modified, a modification change occurs.
Tip |
---|
If the IsAbstract property value of a class in the base had the default value false and the same property value in a compared project version has been changed to true, a modification change occurs. |
...
- Addition modification change that occurs when a value is added to a property.
- Deletion modification change that occurs when a value is removed from a property.
- Replacement modification change that occurs when one value is replaced with another. This type of modification change occurs only for properties that have multiplicity less or equal to 1.
Movement change Anchor #movementchange #movementchange
If an element owner has been changed in a compared project version, a movement change occurs.
...
Tip |
---|
Another case of the movement change is when an attribute or an operation that has been owned by class A in the base, becomes the attribute or an operation of class B in a compared project version. |
Order change Anchor #orderchange #orderchange
If the order of elements has been changed in a compared project version, an order change occurs. Order changes can occur on elements such as attributes, operations, and other ordered elements. Even if a single element in a collection has changed its place, the order change is applied to the entire collection.
Since an element can have several ordered collections, several order changes can occur on a single element.
Tip |
---|
Let's say class A has attributes a, b, and c in the base. The attribute c has been moved up and placed above attribute a in a compared project version. This means that the order of attribute collection in class A has changed in the compared project version. This is a case of the order change. |
...
Warning |
---|
Property names must be written in camel case, for example, ownedAttribute, ownedElement, and so on. |
Dependent change
In some cases, changes depend on other changes and are called dependent changes. Anchor #dependentchange #dependentchange
...
Tip |
---|
Let's suppose there is an attribute type change in a compared project version. An old type has been deleted and a new type has been added to the compared project version. In this case, three changes occur:
The modification change depends on the addition change, and the deletion change depends on the modification change. |
Anchor | ||||
---|---|---|---|---|
|
Diagrams that are loaded and contain changes are considered to be directly modified by the user. In the Environment Options dialog, you can select whether to analyze the changes in all diagrams in the model (All changes) or limit your investigation to diagrams that were loaded (open) when the changes were made (Direct Changes).
...