The Health Check on your dashboard

The Health Check on your dashboard

The Omnext® Portal is equiped with a management dashboard which shows an overview of the Health Check quality model. The Progress diagram shows the changes in violations in your source code. As explained in the previous article about the Health Check the different standards and guidelines rules that are selected show various results, ranging from number of violations to exact limits for this rule.

When looking at a large amount of violations it can be hard to identify new violations. In this case it is possible to, by clicking on the legenda text, eliminate one or more of the objects.

 

Health Check Dashboard_3

Example: in the dashboard shown above, the Unresolved issues are eliminated. Which gives you a clearer overview of how many resolved and new issues there have been found in your source code.

 

New: A city map to visualize your source code

New: A city map to visualize your source code

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

picture2

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.

 

Stop innovation to reduce security risk?

Stop innovation to reduce security risk?

The acceleration towards digital business has presented CIOs with new challenges. They must understand the goals of the business, quickly identify and assess the associated risks, and communicate the relevant risks to the business in business terms. By outsourcing your software development many of the risks might not be entirely clear. Who is working on what part and how is your security arranged?

The effects of losing control

Less control and overview on for example security issues can become a major problem. Why? The answer is twofold. On the one hand for your customers, relations and your own business. On the other had because of the law. Law makers in Europe are creating laws on data breach. This means that at this moment weak security measurements can not only result in a major fall down in business, a loss of clients and less credibility in the market like it did in the past but nowadays it means that low security measurements can result in high fines and are addressed as criminal offences.
At this time, we cannot deny that digital risks are increasing as newer data sources and technologies are woven into the fabric of the business. As Gartner tells us: ‘As organizations adopt more cloud technology and explore more digital business opportunities, existing risk management strategies and practices become quickly outdated.’ Risks and complexities that should be expected when transitioning to digital business have to be defined, as well as hazards that occur when mitigating new risk management challenges.

Stop innovation?

So should we stop innovation to reduce risks? Should we try and rebuild applications to make the perfect protected piece of software? Our answer is no. You definitely shouldn’t. We are convinced that you should embrace your risks, be aware of them and find your solution in other possible ways: Outlining, risk management, control, monitoring and actionable intelligence.

Become the CIO you want to be

What to do? Organizations must move away from trying to achieve the impossible perfect protections, instead organizations must invest in detection and response. How to identify risks and how to qualify risks. Getting back to the source code can give you immediate insights in how your software is maintained, what the possibilities and risks of your software are. Omnext can help you in achieving this, we can help you to become the CIO everyone wants: the recognized business leader, superstar communicator and facilitator and definite problem-solver.