| Package | TC | CC | AC | Ca | Ce | A | I | D | V |
|---|---|---|---|---|---|---|---|---|---|
| org.opendaylight.netvirt.fibmanager | 22 | 22 | 0 | 0 | 43 | 0.0% | 100.0% | 0.0% | 1 |
| Afferent Couplings | Efferent Couplings | Abstractness | Instability | Distance |
|---|---|---|---|---|
| 0 | 43 | 0.0% | 100.0% | 0.0% |
| Abstract Classes | Concrete Classes | Used by Packages | Uses Packages |
|---|---|---|---|
| None | org.opendaylight.netvirt.fibmanager.FibConstants org.opendaylight.netvirt.fibmanager.FibManagerImpl org.opendaylight.netvirt.fibmanager.FibManagerImpl$1 org.opendaylight.netvirt.fibmanager.FibRpcServiceImpl org.opendaylight.netvirt.fibmanager.FibUtil org.opendaylight.netvirt.fibmanager.FibUtil$1 org.opendaylight.netvirt.fibmanager.L3VPNTransportTypes org.opendaylight.netvirt.fibmanager.NexthopManager$1 org.opendaylight.netvirt.fibmanager.NexthopManager$AdjacencyResult org.opendaylight.netvirt.fibmanager.VrfEntryListener$1 org.opendaylight.netvirt.fibmanager.VrfEntryListener$10 org.opendaylight.netvirt.fibmanager.VrfEntryListener$11 org.opendaylight.netvirt.fibmanager.VrfEntryListener$12 org.opendaylight.netvirt.fibmanager.VrfEntryListener$2 org.opendaylight.netvirt.fibmanager.VrfEntryListener$3 org.opendaylight.netvirt.fibmanager.VrfEntryListener$4 org.opendaylight.netvirt.fibmanager.VrfEntryListener$5 org.opendaylight.netvirt.fibmanager.VrfEntryListener$6 org.opendaylight.netvirt.fibmanager.VrfEntryListener$7 org.opendaylight.netvirt.fibmanager.VrfEntryListener$8 org.opendaylight.netvirt.fibmanager.VrfEntryListener$9 org.opendaylight.netvirt.fibmanager.VrfEntryListener$CleanupVpnInterfaceWorker |
None | com.google.common.base com.google.common.util.concurrent io.netty.util.concurrent java.lang java.math java.net java.util java.util.concurrent org.opendaylight.controller.config.api.osgi org.opendaylight.controller.md.sal.binding.api org.opendaylight.controller.md.sal.common.api.data org.opendaylight.genius.itm.globals org.opendaylight.genius.mdsalutil org.opendaylight.genius.mdsalutil.interfaces org.opendaylight.netvirt.fibmanager.api org.opendaylight.netvirt.vpnmanager.api org.opendaylight.netvirt.vpnmanager.api.intervpnlink org.opendaylight.yang.gen.v1.urn.huawei.params.xml.ns.yang.l3vpn.rev140815 org.opendaylight.yang.gen.v1.urn.huawei.params.xml.ns.yang.l3vpn.rev140815.vpn.interfaces org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.yang.types.rev130715 org.opendaylight.yang.gen.v1.urn.opendaylight.genius.idmanager.rev160406 org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.fib.rpc.rev160121 org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.fibmanager.rev150330 org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.fibmanager.rev150330.fibentries org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.fibmanager.rev150330.label.route.map org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.fibmanager.rev150330.vrfentries org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911 org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.adjacency.list org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.prefix.to._interface org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.prefix.to._interface.vpn.ids org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.vpn.id.to.vpn.instance org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.vpn.instance.op.data org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.vpn.instance.op.data.vpn.instance.op.data.entry org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.vpn.instance.op.data.vpn.instance.op.data.entry.vpn.to.dpn.list org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.vpn.instance.to.vpn.id org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.vpn.to.extraroute org.opendaylight.yang.gen.v1.urn.opendaylight.netvirt.l3vpn.rev130911.vpn.to.extraroute.vpn org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.netvirt.inter.vpn.link.rev160311 org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.netvirt.inter.vpn.link.rev160311.inter.vpn.link.states org.opendaylight.yangtools.yang.binding org.opendaylight.yangtools.yang.common org.osgi.framework org.slf4j |
| 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. |