Note: Metrics evaluate the quality of software by analyzing the program source and quantifying
various kind of complexity. Complexity is a common source of problems and defects in software.
High complexity makes it more difficult to develop, understand, maintain, extend, test and debug
a program.
The primary use of metrics is to focus your attention on those parts of code that potentially are
complexity hot spots. Once the complex areas your program have been uncovered, you can take remedial
actions.
For additional information about metrics and their meaning, please consult
Metamata Metrics manual.
Packages
Package
Note: Metrics evaluate the quality of software by analyzing the program source and quantifying
various kind of complexity. Complexity is a common source of problems and defects in software.
High complexity makes it more difficult to develop, understand, maintain, extend, test and debug
a program.
The primary use of metrics is to focus your attention on those parts of code that potentially are
complexity hot spots. Once the complex areas your program have been uncovered, you can take remedial
actions.
For additional information about metrics and their meaning, please consult
Metamata Metrics manual.
Note: Rules checked have originated from style guidelines suggested by the language designers,
experience from the Java development community and insite experience. Violations are generally
reported with a reference to the Java Language Specifications (JLS x.x.x)
and Metamata Audit rules (x.x).
Please consult these documents for additional information about violations.
One should note that these violations do not necessary underline errors but should be used
as an indication for possible errors. As always, use your best judgment and review
them carefully, it might save you hours of debugging.