This is a html'ized CMTJava Complexity Measures Report.
You can view the data via:
SUMMARY view contains class level information. It's columns are:
- SUMMARY view: The class summary level.
- DETAILED view: Effectively the textual CMTJava report of which this html representation was generated.
- Actual source: A link to the actual source code file is constructed (if the source file could be found at cmtjava2html time).
Red color has been used to highlight points that the CMTJava tool gave an alarm of. Click on the column header links for seeing a sorted view of the selected attribute. Click on class links for seeing the corresponding location in DETAILED view.
- Alarms-%: A red/white coded histogram showing how many % of the class's measures were alarmed, i.e. out of their configured limits.
- Measured item: Name of the class.
- v(G): McCabe's cyclomatic number, control flow complexity.
- LOCphy: Number of physical lines.
- LOCpro: Number of lines having program code, i.e. plain blank lines and plain comment lines removed.
- c%: A flag if the measured item was warned ('-') or not (' ') for comment percent (LOCcom/LOCphy * 100) being out of limits.
- V: Halstead's volume (V), "logical code size".
- B: Halstead's estimated number of bugs (B), how many bugs there likely still are based on the code complexity.
- MI or MIwoc: Maintainability index (MI) or Maintainability index without comments (MIwoc), level of maintainability. Whether MI or MIwoc is shown depends on CMTJava configuration setting, and is decided at cmtjava time.
At the bottom there is a copy of the overall summary section from the input report. It contains various summary data of the measured files and the used alarm limits.
DETAILED view is effectively the same as the original input CMTJava report. The v(G), LOCphy, LOCpro, c%, V, B and MI (or MIwoc) columns have the same meanings as in the SUMMARY view.
Note that a (big) DETAILED view may have been splitted to many (smaller) windows, which are First/Previous/Next/Last chained to each other. The possible splitting was decided at cmtjava2html time.
For more information about the CMTJava System in general, please see the CMTJava User's Guide. It should be in the doc subdirectory of the CMTJava installation directory, which in turn should be pointed by environment variable CMTJAVAHOME.