Determine architectural dependencies directly from the code. Examples of SemmleCode's analyses include:

• Hub classes (classes that depend on and are a dependency of a large number of classes);
• Cyclic package dependencies;
• Dependencies on presentation classes (awt, swing, swt/jface, jsp, struts), and SQL classes.

You can also create your own custom analyses and tailor it to your own project, define your own layers and find their dependencies.

SemmleCode shows the results of these analyses using rich visualizations (heat maps, graphs, charts...), making it easier to spot architectural problems.

SemmleCode's Eclipse integration makes it possible to navigate directly from the visualizations into the code, allowing you to diagnose the problem quickly and effectively.

See SemmleCode's features...
Watch video...

Quickly and automatically compute code quality metrics and find latent bugs and violations of best practice by running SemmleCode's analyses. Some of the issues SemmleCode can help you uncover:

• Classes with deep nested loops and branches (high cyclomatic complexity);
• Cross-site scripting vulnerabilities;
• Classes that lack cohesion.

SemmleCode can automate away a lot of the tedium of code reviews, letting you get on with finding deeper bugs that may lie in the code.

SemmleCode's metrics and visualizations allow you to quickly find the quality "hot" spots in code, so that you can focus on the areas that need the most attention.

SemmleCode also allows you to save a history of your analyses, and let you compare them to see trends over time of a codebase's quality metrics.

See SemmleCode's features...
Watch video...

Locate refactoring opportunities in a project using SemmleCode. The following patterns indicate code that can be refactored, and are examples of what SemmleCode can spot:

• Large classes, which are likely to be classes that try to do too many things;
• Unrelated classes with a large number of similar methods (methods with the same signature), which can possibly be refactored to have a common superclass;
• Classes with too many fields or dependencies. Methods that have too many parameters.

You can check the refactoring as it is being performed, through live analyses. Live analyses are run every time your code is built in Eclipse, allowing you to see the progress of your refactoring as it happens.

See SemmleCode's features...

Enforce project-specific coding and architecture conventions by making your own SemmleCode custom analyses. All checks are concisely expressed in the object-oriented query language .QL. This makes it possible to create your own checks, for instance to enforce:

• Naming conventions on classes, fields, methods;
• Layer dependencies;
• Method return conventions (single exit point in methods).

By continuously running these checks you can prevent further occurrences of undesirable code patterns and avoid recurring bugs caused by them.

See SemmleCode's features...