Tested integration scope
Last updated: October 12, 2026
DOORS Next 7.2
On an evaluation server, live reads of 100 and 1,000 invented requirements matched real CSV exports for IDs, order and text after whitespace normalization. These read tests included two requirement types and Unicode text.
In a separate module with three requirements, live writes persisted all five VerifyPlan fields. A second dry run found no changes. Annotated ReqIF reimport, including a repeated import, preserved the existing requirement IDs, text and module count. The fields already existed before export.
Other requirements tools
Polarion tests covered an 80 requirement document, with live reads and annotated ReqIF updates to existing work items. Live API writes updated the run field, and a second dry run found no changes.
DOORS Classic export parsing is tested on small public ReqIF files. It has no live connector, and reimport remains untested. Real Jama exports and live Jama integration remain unverified.
Writes are for evaluation projects
Use fresh audits and trusted source URLs in isolated test projects. Writes are not yet proven safe for production: stale audit text is not checked, ETag protection is optional, and a later failure can leave earlier batch updates applied. Resource origin checks also need improvement.
These tests are not vendor certification or proof for every version and configuration. Larger writes and the 10,000 requirement test remain unproven. The DOORS Next connector supports Jazz form login and Basic authentication, not external OIDC login.
IBM, DOORS Next, Siemens and Polarion are trademarks of their respective owners. Their names identify compatible tools, not a partnership or endorsement.