Working with deleted requirements and model elements (Integration for IBM Rational DOORS)

When a requirement or model element is deleted, Integration for IBM Rational DOORS can delete that requirement or model element, or mark the requirement or element as deleted.

Integration for IBM Rational DOORS can export and import requirements, and when it does so it can delete requirements from either environment:

• If the Synchronization Direction is Modeler -> DOORS and a requirement is only in DOORS, Integration for IBM Rational DOORS deletes that requirement from the DOORS surrogate module, unless the Keep Unsynchronized Items check box is selected.

• If the Synchronization Direction is DOORS -> Modeler and a requirement is only in Modeler, Integration for IBM Rational DOORS deletes that requirement from the Modeler model, unless the Keep Unsynchronized Items check box is selected.

• If the Synchronization Direction is Modeler <-> DOORS and a requirement used to be in both environments but is now only in one environment, Integration for IBM Rational DOORS deletes that requirement.

Note that if the Synchronization Direction is Modeler <-> DOORS and a requirement has been added to one environment and is not present in the other environment, Integration for IBM Rational DOORS adds the requirement to the other environment.

When Integration for IBM Rational DOORS deletes a requirement, the options in the 'Action for Deleted Source Object' group of the Requirements Mapping Options page determine whether Integration for IBM Rational DOORS deletes the requirement or marks the requirement as deleted:

• In Modeler, a SysML Requirement is marked as deleted by setting its 'isDeletedInRequirementTool' tag definition (applied by the «requirement» stereotype) to True.

• In DOORS, a requirement is marked as deleted by setting its 'ART Model Element Deleted' attribute to True.

Note that before deleting a Requirement in DOORS Integration for IBM Rational DOORS deletes its incoming and outgoing links that are in the scope of the mappings that are being synchronized. If after deleting these links there are no incoming or outgoing links, Integration for IBM Rational DOORS deletes the Requirement form DOORS; if after deleting these links there are incoming or outgoing links, Integration for IBM Rational DOORS does not delete the Requirement in DOORS and instead marks it as deleted.

To maintain the traceability of requirements that have been deleted, you may prefer to mark requirements as deleted, rather than deleting the requirements.

Undeleting a surrogate object may result in more than one surrogate object being mapped to the same Modeler item. If Integration for IBM Rational DOORS detects this problem it abandons the synchronization and records which surrogate objects are causing the problem in the log. To resolve the problem you must change the module so that only one surrogate object is mapped to the Modeler item.

If Integration for IBM Rational DOORS has created a surrogate object for a Modeler item and then that model item is deleted or not included in a future synchronization, Integration for IBM Rational DOORS can delete that surrogate object from the DOORS surrogate module.

When Integration for IBM Rational DOORS deletes a surrogate object, the options in the 'Action for Deleted Modeler Items' group of the Surrogate Mapping Options page determine whether Integration for IBM Rational DOORS deletes the model object or marks the model object as deleted. In DOORS, a model object is marked as deleted by setting its 'ART Model Element Deleted' attribute to True.

Note that before deleting a DOORS object Integration for IBM Rational DOORS deletes its incoming and outgoing links that are in the scope of the mappings that are being synchronized. If after deleting these links there are no incoming or outgoing links, Integration for IBM Rational DOORS deletes the DOORS object; if after deleting these links there are incoming or outgoing links, Integration for IBM Rational DOORS does not delete the DOORS object and instead marks it as deleted.

To maintain the traceability of surrogate objects that have been deleted, you may prefer to mark surrogate objects as deleted, rather than deleting the surrogate objects.