Overview
This article explains the DX option for including a top-level container in exports, its relevance to ReqIF, and considerations for Jama Connect Integration (JCI).
1. What Is the "Include Top-Level Container" Option in DX?
✔ This option allows users to export an entire container structure, treating the top-level component as the primary module.
✔ Without selecting this option, DX exports only the first-level children of the selected location, treating them as separate specifications.
✔ This is NOT a standard ReqIF feature but rather a DX-specific implementation for structuring ReqIF documents.
✔ Impact on ReqIF Exchange & JCI:
-
Other ReqIF-based tools (DOORS, DNG) may not support this flag.
-
When importing into JCI, the top-level container is visible, but nested sets are treated separately.
-
This feature was originally designed for multi-location project exports.
2. How Does the Export Setting Work?
✔ If "Include Top-Level Container" is selected:
-
The entire container structure is exported.
-
All sets inside the component become modules in DOORS upon import.
✔ If the option is NOT selected:
-
Only first-level children of the selected location are exported as independent ReqIF specifications.
-
Nested structures within the top-level container are not maintained as part of a unified module.
✔ When is this needed?
-
Jama-to-Jama exchanges require this option enabled to maintain the full structure.
-
If exporting to DOORS/DNG, users should verify whether the receiving tool can interpret top-level containers correctly.
3. Best Practices for Handling Top-Level Containers in ReqIF Exports
✅ For Jama-to-Jama Exchange: Always enable this option if maintaining the full structure is necessary.
✅ For Jama-to-DOORS/DNG Exports: Verify whether the target tool supports top-level containers or if a manual structure mapping is needed.
✅ For JCI Integration: Evaluate whether tool-specific methods can replace this feature to simplify user experience.
4. Conclusion
-
The "Include Top-Level Container" option is DX-specific and not a standard ReqIF feature.
-
Jama-to-Jama exchanges require this option enabled, while other tools may not interpret it correctly.
-
JCI may implement tool-specific solutions to handle structured exports/imports without requiring this setting.
Comments
0 comments
Please sign in to leave a comment.