Inconsistencies
View
The Inconsistencies View lets you view and manage inconsistencies between a Concern
Graph and the underlying source code.
At the top of the view, a table list the different inconsistencies present
in the concern. Left-clicking on an inconsistency displays a tree representing
the inconsistent information. Right-clicking on an inconsistency allows you
the repair the inconsistency. Repairing an inconsistency
has different consequences based on the type of inconsistency. There are three
types of inconsistencies:
-
Missing domain inconsistency.
The domain element in this inconsistency does not exist in the source code.
Repairing will cause the information to be removed
from the Concern Graph.
-
No relation inconsistency.
The relation does not exist in the source code. Repairing
will cause the information to be removed from the Concern Graph.
-
Mismatch inconsistency. This
inconsistency represents a general query, such as "A.m() calls ALL". In this
case, the range representing ALL in the Concern Graph differs from the code.
Repairing will synchronize the range in the Concern
Graph to the one in the code.
The tree at the bottom of the view represents information in a way similar
to the Projection View, and supports the same actions.
However, inconsistent elements will be marked as such:
Invalid element. The element
does not exist in the source code.
Missing element. The element is
present in the source code but missing in the Concern Graph.
Extra element. The element is
present in the Concern Graph but not in the source code.
On the tool bar, clicking on the repair all icon
will repair all inconsistencies in the view. Clicking on the package icon
enables or disables the display of package names in the view.