Eccox QC Modernization Guide
Eccox QC is a tools and utilities product by Eccox Technology. Explore technical details, modernization strategies, and migration paths below.
Product Overview
Eccox QC is a tool designed to apply and enforce site-specified rules to source code as it is developed.
The tool integrates with source code management software such as Serena Changeman ZMF and CA Endevor. Key features include: * **Code Analysis:** Analyzes source code against predefined rules. * **Scoring:** Produces a score reflecting code's adherence to rules. * **Integration:** Supports Serena Changeman ZMF, CA Endevor, Eclipse IDE, and CI/CD tools like CruiseControl and Hudson CI. * **Interfaces:** Offers batch and ISPF interfaces. To get started, configure the rules in the configuration files and use the batch or ISPF interface to analyze your code.
Modernization Strategies
Rehost
- Timeline:
- 6-12 months
Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.
Refactor (Recommended)
- Timeline:
- 18-24 months
Optimize application architecture for cloud while preserving business logic. Best ROI long-term.
Replatform
- Timeline:
- 3-5 years
Complete rewrite to cloud-native architecture with microservices and modern tech stack.
Frequently Asked Questions
General
What is the primary function of Eccox QC?
Eccox QC analyzes source code against a predefined set of rules to identify potential issues and enforce coding standards. It supports COBOL, DB2, CICS, and Java. The tool integrates with source code management systems like Serena Changeman ZMF and CA Endevor.
With what source code management systems does Eccox QC integrate?
Eccox QC integrates with Serena Changeman ZMF, CA Endevor, Eclipse IDE, CruiseControl, Apache Continuum, Hudson CI, Rational Team Concert, Apache Ant, and Apache Maven. This allows for automated code quality checks within existing development workflows.
What programming languages and environments does Eccox QC support?
Eccox QC supports COBOL code, including DB2 and CICS statements. It also supports Java for non-mainframe systems, typically used with Apache Tomcat.
How does Eccox QC measure code quality?
The tool produces a score based on predefined rules as code is compiled. This score reflects the code's adherence to the established coding standards and rules.
Technical
What interfaces are available for using Eccox QC?
Eccox QC can be used through batch interfaces for automated processing and ISPF interfaces for interactive use. Configuration files define the rules and standards to be enforced.
Does Eccox QC expose an API?
While specific API details are not publicly available, integration with CI/CD tools like CruiseControl, Apache Continuum, and Hudson CI suggests the presence of APIs or command-line interfaces for automated code analysis.
What are the main components of the Eccox QC architecture?
The architecture likely includes components for parsing source code, evaluating rules, and generating reports. Specific component names are not available without direct access to the product documentation.
What databases or storage mechanisms are used by Eccox QC?
The tool likely uses a database or file system to store rules, configurations, and results. Specific database types are not publicly documented.
Business Value
What is the business value of using Eccox QC?
By enforcing coding standards and identifying potential defects early in the development cycle, Eccox QC helps reduce development costs, improve code quality, and minimize the risk of production issues.
How does Eccox QC improve development workflows?
The tool's integration with source code management systems and CI/CD pipelines enables automated code quality checks, ensuring consistent adherence to coding standards across all projects.
How does Eccox QC contribute to customer satisfaction?
A higher code quality score translates to fewer defects, reduced maintenance costs, and improved application stability, leading to increased customer satisfaction.
Security
What authentication methods are supported by Eccox QC?
While specific authentication methods are not publicly detailed, enterprise tools often support standard methods such as LDAP or Active Directory integration for user authentication.
What access control model is used by Eccox QC?
The access control model is likely role-based access control (RBAC), allowing administrators to assign permissions to users based on their roles within the organization.
What audit/logging capabilities exist in Eccox QC?
Audit logging capabilities likely exist to track user activity and changes to rules and configurations, providing an audit trail for compliance purposes.
Operations
What administrative interfaces are available for Eccox QC?
Administrative interfaces are available through both batch and ISPF interfaces. The ISPF interface provides a GUI for interactive administration, while the batch interface allows for automated configuration and management.
How is user management handled in Eccox QC?
User management is typically handled through the administrative interfaces, allowing administrators to add, modify, and delete user accounts and assign roles and permissions.
What monitoring/logging capabilities exist in Eccox QC?
Monitoring and logging capabilities likely include the ability to track code analysis results, identify rule violations, and generate reports on code quality metrics.
Ready to Start Your Migration?
Download our comprehensive migration guide for Eccox QC or calculate your ROI.