The following document contains the results of a JDepend metric analysis. The various metrics are defined at the bottom of this document.

Package | TC | CC | AC | Ca | Ce | A | I | D | V |
---|---|---|---|---|---|---|---|---|---|

org.gnu.glpk | 36 | 33 | 3 | 0 | 3 | 8.0% | 100.0% | 8.0% | 1 |

Afferent Couplings | Efferent Couplings | Abstractness | Instability | Distance |
---|---|---|---|---|

0 | 3 | 8.0% | 100.0% | 8.0% |

Abstract Classes | Concrete Classes | Used by Packages | Uses Packages |
---|---|---|---|

org.gnu.glpk.GLPKConstants org.gnu.glpk.GlpkCallbackListener org.gnu.glpk.GlpkTerminalListener |
org.gnu.glpk.GLPK org.gnu.glpk.GLPKJNI org.gnu.glpk.GlpkCallback org.gnu.glpk.GlpkCallback$1 org.gnu.glpk.GlpkException org.gnu.glpk.GlpkTerminal org.gnu.glpk.GlpkTerminal$1 org.gnu.glpk.SWIGTYPE_p_double org.gnu.glpk.SWIGTYPE_p_f_p_q_const__char_v_______void org.gnu.glpk.SWIGTYPE_p_f_p_struct_glp_tree_p_void__void org.gnu.glpk.SWIGTYPE_p_f_p_void__void org.gnu.glpk.SWIGTYPE_p_f_p_void_p_q_const__char__int org.gnu.glpk.SWIGTYPE_p_glp_prep org.gnu.glpk.SWIGTYPE_p_int org.gnu.glpk.SWIGTYPE_p_p_glp_vertex org.gnu.glpk.SWIGTYPE_p_size_t org.gnu.glpk.SWIGTYPE_p_va_list org.gnu.glpk.SWIGTYPE_p_void org.gnu.glpk.glp_arc org.gnu.glpk.glp_attr org.gnu.glpk.glp_bfcp org.gnu.glpk.glp_cpxcp org.gnu.glpk.glp_graph org.gnu.glpk.glp_iocp org.gnu.glpk.glp_iptcp org.gnu.glpk.glp_java_arc_data org.gnu.glpk.glp_java_vertex_data org.gnu.glpk.glp_mpscp org.gnu.glpk.glp_prob org.gnu.glpk.glp_smcp org.gnu.glpk.glp_tran org.gnu.glpk.glp_tree org.gnu.glpk.glp_vertex |
None |
java.io java.lang java.util |

There are no cyclic dependencies.

The following explanations are for quick reference and are lifted directly from the original JDepend documentation.

Term | Description |
---|---|

Number of Classes | The number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package. |

Afferent Couplings | The number of other packages that depend upon classes within the package is an indicator of the package's responsibility. |

Efferent Couplings | The number of other packages that the classes in the package depend upon is an indicator of the package's independence. |

Abstractness | The ratio of the number of abstract classes (and interfaces) in the analyzed package to the total number of classes in the analyzed package. The range for this metric is 0 to 1, with A=0 indicating a completely concrete package and A=1 indicating a completely abstract package. |

Instability | The ratio of efferent coupling (Ce) to total coupling (Ce / (Ce + Ca)). This metric is an indicator of the package's resilience to change. The range for this metric is 0 to 1, with I=0 indicating a completely stable package and I=1 indicating a completely instable package. |

Distance | The perpendicular distance of a package from the idealized line A + I = 1. This metric is an indicator of the package's balance between abstractness and stability. A package squarely on the main sequence is optimally balanced with respect to its abstractness and stability. Ideal packages are either completely abstract and stable (x=0, y=1) or completely concrete and instable (x=1, y=0). The range for this metric is 0 to 1, with D=0 indicating a package that is coincident with the main sequence and D=1 indicating a package that is as far from the main sequence as possible. |

Cycles | Packages participating in a package dependency cycle are in a deadly embrace with respect to reusability and their release cycle. Package dependency cycles can be easily identified by reviewing the textual reports of dependency cycles. Once these dependency cycles have been identified with JDepend, they can be broken by employing various object-oriented techniques. |