Some hints about quality indicators that are worth checking are listed below:
- Default selection of quality rules with the "critical contribution" option set is available in the release notes. Please note that a migrated installation will not automatically benefit from this default selection: you HAVE to perform the selection.
- Naming controls on prefixes must most of the time be adapted:
- OO inheritance controls can be adapted to take into account resources' skill level
- Algorithmic complexity controls can be adapted to take into account resources' skill level and application history:
- Coupling controls can also be adapted to take into account resources' skill level and application history
- Documentation controls - and more specifically the percentage thresholds for comment ratios - can be adapted to take into account application history
- Volume controls are also good candidates for adaptation to take into account application history
- Structured controls are also good candidates for adaptation to take into account an application history
Some hints about quality indicators that may not be applicable in all contexts are listed below:
- "Reuse by Call Distribution" weight and thresholds may not be the same in all contexts as it is more valuable to assess components that are known to be framework components.
For Quality Distributions:
- CAST-delivered Quality Distributions feature multiple parameters to define the limit values that drive the distribution in Categories. Expert users can update these values to better detect quality drifts. Other users need to retain default values.
Mutually exclusive quality indicators are to be activated / de-activated according to the customer's preferences: "Java: Avoid using Throwable.printStackTrace() outside a try catch block" versus "Java: Avoid using Throwable.printStackTrace() within a try catch block", "Java: Avoid using System.err and System.out outside a try catch block" versus "Java: Avoid using System.err and System.out within a try catch block" (Important reminder: quality indicators that require a configuration and mutually exclusive quality indicators are delivered with the active status option set to 'false' so as not to disturb the quality assessment if not properly configured) . You need to choose the type of coding you require and de-activate the corresponding quality indicator.
- If all Mainframe analysis configurations do not take into account JCL analysis, you may wish to disable:
- Avoid incoherent file accesses in Cobol programs and DISP clauses in JCL
- Or, if some analysis does not take into account JCL files, you should declare exceptions for Modules generated with the results of these analyses.
- Naming controls on prefixes can be adapted:
Naming controls on prefixes can be adapted.:
Naming controls on prefixes can be adapted: