Chapter 13 Impact analysis
When you generate a model to another model or when you create an external shortcut, you create cross-model dependencies. These dependencies are automatically taken into account during impact analysis provided the source and target models are open in the workspace.
If the models are not open in the workspace and if they are consolidated in the repository, you can use the extract dependencies feature to retrieve cross-model dependencies. This feature scans inverse collections between models consolidated in the repository and extracts objects in the local models. More precisely, it scans inverse collections in the model of the item selected in the impact analysis tree, this model may be different from the model where you opened the Impact Analysis dialog box.
The distant objects appear with a specific icon (a red dot) in the Dependencies page. To further analyze impact on objects depending on these distant objects you have to open their models.
In the following example, you analyze the impact of deleting table Sale. This table has a shortcut in another model with incoming references. The dependencies tree indicates that these references will be affected by the deletion of table Sale:
The extract dependencies feature allows you to recover object dependencies without having to open model in your current workspace. You do not even need to have the models on your machine provided these are consolidated in the repository.
| Copyright (C) 2006. Sybase Inc. All rights reserved. |
| |