Enable ReqIF Export of Modules with Multiple Large Embedded Files

Current Situation:

When exporting modules via ReqIF that contain a large number of embedded files (some of them very large), DNG may run into an OutOfMemoryError.

According to IBM Support (IBM Case TS018669674), this issue occurs due to an internal array size limitation (2 GB) in the Java Runtime. Once DNG buffers the embedded files during the export process, this limit can be exceeded, causing the export to fail.

Problem / Impact:

ReqIF exports fail when modules include multiple large attachments. This prevents teams from exchanging complete requirement modules with stakeholders or other tools.
Workarounds (e.g., splitting modules or removing attachments) are inefficient, error-prone, and compromise consistency between the source and the exported module.

Target / Requirement:

ReqIF exports should reliably support modules that contain many large embedded files. The export process must be able to handle large attachments without running into memory or runtime limitations. This is essential for efficient collaboration in larger projects, where requirements are typically enriched with extensive supporting documentation.

Benefits:

• Increased reliability of ReqIF export in real-world scenarios.
• Significant reduction of manual effort for users (no more splitting modules or removing attachments required).
• Improved collaboration and interoperability with partners, customers, and suppliers through complete and accurate data exchange.

Open questions:

• If there has to be an 'upper limit' that export supports, what should the upper limit be?
  • Size of one embedded file? (Suggestion: Up to 200 MB)
  • Total size of all embedded files for exported ReqIF? (Suggestion: Up to 2GB)