Handling Parent-Child Relationships in DOORS 9 ReqIF Imports to Jama

Overview

This article explains how parent-child relationships in DOORS 9 ReqIF exports are handled in Jama Connect via DX, and possible workarounds to display them as relationships rather than text attributes.

1. Problem: DOORS 9 Parent-Child Relationships Are Captured as Attributes, Not Links

✔ Observed Behavior:

• DOORS 9 captures parent-child relationships as an attribute rather than a structured ReqIF relationship.

• DX imports this attribute as a text field in Jama rather than as a relationship link.

• Leidos wants this parent-child attribute to appear as a relationship in Jama, not just as text.

✔ Why This Happens:

• ReqIF does not natively support parent-child hierarchy relationships.

• The Tool-Extensions section in ReqIF contains path information, but it does not establish true relationships.

• DX does not have a built-in feature to convert parent-child attributes into relationships.

2. Current Workarounds

A. Import Parent-Child Data as a Text Field (Default DX Behavior)

✔ If the attribute exists in DOORS, DX can import it into Jama as a text field.
✔ This means the parent module name is stored in a field but does not create an actual relationship.
✔ Example:

• DOORS 9 Attribute: Parent Module: System Requirements

• DX Import Result in Jama: Text field → Parent Module: System Requirements

✔ Use Case:

• If customers only need a visual reference of parent-child structure, this may be sufficient.

B. Post-Processing Script to Convert Text into Relationships

✔ Since DX does not support this natively, a custom post-import script could:

• Scan imported parent-child attributes.

• Convert them into Jama relationships programmatically.

✔ How It Works:

• The script looks for matching parent-child names in imported sets.

• If a match is found, it creates a relationship link between them.

• This can be developed as a paid EES Request (Enterprise Engineering Services).

✔ Use Case:

• If customers need functional relationships instead of text, this is the best option.

C. Future Enhancement via JCI (Jama Connect Interchange)

✔ This feature has not yet been requested for JCI ReqIF handling, but it is possible.
✔ JCI could be enhanced to recognize parent-child attributes and convert them into relationships.
✔ Customers should discuss this request with Debbie Mitchell and the JCI team.

3. Best Practices for Handling Parent-Child Relationships from DOORS to Jama

✅ Determine whether customers need actual relationships or just text fields for reference.
✅ If relationships are required, consider a post-processing script to automate link creation.
✅ If looking for a long-term solution, engage with JCI to see if the feature can be built.

4. Conclusion

• DX does not convert parent-child attributes into relationships.

• By default, parent-child relationships from DOORS 9 appear as text fields in Jama.

• A post-import script can convert these attributes into actual relationships.

• Future updates in JCI may provide a native solution.