Mapping System Composer ReqIF Elements to Jama Connect via DX

Overview

This article explains how to map different element types (containers, requirements) from System Composer ReqIF exports into Jama Connect using DX and whether a conversion script is required.

1. Problem: Containers and Requirements Are Treated as the Same Type in ReqIF

✔ Observed Behavior:

• System Composer exports to ReqIF but does not differentiate between containers (folders, sets) and actual requirements in the ReqIF file.

• Instead, all elements are treated as generic requirements, with an attribute to indicate the type.

• During round-trip back into Jama, DX does not recognize containers as components, sets, or folders—they import as requirements instead.

✔ Impact:

• Containers are not preserved in Jama after import.

• Structure is lost, making navigation harder.

✔ Question:

• Can DX map attributes to determine whether an element is a folder, text item, or system requirement before importing?

2. Solution: Using a Conversion Script to Modify ReqIF Before Importing into Jama

✔ DX does not have built-in logic to distinguish containers from requirements.
✔ A ReqIF Object Converter script is required to modify the ReqIF file before import.
✔ The script can:

• Identify container attributes in the ReqIF file.

• Convert them to Jama-recognized item types like folders, text items, or system requirements.

• Preserve the original structure before import.

✔ Example ReqIF Modification:

• Before (Raw ReqIF Output from System Composer):

  xml

  CopyEdit

  <SPEC-OBJECT> <ATTRIBUTE-VALUE-STRING> <DEFINITION-REF>Type</DEFINITION-REF> <VALUE>Container</VALUE> </ATTRIBUTE-VALUE-STRING> </SPEC-OBJECT>

• After (Modified for Jama Import):

  xml

  CopyEdit

  <SPEC-OBJECT> <ATTRIBUTE-VALUE-STRING> <DEFINITION-REF>Item Type</DEFINITION-REF> <VALUE>Folder</VALUE> </ATTRIBUTE-VALUE-STRING> </SPEC-OBJECT>

3. Available Tools & Workarounds

A. Use the ReqIF Object Converter for DOORS-Based ReqIF Files

✔ Jama has an existing ReqIF Object Converter built for DOORS ReqIF files.
✔ Located in the Jama Software EES Tool Suite:

• GitHub Link: ReqIF Object Converter
  ✔ This may require modification to support MathWorks System Composer ReqIF format.

B. Manual Pre-Processing Before Importing to Jama

✔ If a script is not feasible, manually edit the ReqIF file to adjust types before import.
✔ This method is time-consuming but ensures proper mapping.

C. Future Integration with Jama Connect Interchange (JCI)

✔ JCI is fully designed to handle ReqIF transformations but is not yet implemented in the roadmap.
✔ Customers seeking better ReqIF handling should monitor JCI updates.

4. Best Practices for Mapping System Composer ReqIF to Jama

✅ Identify how System Composer marks different item types (containers vs. requirements) in the ReqIF export.
✅ Use a conversion script to modify ReqIF files before importing into Jama.
✅ Test the ReqIF import in a sandbox environment to verify correct mapping.
✅ Track JCI development for future improvements in ReqIF handling.

5. Conclusion

• System Composer exports ReqIF files treating all items as requirements.

• DX does not distinguish between containers and actual requirements without modification.

• A ReqIF conversion script is required to adjust item types before import.

• Future improvements may come via JCI, but no immediate fixes exist in DX.