N denotes the number of nodes in the graph At this time in my little library, there are two high issues, six medium and two low.E denotes the number of edges in the graph Issues: Another classification of the problems of your code classified by its importance.Rules: Again, a set of analyzers that could pass or fail.If you see something in fail, as in this case, you should start with that point to review your application. This is a direct image of the quality of your code. Quality Gates: Quality gates are a set of rules classified as either fail, warn, or pass.In this case, I have no unit tests, so its value is 0%.
Types: Counts the number of language constructs such as the number of assemblies, the number of namespaces, the number of methods, of field, and of third-party elements.# Lines of Code: it counts the lines of code.In this context stable means painful to modify. Instability: an assembly is considered stable if its types are used by a lot of types from other assemblies. Abstractness: If an assembly contains many abstract types (i.e interfaces and abstract classes) and few concrete types, it is considered abstract. It 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 unstable). Instability: This is a very interesting representation. Its size and color depends on its complexity. Practically, you see an image composed of squares, with each square representing a method. Treemap Metric View: This is a matrix that represents the cyclomatic complexity of your software.Dependency Matrix: Another representation of the assemblies relations.In my example we see that Playground depends on BasicEmailQueueManager(of course, Playground uses its classes) and by. Dependency Graph: Here we can see the relations between the assemblies our application.
0 kommentar(er)
