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:

  1. In the Objects with Conflict field, review the objects that have conflicts.
  2. In the Object Attributes with Conflicts field, individually select each attribute to view the details.

    When you click an item in this section, the conflict results display in the Original Value, Current Value, and Proposed Value fields. Resolve these one at a time.

  3. Review the following sections:
    • Original Value: Displays, before any changes, the attribute value.
    • Current Value: Displays the current attribute value that is in the Rational DOORS database.
    • Proposed Value: Displays your proposed values for that attribute.
  4. In the Format field, in the Proposed Value section, select from the following options:
    • Proposed Value: Displays the proposed value as it is displayed in Rational DOORS.
    • Difference with Original: Displays the proposed value with redline differences against the original value.
    • Difference with Current: Displays the proposed value with redline differences against the current value.
  5. To edit the information in the Proposed Value field:
    1. Click Edit to activate the Update and theCancel options so that you can make your edits.
    2. Click Update to update the object with the conflict.
    3. Optionally, to undo the edits, click Cancel.
  6. Determine how to resolve the conflict, and then perform one of the following actions:
    • To keep the proposed edits and to permit your changes to overwrite the values in the database, click Keep Proposed.

      The attribute value stays as is, with your changes.

    • To discard your changes and keep the database values, click Discard Proposed.

      The proposed values are replaced with the attribute current values.

    • To override the conflict and make the RCR active, in the Objects with Conflicts field, select all objects, and then click Finish Conflict Resolution to clear the obsolete flag.

      The Finish Conflict Resolution option becomes active after the resolved box is checked for each object. It also becomes active when all objects with conflicts are resolved.

  7. Click Close.
  8. In Rational DOORS, save the module.

    If you discard any proposed changes, the Rational DOORS module closes.


Feedback