AP 2025-12-10

A team is using CATIA Magic for system architecture and the 3DEXPERIENCE platform for requirements management. To leverage the collaboration and requirement management features of the platform while managing architecture in CATIA Magic, the team needs to integrate ENOVIA Requirements with DataHub.

This Technical Practice emphasizes the importance of seamless collaboration and data management for integrating ENOVIA Requirements with the DataHub.

Requirements Manager, Systems Architect

Requirement Management

Requirement management is the process of collecting, analyzing, refining and prioritizing the product requirements and then planning for their delivery. Requirements management ensures that the organization validates and meets the needs of its customers and external and internal stakeholders.

Data Model of SysML

Integrating CATIA Magic models with ENOVIA Requirements through DataHub is crucial for seamless data exchange and interoperability. DataHub provides predefined mapping templates that facilitate the exchange of data between SysML models and ENOVIA Requirements, ensuring that requirements and system architectures are consistently managed and traced. This integration allows for the synchronization of stakeholder requirements defined in ENOVIA Requirements with system requirements and architectures modeled in SysML, enabling a cohesive and traceable development process.

Operations in DataHub Explorer

The Operation list in the Cameo DataHub Explorer panel provides several options for you to work with your data.

The table below briefly explains the functions of the DataHub operations.

Operation	Function
Copy Data	Only copies the data with child nodes.
Copy Data with DHTrace	Copies data and creates DHTrace links between the source and target nodes. DHLinks are used to trace the changes.
Copy Data with Sync	Copies data and creates synchronization (DHLinks) between the source and target nodes. Nodes in the modeling tool are updated or deleted whenever their corresponding nodes in associated tools are updated or deleted. The newly created nodes can be transferred to other associated tools as well.
Create DHTrace (with OSLC links)	Creates DHLinks between the source and target nodes without copying any data. Creates an OSLC link from an IBM® Rational® DOORS® Next Generation Data Source to a MagicDraw® element.
Create Sync	Recreates synchronization (DHLinks) if you lose or delete the DHLinks without replicating the data.

Copy Data with Sync operation

In this operation, a DHLink for synchronization is added to the data. It maintains the structure and data of the elements within the node. During data synchronization, DataHub searches for any new nodes and deleted nodes. If it finds any new nodes or deleted nodes within the scope on one side, DataHub copies them to the other side and creates a synchronization relation between them or deletes them from the other side.

Copy Sync Operation

The Create Sync operation will create or recreate synchronization (DHLinks) if you lose or delete the DHLinks This new operation allows you to create or recreate synchronization(DHLinks) without replicating the data.

Use Case 1: Copy Data with Sync Operation from ENOVIA Requirements to CATIA Magic

Scenario: A systems engineer initiates a Copy Data with Sync operation to copy validated requirement changes from TRM to CATIA Magic, enabling seamless traceability and model alignment.

Personas: Dave, Systems Architect is responsible for maintaining requirement traceability. After requirements are updated in ENOVIA Requirements, he triggers a sync operation to copy the latest data into CATIA Magic, ensuring the system model stays aligned with the current specifications.

Workflow:

Use Case 2: Update Requirements from CATIA Magic to ENOVIA Requirements

Scenario: The Systems Architect is assigned to update the CATIA Magic model and wants to synchronize the updated requirements and traceability data to TRM to ensure consistent and collaborative development across teams.

Actors/Personas: Dave, Systems Architect is responsible for updating the CATIA Magic model and syncing the revised requirements and trace links to TRM to keep all teams aligned and maintain data consistency.

Workflow:

Use Case 3: Update Requirements from ENOVIA Requirements to CATIA magic

Scenario: The Systems Architect is assigned to update the system model in CATIA Magic by syncing the latest requirements changes from TRM, ensuring the architecture stays aligned with current specifications and traceability.

Actors/Personas: Dave, Systems Architect is responsible for updating requirements in TRM and syncing those changes into CATIA Magic to ensure the system model reflects the latest requirements and maintains accurate traceability.

Workflow: