Change Management for Rational® DOORS® automatically detects most
conflicts during the review and apply states. During
review, conflicts are detected only within the selected RCR. During apply,
conflicts are detected on all approved RCRs.
When Change Management for Rational DOORS checks for conflicts, one
of the following situations occur, depending on how the template was
configured.
- Warns you when you are modifying attributes that already have
outstanding proposed changes.
- Prevents approval of RCRs that conflict with already approved
RCRs.
- Helps you identify and resolve conflicts when working on an RCR
that is marked obsolete.
For more details, see Defining
configuration templates and Resolving
requirements change request conflicts.
Conflicts
The following are some examples
of conflicts:
- Two or more proposals were made against the same object or module.
These proposals might clash with each other or be order-dependent.
- Multiple RCRs were approved against the same object and the change
type is Delete on any of the RCRs.
- The Rational DOORS attributes were changed
by the RCR overlap.
- Two RCRs were approved to change the object text of a requirement.
If both are applied without revision, the second one applied would
overwrite the first. Similarly, one CR might request a child object
to be added to requirement X while another requests that requirement
X be deleted. If the latter is applied, the former must not be applied.
- Not all changes were made using Change Management for Rational DOORS. The change management feature cannot
detect manual changes. For example, an RCR might have been submitted
against a requirement. Before the CR was applied, someone manually
modified the requirement without using the change management feature.
In this case, when the CR is applied, it might overwrite the other
change because the two are unrelated.
The system, however, cannot detect all conflicts, so they
need to be inspected manually to evaluate the semantics of the change.
See Resolving requirements change request conflicts.
Use the RCR Conflicts report to identify the conflicts the system
cannot detect. See Running the RCR Conflicts report.