It is the cyclomatic complexity, also known as McCabe metric. Whenever the control flow of a method function splits, the complexity counter gets incremented by one.
|Complexity /class||class_complexity||Average complexity by class.|
|Complexity /file||file_complexity||Average complexity by file.|
|Complexity /method||function_complexity||Average complexity by method function.|
A class' afferent couplings is a measure of how many other classes use the specific class.
Depth in Tree
The depth of inheritance tree (DIT) metric provides for each class a measure of the inheritance levels from the top of the object hierarchy.
A class' efferent couplings is a measure of how many different classes are used by the specific class.
Minimal number of file cycles detected inside a package to be able to identify all undesired dependencies.
Number of file dependencies inside a package.
File dependencies to cut
Number of file dependencies to cut in order to remove all cycles between packages.
File tangle = Suspect file dependencies
File tangle index = 2 * (File tangle / File edges weight) * 100.
Lack of cohesion of methodsfunctions. See LCOM4 documentation page.
Number of children
The number of direct and indirect descendants of this class.
Minimal number of package cycles detected to be able to identify all undesired dependencies.
Package dependencies to cut
Number of package dependencies to cut in order to remove all cycles between packages.
Package tangle index
Level of package interdependency. Best value (0%) means that there is no cycle and worst value (100%) means that packages are really tangled. This metric is computed with the following formula: 2 * (File dependencies to cut / Number of file dependencies between packages) * 100.
Response for class
See RFC documentation page.
Package edges weight
Number of file dependencies between packages.
File dependencies to cut in order to remove cycles between files inside a package. Note that cycles between files inside a package does not always mean a bad quality architecture.
|Suspect LCOM4 density||suspect_lcom4_density||Density of files having a LCOM4 density greater than 1.|
Number of getter and setter methods functions used to get (reading) or set (writing) a class property.
|classes||Number of classes (including nested classes, interfaces, enums and annotations).|
|directories||Number of directories.|
|files||Number of files.|
Number of lines generated by Cobol code generators like CA-Telon.
|Generated lines of code||generated_ncloc||Number of lines of code generated by Cobol code generators like CA-Telon.|
|Inside Control Flow Statements||cobol_inside_ctrlflow_statements||Number of inside (intra program) control flow statements (GOBACK, STOP RUN, DISPLAY, CONTINUE, EXIT, RETURN, PERFORM paragraph1 THRU paragraph2).|
|lines||Number of physical lines (number of carriage returns).|
Number of physical lines that contain at least one character which is neither a whitespace or a tabulation or part of a comment.
|LOCs in Data Divisions||cobol_data_division_ncloc||Number of lines of code in Data divisions. Generated lines of code are excluded.|
|LOCs in Procedure Divisions||cobol_procedure_division_ncloc||Number of lines of code in Procedure divisions. Generated lines of code are excluded.|
Number of methods/ functions. Depending on the language, a function is either a function or a method or a paragraph.
|Outside Control Flow Statements||cobol_outside_ctrlflow_statements||Number of outside (inter programs) control flow statements (CALL, EXEC CICS LINK, EXEC CICS XCTL, EXEC SQL, EXEC CICS RETURN).|
|packages||Number of packages.|
|projects||Number of projects in a view.|
Number of public Classes + number of public Methods Functions + number of public Properties
Number of statements.