Browse violations

After defining the logical architecture, mapping scanned source code to the logical architecture and defining rules in the logical architecture the possibility to check if the defined architecture has violations is available.

This can be done in the browse violations screen (figure 1). The goal of this screen is to validate the project and to see if any violations have occurred. Additional features are:

The screen can be opened through “menu -> Validate -> Validate now” or by pressing the “validate now” icon () in the toolbar

Note: When storing the workspace the violations won’t be stored. The violation history points are experimental and unwanted behavior can occur.


 Browse violations screen

Explanation of the components:

  1. When this button is pressed, the system will check if there are violations on the defined rules.
  2. When this button is pressed, the last known violations will be shown to the user. The violations will be shown in area 7.
  3. When this button is pressed, the system creates a history point of the last known violations. When the violations are saved the system will disable the button. For saving the violations you need to add a description of the violations.
  4. This table contains all the created/available history points. After clicking on a row, the system will show the violations that are saved in that point. The violations will be shown in area 7.
  5. When this button is pressed, the system will remove the selected history point in area 4.
  6. This panel shows information about the amount of violations. It shows the total violations, the violations shown this moment and the amount of violations per severity.
  7. This table shows all the violations. The violations can be sorted by clicking on the headers, e.g. ‘From’. If you want more information about a violation select the row of the specific violation. The information will be shown in area 8.
  8. This panel shows information about the selected of the selection violation in area 7.
  9. With this button the code viewer can be used to see the exact piece of code which is responsible for the violation. (see the code viewer chapter)
  10. With this checkbox the filter can be turned on or off.
  11. When this button is pressed it will open the Filter dialog (see the filter dialog chapter).
  12. This is an on screen filter to switch between all kinds of dependencies, only direct dependencies or only indirect dependencies. These only work when the checkbox of area 9 is selected.