JavaNCSS Metric Results

[ package ] [ object ] [ method ] [ explanation ]

The following document contains the results of a JavaNCSS metric analysis, using JavaNCSS version 32.53.
JavaNCSS web site.

Packages

[ package ] [ object ] [ method ] [ explanation ]

Packages sorted by NCSS.

Package	Classes	Methods	NCSS	Javadocs	Javadoc lines	Single lines comment	Multi lines comment
de.smartics.properties.api.core.annotations	2	0	82	0	0	22	679

Classes total	Methods total	NCSS total	Javadocs	Javadoc lines	Single lines comment	Multi lines comment
2	0	82	0	0	22	679

Objects

[ package ] [ object ] [ method ] [ explanation ]

TOP 30 classes containing the most NCSS.

Object	NCSS	Methods	Classes	Javadocs
de.smartics.properties.api.core.annotations.AccessType	1	0	0	0
de.smartics.properties.api.core.annotations.PropertyDefinitionTime	1	0	0	0

TOP 30 classes containing the most methods.

Object	NCSS	Methods	Classes	Javadocs
de.smartics.properties.api.core.annotations.AccessType	1	0	0	0
de.smartics.properties.api.core.annotations.PropertyDefinitionTime	1	0	0	0

Averages.

NCSS average	Program NCSS	Classes average	Methods average	Javadocs average
1.00	82.00	0.00	0.00	0.00

Methods

[ package ] [ object ] [ method ] [ explanation ]

TOP 30 Methods containing the most NCSS.

Methods	NCSS	CCN	Javadocs
de.smartics.properties.api.core.annotations..UpdateInterval()	1	1	0

Averages.

Program NCSS	NCSS average	CCN average	Javadocs average
82.00	1.00	1.00	0.00

Explanations

[ package ] [ object ] [ method ] [ explanation ]

Non Commenting Source Statements (NCSS)

Statements for JavaNCSS are not statements as specified in the Java Language Specification but include all kinds of declarations too. Roughly spoken, NCSS is approximately equivalent to counting ';' and '{' characters in Java source files.

Not counted are empty statements, empty blocks or semicolons after closing brackets. Of course, comments don't get counted too. Closing brackets also never get counted, the same applies to blocks in general.

	Examples
Package declaration	package java.lang;
Import declaration	import java.awt.*;
Class declaration	public class Foo { public class Foo extends Bla {
Interface declaration	public interface Able ; {
Field declaration	int a; int a, b, c = 5, d = 6;
Method declaration	public void cry(); public void gib() throws DeadException {
Constructor declaration	public Foo() {
Constructor invocation	this(); super();
Statement declaration	i = 0; if (ok) if (exit) { if (3 == 4); if (4 == 4) { ; } else {
Label declaration	fine :

In some cases consecutive semicolons are illegal according to the JLS but JavaNCSS still tolerates them (thought JavaNCSS is still more strict as 'javac'). Nevertheless they are never counted as two statements.

Cyclomatic Complexity Number (CCN)

CCN is also know as McCabe Metric. There exists a much hyped theory behind it based on graph theory, but it all comes down to simply counting 'if', 'for', 'while' statements etc. in a method. Whenever the control flow of a method splits, the "CCN counter" gets incremented by one.

Each method has a minimum value of 1 per default. For each of the following Java keywords/statements this value gets incremented by one:

• if
• for
• while
• case
• catch

Also if the control flow of a method returns abortively the CCNvalue will be incremented by one:

• if
• for

An ordinary return at the end of method will not be counted.

Note that 'else', 'default', and 'finally' don't increment the CCN value any further. On the other hand, a simple method with a 'switch' statement and a huge block of 'case' statements can have a surprisingly high CCN value (still it has the same value when converting a 'switch' block to an equivalent sequence of 'if' statements).