DX Export Hierarchy Mapping from Jama to DOORS ReqIF

Overview

This article explains how Data Exchange (DX) exports from Jama Connect are structured when imported into IBM DOORS via ReqIF, highlighting key hierarchy transformations.

1. Understanding the Hierarchy Mapping

✔ Jama Components & Sets → DOORS Modules & Headings

• In Jama, a Component with Sets and Sub-components with Sets is exported.

• In DOORS, top-level Sets become Modules.

• Sub-component Sets become Headings within Modules instead of separate Modules.

✔ Excluded Elements in DX Export

• The “Requirements” root-level item in Jama (marked in red) is not included in the export.

• Only Solution Requirements and their sub-components (marked in green) are transferred.

✔ ReqIF Import Target Location in DOORS

• Requirements exported from Jama are imported into a specific target location in DOORS (marked in purple).

• They retain hierarchical structure but are structured according to DOORS' data model.

2. Key Observations from the Import Process

✅ Top-Level Sets in Jama become Modules in DOORS
✅ Sub-component Sets in Jama become Headings within Modules in DOORS
✅ Hierarchy is preserved but structured differently in DOORS
✅ Root-level organizational items (e.g., "Requirements") are not exported

3. Best Practices for Exporting DX Data from Jama to DOORS

✔ Plan the export structure to align with DOORS’ hierarchy needs.
✔ Ensure required Sets are structured properly before exporting to avoid unnecessary nesting.
✔ Verify the target import location in DOORS before performing the ReqIF import.
✔ Document any expected exclusions from the export to prevent missing data concerns.

4. Conclusion

When exporting Jama Connect data to DOORS via DX and ReqIF, understanding the hierarchy mapping is crucial. By knowing how Sets transform into Modules and Headings, users can plan exports efficiently and maintain traceability.

For additional guidance, refer to the Jama-to-DOORS ReqIF Export Guide (if available in your documentation repository).