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
ch.visnet.heartbreak 41 30 11 0 18 27.000002% 100.0% 27.000002% 1
com.adhoco.controller 1 1 0 1 2 0.0% 67.0% 33.0% 1

Packages

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

ch.visnet.heartbreak

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 18 27.000002% 100.0% 27.000002%
Abstract Classes Concrete Classes Used by Packages Uses Packages
ch.visnet.heartbreak.AbstractHeatSource
ch.visnet.heartbreak.AbstractThermalNode
ch.visnet.heartbreak.FunctionOfTime
ch.visnet.heartbreak.Illuminance
ch.visnet.heartbreak.NodeConnection
ch.visnet.heartbreak.Schedule
ch.visnet.heartbreak.Steppable
ch.visnet.heartbreak.ThermalNode
ch.visnet.heartbreak.ZoneLightingModel
ch.visnet.heartbreak.ZoneModel
ch.visnet.heartbreak.ZoneThermalModel
ch.visnet.heartbreak.AdhocoControlProfile
ch.visnet.heartbreak.AdhocoHardwareFactory
ch.visnet.heartbreak.AdhocoHardwareFactory$1
ch.visnet.heartbreak.ControllableHeatSource
ch.visnet.heartbreak.EccobuildClimateDAO
ch.visnet.heartbreak.EccobuildClimateDAO$1
ch.visnet.heartbreak.EccobuildClimateDAO$ClimateEntity
ch.visnet.heartbreak.EccobuildClimateDAO$ClimateEntityMapper
ch.visnet.heartbreak.EccobuildIrradianceSchedule
ch.visnet.heartbreak.EccobuildTemperatureSchedule
ch.visnet.heartbreak.FunctionalSchedule
ch.visnet.heartbreak.HeatingBreaker
ch.visnet.heartbreak.Main
ch.visnet.heartbreak.MockHomeController
ch.visnet.heartbreak.MockMeteo
ch.visnet.heartbreak.MockRoom
ch.visnet.heartbreak.MockRoomController
ch.visnet.heartbreak.MockValveHeating
ch.visnet.heartbreak.Node2NodeConnection
ch.visnet.heartbreak.Node2NodeConnection$1
ch.visnet.heartbreak.Node2NodeConnection$NodesComplete
ch.visnet.heartbreak.RealTimeClockAdapter
ch.visnet.heartbreak.ScheduledIlluminance
ch.visnet.heartbreak.ScheduledTemperatureNode
ch.visnet.heartbreak.SimpleSolarGains
ch.visnet.heartbreak.SimpleThermalNode
ch.visnet.heartbreak.SimpleZoneLightingModel
ch.visnet.heartbreak.SimpleZoneModel
ch.visnet.heartbreak.SimpleZoneThermalModel
ch.visnet.heartbreak.SineWave
None com.adhoco.controller
com.adhoco.hardware.osgi
com.adhoco.homestructure
com.adhoco.system
com.adhoco.zbdevices
com.adhoco.zbport
java.io
java.lang
java.sql
java.text
java.util
java.util.logging
javax.sql
org.osgi.framework
org.springframework.context
org.springframework.context.support
org.springframework.jdbc.core
org.springframework.jdbc.core.simple

com.adhoco.controller

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 2 0.0% 67.0% 33.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None com.adhoco.controller.HeatingAdapter
ch.visnet.heartbreak
com.adhoco.hardware.osgi
java.lang

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.