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
com.soebes.subversion.sapm20191155.0%83.0%12.0%1
com.soebes.subversion.sapm.parser32320150.0%83.0%17.0%1

Packages

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

com.soebes.subversion.sapm

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
155.0%83.0%12.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
com.soebes.subversion.sapm.IPrincipal
com.soebes.subversion.sapm.ANTLRNoCaseStringStream
com.soebes.subversion.sapm.Access
com.soebes.subversion.sapm.AccessLevel
com.soebes.subversion.sapm.AccessRule
com.soebes.subversion.sapm.AccessRules
com.soebes.subversion.sapm.Alias
com.soebes.subversion.sapm.Aliases
com.soebes.subversion.sapm.AuthorizationFile
com.soebes.subversion.sapm.AuthorizationFileException
com.soebes.subversion.sapm.FileName
com.soebes.subversion.sapm.Group
com.soebes.subversion.sapm.Groups
com.soebes.subversion.sapm.Path
com.soebes.subversion.sapm.User
com.soebes.subversion.sapm.UserAnonymous
com.soebes.subversion.sapm.UserAsterik
com.soebes.subversion.sapm.UserAuthenticated
com.soebes.subversion.sapm.UserFactory
com.soebes.subversion.sapm.Users
com.soebes.subversion.sapm.parser
com.soebes.subversion.sapm.parser
java.io
java.lang
java.util
org.antlr.runtime

com.soebes.subversion.sapm.parser

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
150.0%83.0%17.0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
Nonecom.soebes.subversion.sapm.parser.SAFPLexer
com.soebes.subversion.sapm.parser.SAFPLexer$DFA6
com.soebes.subversion.sapm.parser.SAFPParser
com.soebes.subversion.sapm.parser.SAFPParser$alias_return
com.soebes.subversion.sapm.parser.SAFPParser$aliases_return
com.soebes.subversion.sapm.parser.SAFPParser$aliaspermission_return
com.soebes.subversion.sapm.parser.SAFPParser$aliasreference_return
com.soebes.subversion.sapm.parser.SAFPParser$group_return
com.soebes.subversion.sapm.parser.SAFPParser$grouppermission_return
com.soebes.subversion.sapm.parser.SAFPParser$groupreference_return
com.soebes.subversion.sapm.parser.SAFPParser$groups_return
com.soebes.subversion.sapm.parser.SAFPParser$groupuserdefinition_return
com.soebes.subversion.sapm.parser.SAFPParser$groupuserreference_return
com.soebes.subversion.sapm.parser.SAFPParser$permission_nothing_return
com.soebes.subversion.sapm.parser.SAFPParser$permission_read_return
com.soebes.subversion.sapm.parser.SAFPParser$permission_read_write_return
com.soebes.subversion.sapm.parser.SAFPParser$permission_return
com.soebes.subversion.sapm.parser.SAFPParser$permission_write_return
com.soebes.subversion.sapm.parser.SAFPParser$permissionrule_return
com.soebes.subversion.sapm.parser.SAFPParser$prog_return
com.soebes.subversion.sapm.parser.SAFPParser$repos_return
com.soebes.subversion.sapm.parser.SAFPParser$repository_return
com.soebes.subversion.sapm.parser.SAFPParser$repositorypath_return
com.soebes.subversion.sapm.parser.SAFPParser$sectionaliases_return
com.soebes.subversion.sapm.parser.SAFPParser$sectiongroup_return
com.soebes.subversion.sapm.parser.SAFPParser$sectionrepository_return
com.soebes.subversion.sapm.parser.SAFPParser$statement_return
com.soebes.subversion.sapm.parser.SAFPParser$user_return
com.soebes.subversion.sapm.parser.SAFPParser$useralias_return
com.soebes.subversion.sapm.parser.SAFPParser$useraliasdefinition_return
com.soebes.subversion.sapm.parser.SAFPParser$userpermission_return
com.soebes.subversion.sapm.parser.SAFPParser$userreference_return
com.soebes.subversion.sapm
com.soebes.subversion.sapm
java.lang
java.util
org.antlr.runtime
org.antlr.runtime.tree

Cycles

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

PackagePackage Dependencies
com.soebes.subversion.sapmcom.soebes.subversion.sapm.parser
com.soebes.subversion.sapm
com.soebes.subversion.sapm.parsercom.soebes.subversion.sapm
com.soebes.subversion.sapm.parser

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.