Extend an existing CAD application
Software customization starts from an application that already has users, data and operational constraints. The work may add a geometry operation, adapt a workflow, integrate a commercial component or prepare the product for another platform or OCCT release.
Preserving the behavior that users rely on is part of the scope. Identify existing workflows and data that must continue to work alongside the requested change.
Product configuration and third-party application extensions
Customization can combine software development, configuration and maintenance around an existing OCCT3D product or component. The starting point is the customer’s operating process: which commands, data, geometry rules and outputs need to change for the product to fit that process.
The scope can also include extensions to third-party CAD, CAM or CAE products. Identify the host application’s supported extension interfaces, version and deployment requirements before selecting the integration. Existing OCCT3D geometry, visualization and exchange components provide reusable building blocks for these changes.
Plan an OCCT upgrade or platform change
Establish the current OCCT version, target version, compiler, dependencies and deployment platforms. Check affected APIs and the application’s geometry, visualization and exchange behavior. A successful build alone does not establish that existing models still produce the expected results.
Agree on representative regression cases and release acceptance criteria before making the change. Platform-specific dependencies and commercial component compatibility should be evaluated with the target delivery.
Preserve behavior across an OCCT migration
Build a comparison set from the application’s actual use: imported assemblies, edited models, saved documents, meshing settings and export targets. Compare both geometry and the information users depend on, such as names, colors, selection behavior and document structure.
For a .NET application, include wrapper API coverage and native runtime packaging in the migration scope. The C# Wrapper page describes the published OCCT 8.0.0 packaging options. For a change of data model, assess how BRepGraph Advance operations fit into the existing workflow before substituting individual calls.
Scope a focused improvement
Describe the current workflow, intended behavior and reason for the change. For performance work, include a reproducible baseline; for data exchange, specify source and target requirements using the format matrix.
Use architecture consulting when the implementation approach needs review. See development engagement options for work from technical proof through handover.