Statics Report -
Date: Today||Designed for use with
For each histogram column, you can roll over the diagrams to get details on the contents on which subsystem the column relates to.
Click on it to go to a detailed view. On the bottom of the screen the data is presented in tabular form.
The matrix below presents in what way and to what degree code duplications are found in the
modules in the analysed system. Each dot represents a duplication between two classes. The size of the dots represents the number of
duplications the two classes are involved in between each other. Dots on the
diagonal represent duplications within a class. Notice that each side of the diagonal is equal. This
is no coincidence since they are each others mirror image.
By pointing your mouse over the dots you will see the details of that duplication. Click to
go to the class.
The Pareto Principle states that a minority of input produces the majority of results. This principle is often called the 80%:20% rule. The principle originates
from economics, but is often just as applicable to other types of systems such as software. In the following graphs Aggregated Source Statements and Aggregated
Cyclomatic Complexity per package is plotted.
According to the theroy the aggregated results will in most cases go though the 80:20 / 70:30 box. That
is not necessarily assert a bad design. Still, it proves the point that most of the logics and development effort in the system is focused on a limited number of
packages. You may in such cases consider to split up the main packages or pull together the smallest packages to get
the curve to go below the 80:20 / 70:30 box. That will probably make the package structure more balanced. Note that if all the packages are of equal size, the curve
will be linear (y=x).
See the explanations for
Source Statements and
Cyclomatic Complexity for more on their definitions.