Metric Results

[ summary ] [ packages ] [ cycles ] [ explanations ]

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

Summary

[ summary ] [ packages ] [ cycles ] [ explanations ]

Package TC CC AC Ca Ce A I D V
ccol 2 2 0 0 14 0.0% 100.0% 0.0% 1
org.opentrafficsim.trafficcontrol 2 1 1 2 3 50.0% 60.000004% 10.0% 1
org.opentrafficsim.trafficcontrol.trafcod 23 22 1 0 28 4.0% 100.0% 4.0% 1

Packages

[ summary ] [ packages ] [ cycles ] [ explanations ]

ccol

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 14 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None ccol.CCOL
ccol.CCOL$1
 None java.io
java.lang
java.net
java.rmi
java.util
nl.tudelft.simulation.dsol
nl.tudelft.simulation.dsol.simulators
nl.tudelft.simulation.event
org.djunits.unit
org.djunits.value.vdouble.scalar
org.opentrafficsim.core.dsol
org.opentrafficsim.core.network
org.opentrafficsim.core.object
org.opentrafficsim.trafficcontrol

org.opentrafficsim.trafficcontrol

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 3 50.0% 60.000004% 10.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.opentrafficsim.trafficcontrol.TrafficController
 org.opentrafficsim.trafficcontrol.TrafficControlException
 ccol
org.opentrafficsim.trafficcontrol.trafcod
 java.lang
nl.tudelft.simulation.event
org.opentrafficsim.core.object

org.opentrafficsim.trafficcontrol.trafcod

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 28 4.0% 100.0% 4.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.opentrafficsim.trafficcontrol.trafcod.TrafCODObject
 org.opentrafficsim.trafficcontrol.trafcod.CausePrinter
org.opentrafficsim.trafficcontrol.trafcod.DetectorImage
org.opentrafficsim.trafficcontrol.trafcod.Diagram
org.opentrafficsim.trafficcontrol.trafcod.Diagram$1
org.opentrafficsim.trafficcontrol.trafcod.Diagram$2
org.opentrafficsim.trafficcontrol.trafcod.Diagram$3
org.opentrafficsim.trafficcontrol.trafcod.Diagram$4
org.opentrafficsim.trafficcontrol.trafcod.Diagram$Command
org.opentrafficsim.trafficcontrol.trafcod.Diagram$LaneType
org.opentrafficsim.trafficcontrol.trafcod.Diagram$RouteStep
org.opentrafficsim.trafficcontrol.trafcod.Diagram$XYPair
org.opentrafficsim.trafficcontrol.trafcod.Flags
org.opentrafficsim.trafficcontrol.trafcod.NameAndStream
org.opentrafficsim.trafficcontrol.trafcod.PrintFlags
org.opentrafficsim.trafficcontrol.trafcod.TrafCOD
org.opentrafficsim.trafficcontrol.trafcod.TrafCOD$1
org.opentrafficsim.trafficcontrol.trafcod.TrafCOD$ParserState
org.opentrafficsim.trafficcontrol.trafcod.TrafCOD$Token
org.opentrafficsim.trafficcontrol.trafcod.TrafCODDisplay
org.opentrafficsim.trafficcontrol.trafcod.TrafficLightImage
org.opentrafficsim.trafficcontrol.trafcod.TrafficLightImage$1
org.opentrafficsim.trafficcontrol.trafcod.Variable
 None java.awt
java.awt.event
java.awt.geom
java.awt.image
java.io
java.lang
java.net
java.rmi
java.util
javax.imageio
javax.media.j3d
javax.swing
nl.tudelft.simulation.dsol
nl.tudelft.simulation.dsol.simulators
nl.tudelft.simulation.event
nl.tudelft.simulation.immutablecollections
nl.tudelft.simulation.language
nl.tudelft.simulation.language.d3
org.djunits.unit
org.djunits.value.vdouble.scalar
org.opentrafficsim.core.dsol
org.opentrafficsim.core.geometry
org.opentrafficsim.core.network
org.opentrafficsim.core.object
org.opentrafficsim.road.network.lane
org.opentrafficsim.road.network.lane.object.sensor
org.opentrafficsim.road.network.lane.object.trafficlight
org.opentrafficsim.trafficcontrol

Cycles

[ summary ] [ packages ] [ cycles ] [ explanations ]

There are no cyclic dependencies.

Explanation

[ summary ] [ packages ] [ cycles ] [ explanations ]

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.