<%-- * Copyright by Intland Software * * All rights reserved. * * This software is the confidential and proprietary information * of Intland Software. ("Confidential Information"). You * shall not disclose such Confidential Information and shall use * it only in accordance with the terms of the license agreement * you entered into with Intland. * * $Revision$ $Date$ --%> <%@ taglib uri="jstl-c" prefix="c" %> <%@ taglib uri="jstl-fmt" prefix="fmt" %> <%@ taglib uri="jstl-x" prefix="x" %> <%@ taglib uri="jstl-fn" prefix="fn" %> <%@ taglib uri="struts-html" prefix="html" %> <%@ taglib uri="taglib" prefix="tag" %> <%@ taglib uri="uitaglib" prefix="ui" %> <% final String lineBreak = " "; int counter = 0; %>
: JDepend Analysis
<%-- Description of the JDepend Plugin. --%>
JDepend traverses Java class file directories and generates design quality metrics for each Java package. JDepend allows you to automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability to manage package dependencies effectively.
Trends-chart information
<%-- Here the summary of the jdepend results are displayed. --%> <%-- Summary of the JDepend Results. --%> ">
 Package   TC   AC   CC   AC   EC   A  I  D
                           
<%-- Here we indicate the information about the packages with regard to jdepend. --%> <%-- The below html:link tag includes as a html anchor tag with name of the package.--%> Package:  
 Afferent Couplings   Efferent Couplings   Abstractness   Instability   Distance 
              
 Abstract Classes   Concrete Classes   Used by Packages   Uses Packages 
  
 		  
 		  
 		  
<%-- Here we indicate the information about the Cycles with regard to jdepend. --%> ">
 Package   Cyclic Dependencies 
     
<%-- This is a detailed explanation of the terms. --%> <%=lineBreak%>
The following explanations are for quick reference and are lifted directly from the original JDepend documentation.
<%=lineBreak%>
 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 percentage 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 100%, with A=0% indicating a completely concrete package and A=100% indicating a completely abstract package.
 Instability    The ratio percentage 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 100 %, with I=0% indicating a completely stable package and I=100% indicating a completely instable package.
 Distance    The perpendicular distance of a package from the idealized line A + I = 100%. 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 100%, with D=0% indicating a package that is coincident with the main sequence and D=100% 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.