[ 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.maxur.perfmodel.backend 7 7 0 0 12 0.0% 100.0% 0.0% 1
org.maxur.perfmodel.backend.domain 3 2 1 3 3 33.0% 50.0% 17.0% 1
org.maxur.perfmodel.backend.infrastructure 2 2 0 1 8 0.0% 89.0% 11.0% 1
org.maxur.perfmodel.backend.rest 7 7 0 2 12 0.0% 86.0% 14.0% 1
org.maxur.perfmodel.backend.rest.resources 2 2 0 0 9 0.0% 100.0% 0.0% 1
org.maxur.perfmodel.backend.service 9 3 6 3 12 67.0% 80.0% 47.0% 1
org.maxur.perfmodel.backend.service.impl 3 3 0 1 11 0.0% 92.0% 8.0% 1
org.maxur.perfmodel.backend.utils 3 3 0 0 2 0.0% 100.0% 0.0% 1

Packages

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

org.maxur.perfmodel.backend

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 12 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.maxur.perfmodel.backend.ApplicationProvider
org.maxur.perfmodel.backend.Config
org.maxur.perfmodel.backend.Config$1
org.maxur.perfmodel.backend.Config$2
org.maxur.perfmodel.backend.Config$3
org.maxur.perfmodel.backend.DataSourceProvider
org.maxur.perfmodel.backend.Launcher
None java.lang
java.lang.annotation
javax.inject
org.glassfish.hk2.api
org.glassfish.hk2.utilities
org.glassfish.hk2.utilities.binding
org.glassfish.jersey.server
org.maxur.perfmodel.backend.infrastructure
org.maxur.perfmodel.backend.rest
org.maxur.perfmodel.backend.service
org.maxur.perfmodel.backend.service.impl
org.slf4j

org.maxur.perfmodel.backend.domain

Afferent Couplings Efferent Couplings Abstractness Instability Distance
3 3 33.0% 50.0% 17.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.maxur.perfmodel.backend.domain.Repository
org.maxur.perfmodel.backend.domain.ConflictException
org.maxur.perfmodel.backend.domain.Project
org.maxur.perfmodel.backend.infrastructure
org.maxur.perfmodel.backend.rest
org.maxur.perfmodel.backend.rest.resources
java.io
java.lang
java.util

org.maxur.perfmodel.backend.infrastructure

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 8 0.0% 89.0% 11.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.maxur.perfmodel.backend.infrastructure.DataSourceLevelDbImpl
org.maxur.perfmodel.backend.infrastructure.ProjectRepositoryLevelDbImpl
org.maxur.perfmodel.backend
java.io
java.lang
java.util
org.iq80.leveldb
org.iq80.leveldb.impl
org.maxur.perfmodel.backend.domain
org.maxur.perfmodel.backend.service
org.slf4j

org.maxur.perfmodel.backend.rest

Afferent Couplings Efferent Couplings Abstractness Instability Distance
2 12 0.0% 86.0% 14.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.maxur.perfmodel.backend.rest.PmcObjectMapperProvider
org.maxur.perfmodel.backend.rest.RestServiceConfig
org.maxur.perfmodel.backend.rest.RestServiceConfig$ServiceLocatorFeature
org.maxur.perfmodel.backend.rest.RuntimeExceptionHandler
org.maxur.perfmodel.backend.rest.RuntimeExceptionHandler$1
org.maxur.perfmodel.backend.rest.WebException
org.maxur.perfmodel.backend.rest.WebException$1
org.maxur.perfmodel.backend
org.maxur.perfmodel.backend.rest.resources
com.fasterxml.jackson.databind
java.lang
java.util
javax.ws.rs
javax.ws.rs.core
javax.ws.rs.ext
javax.xml.bind
org.glassfish.jersey
org.glassfish.jersey.jackson
org.glassfish.jersey.server
org.maxur.perfmodel.backend.domain
org.slf4j

org.maxur.perfmodel.backend.rest.resources

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 9 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.maxur.perfmodel.backend.rest.resources.ApplicationResource$1
org.maxur.perfmodel.backend.rest.resources.ProjectResource
None com.fasterxml.jackson.core.type
com.google.common.base
java.lang
java.util
javax.ws.rs.core
org.maxur.perfmodel.backend.domain
org.maxur.perfmodel.backend.rest
org.maxur.perfmodel.backend.rest.dto
org.slf4j

org.maxur.perfmodel.backend.service

Afferent Couplings Efferent Couplings Abstractness Instability Distance
3 12 67.0% 80.0% 47.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
org.maxur.perfmodel.backend.service.Application
org.maxur.perfmodel.backend.service.Benchmark
org.maxur.perfmodel.backend.service.DataSource
org.maxur.perfmodel.backend.service.Database
org.maxur.perfmodel.backend.service.PropertiesService
org.maxur.perfmodel.backend.service.WebServer
org.maxur.perfmodel.backend.service.BenchmarkMethodInterceptor
org.maxur.perfmodel.backend.service.ConfigurationInjectionResolver
org.maxur.perfmodel.backend.service.HK2InterceptionService
org.maxur.perfmodel.backend
org.maxur.perfmodel.backend.infrastructure
org.maxur.perfmodel.backend.service.impl
com.ecyrd.speed4j
java.io
java.lang
java.lang.annotation
java.lang.reflect
java.util
javax.inject
org.aopalliance.intercept
org.glassfish.hk2.api
org.glassfish.hk2.utilities
org.iq80.leveldb
org.slf4j

org.maxur.perfmodel.backend.service.impl

Afferent Couplings Efferent Couplings Abstractness Instability Distance
1 11 0.0% 92.0% 8.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.maxur.perfmodel.backend.service.impl.CliApplication
org.maxur.perfmodel.backend.service.impl.PropertiesServiceHoconImpl
org.maxur.perfmodel.backend.service.impl.WebServerGrizzlyImpl
org.maxur.perfmodel.backend
com.typesafe.config
java.io
java.lang
java.net
org.glassfish.grizzly
org.glassfish.grizzly.http.server
org.glassfish.hk2.api
org.glassfish.jersey.grizzly2.httpserver
org.glassfish.jersey.server
org.maxur.perfmodel.backend.service
org.slf4j

org.maxur.perfmodel.backend.utils

Afferent Couplings Efferent Couplings Abstractness Instability Distance
0 2 0.0% 100.0% 0.0%
Abstract Classes Concrete Classes Used by Packages Uses Packages
None org.maxur.perfmodel.backend.utils.DateTimeUtils
org.maxur.perfmodel.backend.utils.DateTimeUtils$1
org.maxur.perfmodel.backend.utils.OsUtils
None java.lang
java.util

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.

Back to top

Version: 2.1. Last Published: 2015-10-02.

Reflow Maven skin by Andrius Velykis.