Dependency Graph

Online documentation:

Dependency Matrix

Online documentation:

Visualizing Code Metrics through Treemaping

With the Online documentation, understand how Treemaping can help you see patterns in your code base, that would be hard to spot with other ways.

Abstractness versus Instability Diagram

The Abstractness versus Instability Diagram helps to detect which assemblies are potentially painful to maintain (i.e concrete and stable) and which assemblies are potentially useless (i.e abstract and instable).

Online documentation:

For beginners: Where to start

Code queries and rules results are truncated to list a maximum of 100 code elements in this report

Does this report gets too large?

The list contains only code elements refactored or added since the baseline for comparison.

The setting Recent Violations Only is enabled

Why should I enable the setting Recent Violations Only ?

Quick Tips

Main
ndepend report summary application nameSolidTacToe (v1.0.0.0)report build date07/25/2014 21:30:50analysis duration00:04ndepend version 5.2.1.8320 (Evaluation: 14 days left)baseline for comparison Not Defined. To define a Baseline for Comparison, please read this online documentation. code coverage data Not Defined. To import Code Coverage Data, please read this online documentation.
Get started.Quick tips.Back to NDepend. The present HTML report is a summary of data gathered by the analysis.
It is recommended to use the NDepend interactive UI capabilities
to make the most of NDepend by mastering all aspects of your code.

Diagrams

.NET Assemblies Dependency Graph
Dependency Graph
View as ?fullscaled
.NET Assemblies Dependency Matrix
Dependency Matrix
View as ?fullscaled
Treemap View
Treemap Metric View
View as ?fullscaled
Abstractness versus Instability
Abstractness vs. Instability
View as ?fullscaled

Application Metrics

Note: Further Application Statistics are available.
# Lines of Code
357      
0 (NotMyCode)
# Types
65      
3   Assemblies      
12   Namespaces      
226   Methods      
2   Fields      
51   Source Files      
Comment
47.35%      
321   Lines of Comment      
Method Complexity
6   Max      
1.54   Average      
Code Coverage by TestsN/A because no coverage data specified
Third-Party Usage
4   Assemblies used      
18   Namespaces used      
89   Types used      
63   Methods used      
0   Fields used      

Rules summary

117202This section lists all Rules violated, and Rules or Queries with Error
  • Number of Rules or Queries with Error (syntax error, exception thrown, time-out): 0
  • Number of Rules violated: 22

Summary of Rules violated

graphHelp Rules can be checked live at
development-time, from within Visual
Studio. Online documentation.
graphHelp NDepend rules report too many flaws on
existing code base? Use the option
Recent Violations Only!
warningCritical Some Critical Rules are violated. Critical Rules
can be used to break the build process if
violated. Online documentation.
Name # Matches Elements Group
warning   Base class should not use derivatives
4 typesObject Oriented Design
warning   Class with no descendant should be sealed if possible
36 typesObject Oriented Design
warning   A stateless class or structure might be turned into a static type
11 typesObject Oriented Design
warning   Non-static classes should be instantiated or turned to static
23 typesObject Oriented Design
warning   Methods should be declared static if possible
11 methodsObject Oriented Design
warning   Avoid empty interfaces
2 typesObject Oriented Design
warning   Classes that are candidate to be turned into structures
4 typesDesign
warning   Avoid namespaces with few types
7 namespacesDesign
warning   Nested types should not be visible
10 typesDesign
warning   Don't forget to implement methods that throw NotImplementedException
1 methodsDesign
warningCritical   Avoid namespaces mutually dependent
2 namespacesArchitecture and Layering
warning   Avoid namespaces dependency cycles
1 namespacesArchitecture and Layering
warning   Assemblies with poor cohesion (RelationalCohesion)
1 assembliesArchitecture and Layering
warningCritical   Potentially dead Methods
3 methodsDead Code
warning   Methods that could have a lower visibility
67 methodsVisibility
warning   Types that could have a lower visibility
22 typesVisibility
warning   Types that could be declared as private, nested in a parent type
3 typesVisibility
warning   Instance fields should be prefixed with a 'm_'
1 fieldsNaming Conventions
warning   Static fields should be prefixed with a 's_'
1 fieldsNaming Conventions
warning   Avoid methods with name too long
1 methodsNaming Conventions
warning   Avoid defining multiple types in a source file
1 typesSource Files Organization
warning   Mark assemblies with CLSCompliant
3 assembliesSystem
Showing 1 to 22 of 22 entries