Hi,

I have a customer with a question regarding the Jama integration to Cameo using DataHub.

The current Jama workflow has a defined "Derive" relationship that goes from an upstream requirement (parent) to a downstream requirement (child). The intent is to import this into Cameo as a deriveReqt relationship in which the downstream requirement is derived from the upstream requirement. 

The problem is that when the schema is set up, DataHub seems to automatically interpret the direction of the Jama relationship and translate it into a deriveReqt in the "wrong" direction. There seem to be no properties available in the schema to "force" a different interpretation either, like interpreting the source in Jama as the target in Cameo.

A possible solution would be to create a "Derived From" relationship on the Jama side that matches the deriveReqt direction, but this is not optimal because it would disrupt the current requirement management processes handled in Jama.

Another possible solution seems to be to create a custom relationship stereotype in Cameo that is just like deriveReqt but reversed. This one is not optimal because it would require employing a new relationship with different semantics for the broader team.

Is there a known, easier way to overcome this issue?

Thank you!