JavaNCSS Metric Results

[ packages] [ objects] [ functions] [ explanations]

The following document contains the results of a JavaNCSSmetric analysis.

Packages

[ packages] [ objects] [ functions] [ explanations]

Packages sorted by NCSS

PackageClassesFunctions NCSS JavadocsJavadoc LinesSingle Comment LinesMulti Comment Lines
net.sf.jira.plugin.portlet.version36137958693
net.sf.jira.plugin.report.version1260327231
net.sf.jira.plugin.util1449534131
Classes totalFunctions total NCSS total JavadocsJavadoc LinesSingle Comment LinesMulti Comment Lines
512246171199155

Objects

[ packages] [ objects] [ functions] [ explanations]

TOP 30 classes containing the most NCSS

Object NCSS FunctionsClassesJavadocs
net.sf.jira.plugin.portlet.version.VersionTwoDimensionalStatsPortlet43203
net.sf.jira.plugin.util.MultiVersionValuesGenerator38405
net.sf.jira.plugin.report.version.VersionSingleLevelGroupByReport37203
net.sf.jira.plugin.portlet.version.VersionStatsPortlet30203
net.sf.jira.plugin.portlet.version.VersionAssignedToMePortlet10203

TOP 30 classes containing the most functions

ObjectNCSS Functions ClassesJavadocs
net.sf.jira.plugin.util.MultiVersionValuesGenerator38405
net.sf.jira.plugin.portlet.version.VersionStatsPortlet30203
net.sf.jira.plugin.portlet.version.VersionTwoDimensionalStatsPortlet43203
net.sf.jira.plugin.portlet.version.VersionAssignedToMePortlet10203
net.sf.jira.plugin.report.version.VersionSingleLevelGroupByReport37203

Averages

NCSS average Program NCSSClasses averageFunctions averageJavadocs average
31.60246.000.002.403.40

Functions

[ packages] [ objects] [ functions] [ explanations]

TOP 30 functions containing the most NCSS

Function NCSS CCNJavadoc
net.sf.jira.plugin.portlet.version.VersionTwoDimensionalStatsPortlet.getVelocityParams(PortletConfiguration)3551
net.sf.jira.plugin.portlet.version.VersionStatsPortlet.getVelocityParams(PortletConfiguration)2241
net.sf.jira.plugin.report.version.VersionSingleLevelGroupByReport.generateReportHtml(ProjectActionSupport,Map)2151
net.sf.jira.plugin.util.MultiVersionValuesGenerator.addVersions(Map,Map)1341
net.sf.jira.plugin.util.MultiVersionValuesGenerator.getValues(Map)1021
net.sf.jira.plugin.report.version.VersionSingleLevelGroupByReport.VersionSingleLevelGroupByReport(SearchProvider,JiraAuthenticationContext,SearchRequestManager,IssueFactory,CustomFieldManager,SearchProviderFactory)811
net.sf.jira.plugin.util.MultiVersionValuesGenerator.switchKeyValue(Map)721
net.sf.jira.plugin.util.MultiVersionValuesGenerator.getVersionName(String)741
net.sf.jira.plugin.portlet.version.VersionStatsPortlet.VersionStatsPortlet(JiraAuthenticationContext,PermissionManager,ApplicationProperties,SearchRequestManager,CustomFieldManager)411
net.sf.jira.plugin.portlet.version.VersionTwoDimensionalStatsPortlet.VersionTwoDimensionalStatsPortlet(JiraAuthenticationContext,PermissionManager,ApplicationProperties,CustomFieldManager,SearchProvider)411
net.sf.jira.plugin.portlet.version.VersionAssignedToMePortlet.getVelocityParams(PortletConfiguration)411
net.sf.jira.plugin.portlet.version.VersionAssignedToMePortlet.VersionAssignedToMePortlet(JiraAuthenticationContext,PermissionManager,ConstantsManager,SearchProvider,IssueManager,ApplicationProperties)311
Program NCSS: NCSS average CCN averageJavadocs average
246.0011.502.581.00

Explanations

[ packages] [ objects] [ functions] [ explanations]

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.

Actually, the NCSS counter gets incremented by one for each:

 ExamplesComment
Package declarationpackage java.lang; 
Import declarationimport java.awt.*; 
Class declaration- public class Foo {

- public class Foo extends Bla {
 
Interface declarationpublic interface Able ; { 
Field declaration- int a;

- int a, b, c = 5, d = 6;
No matter how many fields get actually declared through a comma separated list, and no matter if these fields get actually initialized, only one statement is counted. So "int a, b, c = 5, d = 6;" gets only +1 count, not four or even six (let me know if there is good reason to count it differently).
Method declaration- public void cry();

- public void gib() throws DeadException {
 
Constructor declarationpublic Foo() { 
Constructor invocation- this();

- super();
 
Statement- i = 0;

- if (ok)

- if (exit) {

- if (3 == 4);

- if (4 == 4) { ; }

- } else {
expression, if, else, while, do, for, switch, break, continue, return, throw, synchronized, catch, finally
Labelfine :normal, case, default

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.

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:
  • return
  • throw

An ordinary return at the end of method (no matter if it's a function or a procedure) will not be counted.

Note that else, default, and finallydon't increment the CCN value any further. On the other hand, a simple method with a switchstatement and a huge block of casestatements can have a surprisingly high CCN value (still it has the same value when converting a switchblock to an equivalent sequence of ifstatements).

The first article about this trivial software metric is one of the most cited papers in computer science. Sometimes you just must be the first to point out some basic shit and you are history. It seems just like a wonder that nobody was able to package Lines of Code in a more scientific manner. Now it's too late to label someone's name on it :).