The Omnext® Portal has been updated with a new quality model: the Health Check. Following a diagram that visualizes the source code as a city map, violations in the system can be shown. Just like a real-life city, the map contains different districts and buildings. The higher the building, the more violations the system contains. The city map shows the progress of the Standards & guidelines that are of relevance to you, our client. When the portal will be delivered for the first time, the standards and guidelines will be selected by Omnext. After that standards and guidelines can be configured by the client him- or herself.

Health Check widgets

In the picture shown above you can see an example of the city map. The different widgets that are shown above relate to the object that is selected in the ‘tree view’ on the left side of the screen. The Unresolved issues are issues that have been in the source code since the last analysis. The New issues are violations that have appeared in the time between the two analyses, Resolved issues are issues that are solved in between the analyses. When looking at the widget ‘Progress’, it shows the relationship between the resolved, unresolved and new issues. A positive number means that more issues have appeared than have been solved. A negative number means the exact opposite.

Health Check details


The details tab shows us exactly where the different violations can be found in the source code. The list shows the standards and guidelines that have been selected beforehand and which were marked as relevant. Every rule is showed separately and gives a number of violations which are either resolved, unresolved or new.

The list below shows the separate objects with violations. By using the Relevance column priorities can be set on which issue to resolve first. Relevance is determined by the number of violations (sometimes size of the violations matters too), the priority of the violation, the volatility (how many times the object has been changed) and the Afferent coupling (how many times the object is invoked).

The column Toxicity shows how many of the selected standards and guidelines are violated. Remaining columns show the results of the standard and guideline rules. When no violations are detected on an object a green checkmark is shown. When violations are detected the shown number gives an actual value of violations. In the list the limits of the rule are shown as well. I.e. AvoidLongUnits gives 67 as the number of lines of code. The given limit is 50, therefore it violates this rule.

Standards and guidelines

Health Check Dashboard

The Standards & Guidelines tab, but also other tabs which show Standards & Guidelines i.e. Cloud Readiness, contains rules that can be selected for the Health Check quality model. Other than selecting individual rules, priorities can be selected as well. In this case violations that belong to the different priorities are shown in the Health Check.


Share This