Resolving requirements change request conflicts
When conflicts are found, they must be resolved manually.
To manually resolve conflicts, reject one of the RCRs, or reject one
of the proposed changes from the conflicting RCR. Usually the person
who proposed the changes or the person who is responsible for the
entire document resolves the conflicts.
About this task
Attention: Be careful when rejecting individual
proposed changes from an RCR. If there are interdependencies between
proposals and only some of the proposals are rejected, an RCR might
be rendered invalid. For example, if the RCR proposes to create a
hierarchy of new Rational® DOORS® objects and the proposal
to create the topmost object is rejected, the other objects no longer
have a parent object, and the RCR is invalid.
When a module is opened in exclusive or shareable edit mode and the default RCR is marked obsolete, Change Management for Rational DOORS displays the Conflict Resolution for RCR - DOORS window.
For more information about how RCRs are marked obsolete, see Applying approved requirements change requests.
The change management feature offers several options to resolve RCR conflicts.
At anytime, click Navigate to Selected Object to view the exact object within the module.
Procedure
To resolve RCR conflicts: