Binding Conflict in Doors Next (DNG) During ReqIF Import

1. Artifact bindings are module-specific: In DOORS Next, each artifact is assigned a unique binding URI linking it to a specific module. Although the same artifact may appear in multiple modules logically, each appearance is treated as a distinct binding. These bindings cannot be reused across modules.
2. Mapping is tracked and enforced by DNG: Artifact-module associations are recorded in an internal system map, and DNG validates these during ReqIF imports. Binding conflicts arise when an artifact is referenced in a different module without the original binding being removed.
3. Current conflict – reassignment to a new location: In the most recent ReqIF package, the stakeholder reassigned several artifacts to new locations (within same module or cross-modules). DNG detects that these artifacts were previously bound to other artifacts. Even in case of deletion, historical constraints prevent reusing those bindings in a new context.

Improve error reporting clarity in DNG for import failures, especially those related to binding conflicts. 

The system should explicitly report:

• The originating module of the artifact binding
• The target module attempting to reuse the binding
• The specific artifact(s) involved
• Request comprehensive IBM documentation detailing:
  • How DNG handles artifact bindings internally
  • How binding conflicts can be proactively diagnosed
  • Best practices for managing artifact movements across modules during ReqIF exchanges

Outcome: Reduced manual rework, improved transparency, and enhanced traceability in distributed requirements engineering environments.