Cameo to Doors Next Generation: Parent Child relationship

[j.h.greenhow@gmail.com]

Hi Everyone,
I am starting to use DataHub to take requirements from CAMEO Systems modeller 19 into Doors Next Generation (web version) but have come across a rather fundamental issue. I'm not sure what I am doing wrong .
I have a number of requirements within CAMEO that have a nested structure through the use of the 'containment' connector in CAMEO. My understanding was that the containment represented the parent child relationship. When I try and bring them into doors this parent child link is not recognised. If I use the other types of connector like derive or trace they are brought across. Any ideas on what I am doing wrong?

Kind Regards,

[j.h.greenhow@gmail.com]

Just a quick update on this. As I have heard back from NoMagic in regards to this. Their response is below;

"The issue is because DOOR Next Gen does not support nested requirements (they call requirements as flat objects). When we export the nested requirement from CSM to Door Next Gen, DataHub will ignore all child requirements under the hierarchy.

Door Next Gen has an object called Module Element that can be a view container for other elements. We are currently using this Door Next Gen’s capability to develop support for the nested requirements in DataHub. This function will be included in DataHub 20.0 release. "