One of my colleagues asked me to analyze the project written by his group of programmers. The project was written during 4 years by a group of 10 programmers, using the technology of Spring. Can you share some ideas of what tools, methods and classifiers you use to analyze the quality of writing projects written in Java.

3 answers 3

"The quality of writing a project," in my opinion, consists of two things:

  1. Low-level: direct quality code. For such a test, use a static code analyzer, it will find potential problem areas (logical errors in conditions, dangerous patterns, etc.). There are both separate tula and embedded in the IDE (for example, in IntelliJ Idea).
  2. High-level: quality design, adequacy of the solution architecture. This is evaluated only by the analysis of the requirements and the finished solution, and requires considerable experience. But it allows you to answer different questions, for example: Will the project be bent after six months from minor changes in the requirements? Is it difficult to make changes to the existing code? To some extent, this is even more important quality than the quality of the code, because correcting errors of this level is very difficult and expensive.

    Use a static analyzer. A link to their list was given to you in the comments. It is also worthwhile to conduct profiling and load testing (there are tool lists on the wiki as well).

      PMD Standard, in general, for these purposes with all the buns in both Eclipse and Jenkins.

      • Try to write more detailed answers. Explain what is the basis of your statement? - Nicolas Chabanovsky ♦