Kiuwan November update

november update

Did you really think we weren’t able to come up with something great after our successful October release?

If so, your were seriously wrong.

Take a look at some interesting updates you’ll find starting Wednesday November 4:


Your apps tree on the left… is now an actual tree!

So it is! You can still have your flat list of applications on the left as usual, but now you can group them by any of the defined portfolios.
Your summary data, defects, action plans, etc. will be aggregated when selecting a portfolio in the tree. When you select an application you will get its details the same way you get them now. So this is now a more clever, faster way to see your results.
Now for example you can analyze different modules of an application separately and group them all in a solution portfolio. This way you have analytics of each module and the ones for the solution in the same place.

New default porftolios in your filters box: Language & Quality model

We want you to get great results literally seconds after you make an analyisis. That’s why we are adding Language & Quality model to your filters box.
These portfolios are automatically populated based on the language and model info coming directly from the analyses. Kiuwan does it for you so you can use the information immediately.

> This article goes deeper into the Kiuwan porfolios organization



‘Activity’ view goes global

Until now, you only had ‘Activity’ for providers. Now you’ll be able to check out activity for any porfolio: Provider, Country, Business Value or any other of your own.
It will make the ‘Activity’ section even more useful, won’t it?

Security analysis improvements

We are continuously improving the depth and breath of our security analysis. With this release you can expect higher accuracy in all the languages with tainting propagation rules, in particular Java, C# and Cobol.
Stay tuned for new updates on this area: the security of your applications is as important for us as it is for you.

Natural joins our supported languages family

We are starting out with 33 rules that check for interesting issues like:
  • Avoid writing multiple sentences in one code line.
  • Avoid debugging write in on-line programmes.
  • Avoid deep nesting in flow control sentences (IF, FOR, REPEAT, DECIDE FOR, DECIDE ON).
  • Avoid variable declarations (records) too deeply nested.
  • Avoid too complex programmes (in cyclomatic complexity, number of different execution ways).
  • Certain code structures (LDA, PDA, programs or subroutines) should not exceed a maximum number of lines.
  • Try to limit the number of options in DECIDE statements.
  • Limit the copy codes to be used.
  • Avoid commented code.
  • Avoid unused data areas (local, global or parameter) in system.
New languages will be added soon.