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 ]

PackageTCCCACCaCeAIDV
org.apache.amber.oauth2.client3210833.0%100.0%33.0%1
org.apache.amber.oauth2.client.request6511717.0%88.0%4.0%1
org.apache.amber.oauth2.client.response8622825.0%80.0%5.0%1
org.apache.amber.oauth2.client.validator4311525.0%83.0%8.0%1

Packages

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

org.apache.amber.oauth2.client

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
0833.0%100.0%33.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.apache.amber.oauth2.client.HttpClient
org.apache.amber.oauth2.client.OAuthClient
org.apache.amber.oauth2.client.URLConnectionClient
Nonejava.io
java.lang
java.net
java.util
org.apache.amber.oauth2.client.request
org.apache.amber.oauth2.client.response
org.apache.amber.oauth2.common.exception
org.apache.amber.oauth2.common.utils

org.apache.amber.oauth2.client.request

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1717.0%88.0%4.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.apache.amber.oauth2.client.request.OAuthClientRequest$OAuthRequestBuilder
org.apache.amber.oauth2.client.request.ClientHeaderParametersApplier
org.apache.amber.oauth2.client.request.OAuthBearerClientRequest
org.apache.amber.oauth2.client.request.OAuthClientRequest
org.apache.amber.oauth2.client.request.OAuthClientRequest$AuthenticationRequestBuilder
org.apache.amber.oauth2.client.request.OAuthClientRequest$TokenRequestBuilder
org.apache.amber.oauth2.client
java.lang
java.util
org.apache.amber.oauth2.common.exception
org.apache.amber.oauth2.common.message
org.apache.amber.oauth2.common.message.types
org.apache.amber.oauth2.common.parameters
org.apache.amber.oauth2.common.utils

org.apache.amber.oauth2.client.response

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
2825.0%80.0%5.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.apache.amber.oauth2.client.response.OAuthAccessTokenResponse
org.apache.amber.oauth2.client.response.OAuthClientResponse
org.apache.amber.oauth2.client.response.GitHubTokenResponse
org.apache.amber.oauth2.client.response.OAuthAuthzResponse
org.apache.amber.oauth2.client.response.OAuthClientResponseFactory
org.apache.amber.oauth2.client.response.OAuthErrorResponse
org.apache.amber.oauth2.client.response.OAuthJSONAccessTokenResponse
org.apache.amber.oauth2.client.response.OAuthResourceResponse
org.apache.amber.oauth2.client
org.apache.amber.oauth2.client.validator
java.lang
java.util
javax.servlet.http
org.apache.amber.oauth2.client.validator
org.apache.amber.oauth2.common.exception
org.apache.amber.oauth2.common.token
org.apache.amber.oauth2.common.utils
org.codehaus.jettison.json

org.apache.amber.oauth2.client.validator

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
1525.0%83.0%8.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
org.apache.amber.oauth2.client.validator.OAuthClientValidator
org.apache.amber.oauth2.client.validator.CodeTokenValidator
org.apache.amber.oauth2.client.validator.CodeValidator
org.apache.amber.oauth2.client.validator.TokenValidator
org.apache.amber.oauth2.client.response
java.lang
java.util
org.apache.amber.oauth2.client.response
org.apache.amber.oauth2.common.exception
org.apache.amber.oauth2.common.utils

Cycles

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

PackagePackage Dependencies
org.apache.amber.oauth2.clientorg.apache.amber.oauth2.client.response
org.apache.amber.oauth2.client.validator
org.apache.amber.oauth2.client.response
org.apache.amber.oauth2.client.responseorg.apache.amber.oauth2.client.validator
org.apache.amber.oauth2.client.response
org.apache.amber.oauth2.client.validatororg.apache.amber.oauth2.client.response
org.apache.amber.oauth2.client.validator

Explanation

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

The following explanations are for quick reference and are lifted directly from the original JDepend documentation.

TermDescription
Number of ClassesThe number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
Afferent CouplingsThe number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
Efferent CouplingsThe number of other packages that the classes in the package depend upon is an indicator of the package's independence.
AbstractnessThe 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.
InstabilityThe 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.
DistanceThe 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.
CyclesPackages 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.