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
org.opendaylight.vtn.manager 2 1 1 1 2 50.0% 67.0% 17.0% 1
org.opendaylight.vtn.manager.packet 14 11 3 0 6 21.0% 100.0% 21.0% 1
org.opendaylight.vtn.manager.util 14 11 3 1 12 21.0% 92.0% 14.0% 1
org.opendaylight.vtn.manager.util.xml.adapters 8 8 0 0 4 0.0% 100.0% 0.0% 1

Packages

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

org.opendaylight.vtn.manager

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 2 50.0% 67.0% 17.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.opendaylight.vtn.manager.VTNManager
org.opendaylight.vtn.manager.VTNException
org.opendaylight.vtn.manager.packet
java.lang
org.opendaylight.yang.gen.v1.urn.opendaylight.vtn.types.rev150209

org.opendaylight.vtn.manager.packet

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 6 21.0% 100.0% 21.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.opendaylight.vtn.manager.packet.EtherTypePacket
org.opendaylight.vtn.manager.packet.Packet
org.opendaylight.vtn.manager.packet.PortPacket
org.opendaylight.vtn.manager.packet.ARP
org.opendaylight.vtn.manager.packet.Ethernet
org.opendaylight.vtn.manager.packet.ICMP
org.opendaylight.vtn.manager.packet.IEEE8021Q
org.opendaylight.vtn.manager.packet.IPv4
org.opendaylight.vtn.manager.packet.Packet$1
org.opendaylight.vtn.manager.packet.Packet$HeaderField
org.opendaylight.vtn.manager.packet.Packet$HeaderMapBuilder
org.opendaylight.vtn.manager.packet.PacketException
org.opendaylight.vtn.manager.packet.TCP
org.opendaylight.vtn.manager.packet.UDP
None com.google.common.collect
java.lang
java.util
org.opendaylight.vtn.manager
org.opendaylight.vtn.manager.util
org.slf4j

org.opendaylight.vtn.manager.util

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 12 21.0% 92.0% 14.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.opendaylight.vtn.manager.util.IpNetwork
org.opendaylight.vtn.manager.util.VTNIdentifiable
org.opendaylight.vtn.manager.util.package-info
org.opendaylight.vtn.manager.util.ByteUtils
org.opendaylight.vtn.manager.util.ByteUtils$1
org.opendaylight.vtn.manager.util.ByteUtils$BitStream
org.opendaylight.vtn.manager.util.EtherAddress
org.opendaylight.vtn.manager.util.EtherTypes
org.opendaylight.vtn.manager.util.InetProtocols
org.opendaylight.vtn.manager.util.Ip4Network
org.opendaylight.vtn.manager.util.IpNetwork$1
org.opendaylight.vtn.manager.util.IpNetwork$InetAddressPrefix
org.opendaylight.vtn.manager.util.NumberUtils
org.opendaylight.vtn.manager.util.VTNIdentifiableComparator
org.opendaylight.vtn.manager.packet
com.google.common.base
com.google.common.collect
java.io
java.lang
java.math
java.net
java.util
org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.inet.types.rev130715
org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.yang.types.rev130715
org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.address
org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.address.address
org.opendaylight.yang.gen.v1.urn.opendaylight.model.match.types.rev131026

org.opendaylight.vtn.manager.util.xml.adapters

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 4 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.opendaylight.vtn.manager.util.xml.adapters.ByteAdapter
org.opendaylight.vtn.manager.util.xml.adapters.DoubleAdapter
org.opendaylight.vtn.manager.util.xml.adapters.IntegerAdapter
org.opendaylight.vtn.manager.util.xml.adapters.LongAdapter
org.opendaylight.vtn.manager.util.xml.adapters.ShortAdapter
org.opendaylight.vtn.manager.util.xml.adapters.VlanIdAdapter
org.opendaylight.vtn.manager.util.xml.adapters.VnodeNameAdapter
org.opendaylight.vtn.manager.util.xml.adapters.VtnPortDescAdapter
None java.lang
javax.xml.bind.annotation.adapters
org.opendaylight.yang.gen.v1.urn.opendaylight.l2.types.rev130827
org.opendaylight.yang.gen.v1.urn.opendaylight.vtn.types.rev150209

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.