A rule is known or it is not. A ‘best practice’ is applied or is not. But if it is not applied, is it because it is not applicable?
You must present the results of your initial Cobol analysis and of course, you want them to be as most relevant as possible in order to prove their value to the project teams, providers, stakeholders, etc.
This requires defining a Quality model – a set of rules and levels of severity – that allows the rapid identification of the most costly and dangerous ‘bad practices’. Obviously that would be a failure if you point at a violation to a ‘best practice’ which is not one – as for example, the use of SQL code (see our last post).
What are the rules you can use or not? What critical thresholds should you choose? How to adjust the Quality model in a Sonar Quality profile for your Cobol applications?
We will show in this post how to set up your own Quality model, using a Sonar View and a very useful widget. Continue reading