Managing Conversation ID & Round-Trip Synchronization in ReqIF/DNG/Jama Connect

Overview

This article outlines best practices for handling synchronization between Jama Connect, DOORS Next Generation (DNG), and ReqIF-based exchanges when a set of items already exists in both systems. Since DNG does not natively support 'Conversation ID', alternative approaches are necessary for maintaining synchronization during round-trip exchanges.

1. Understanding 'Conversation ID' in ReqIF

• The ReqIF standard does not explicitly define 'Conversation ID' but provides a Unique ID at the root of the ReqIF file for object identification.

• The 'Conversation ID' concept is an extension provided by Prostep Ivip, but it is not natively supported by DNG or Modern Requirements.

• This lack of support complicates round-trip workflows, requiring alternative synchronization mechanisms.

2. Workarounds for Synchronization Between Jama & DNG

Since DNG does not recognize 'Conversation ID', follow these steps to establish a stable round-trip workflow:

A. Using 'External ID' for Synchronization

• Instead of relying on 'Conversation ID,' use 'External ID' as the global identifier at the item level.

• The 'External ID' allows tracking changes between synchronized projects.

• This ID can be used for scripting synchronization across tools.

B. Importing DNG Data & Creating Synchronization Rules

1. Import DNG data into a secondary project (or Jama instance) that serves as an intermediary.

2. Map the DNG IDs to the 'External ID' field to preserve traceability.

3. Apply scripting to maintain synchronization rules that align changes in both systems.

3. Best Practices for Round-Trip Management

✔ Use 'External ID' at the item level as the persistent identifier across exchanges.
✔ Automate synchronization scripts to maintain traceability between Jama and DNG.
✔ Ensure consistency in ID mapping before initiating the first ReqIF exchange.
✔ Document all synchronization rules in internal workflows to maintain process integrity.

4. Key Takeaways

• DNG does not natively support 'Conversation ID', requiring workarounds for synchronization.

• Using 'External ID' ensures that items remain linked across projects.

• Scripting synchronization logic is necessary for maintaining round-trip integrity.

• Proper ID mapping and structured workflows prevent data inconsistencies between Jama, DNG, and ReqIF-based exchanges.

Conclusion

For teams working with Jama Connect, DOORS Next Generation, and ReqIF, adopting 'External ID' for item tracking is the most effective way to enable consistent synchronization and round-trip workflows. Until DNG provides native support for 'Conversation ID', automation and structured ID mapping remain essential.