contato@eccox.com.br
+ 55 11 4133-1969

Eccox Quality Controlfor Java

Eccox Application Quality Control for Java is a tool that automates the verification of Java coding. Studies have shown that almost 80% of the cost of software goes on maintenance and the source code is seldom maintained by its author. Therefore, the standardization of code improves the legibility of the software, allowing developers to understand the source code more rapidly. In this context, it becomes important to have an automated process that continuously monitors and integrates the Java coding and is capable of identifying inadequate code before it is promoted to the productive environment.

Benefits

  • Standardized and automatic rules and processes
  • Greater stability of business platforms
  • Improved performance
  • Identification of codes classified as unacceptable
  • Continuous improvement, your infrastructure ready for digital transformation

“Java is a simple, object-oriented language that is interpreted, robust, secure, architecture neutral, portable, high performance, threaded and dynamic (Source: Sun White Paper on Java).

All of these characteristics of Java enable developers to define numerous solutions for the same problem. However, some solutions can generate costs and can affect aspects such as reliability, availability and maintainability of the application. Consequently, low quality applications may be implemented in the productive environment, as the developers do not use more adequate coding in terms of quality. In general, deadlines for the development and maintenance of programs lead to a focus on effectiveness (seeking an end-result) in detriment of efficiency (seeking results with the best quality).

Eccox Application Quality Control for Java verifies whether the code conforms to the pre-set rules aiming to standardize the code, thus increasing the reliability, reusability, maintainability and availability of Java applications. It acts as a quality filter, impeding inadequate code from being promoted to the productive environment and identifying coding that could lead to the consumption of critical resources or impacts on the stability of the environment.

It is run to support the developer in the coding process, identifying coding with violations and providing guidance for applicable alternatives for each case. Eccox Application Quality Control for Java should be used during the development of Java applications in the stages that precede the promotion of the application within the lifecycle of the software or in inventory processes to identify eventual opportunities for improvement.

Acting as a quality filter, Eccox Application Quality Control for Java must be integrated into the development cycle of applications (Plugin Eclipse) interacting in the development and maintenance phases of the source codes. The evaluation process produces a report containing the consolidated score of each source file of the project, its violations and respective signals:

  • Green: indicates that the evaluated source file is in accordance with the standards of the corporation.
  • Yellow: indicates that the evaluated source file has violations that are tolerable in the corporation but require attention to eliminate them.
  • Red: indicates that the evaluated source file has serious violations that are not in accordance with the standards of the organization.
  • Blue: indicates that the source file has a red signal and is in exception.

Main functions

• Easy and simple integration with tools that manage the application lifecycle, such as CVS, SVN, Hudson, Continuum, etc.
• Definition and implementation of contingency processes;
• Monitoring the vegetative growth of the bases of Eccox Application Quality Control for Java according to the stored evaluation data;
• Implementation of backup, reorganization and security procedures stored in the bases of Eccox Application Quality Control for Java;
• Implementation of the Purge process of the evaluation data;
• Maintenance of processes that implement Eccox Application Quality Control for Java interface with the ongoing integration process;
• Adjustments to the product parameters;
• Adjustment to the parameters of the verification rules;
• Choice of adopted evaluation criterion, signal codes and mode of operation;
• Registration of source files in exception;
• Registration of projects;
• Registration of the Legacy.